[Nix-dev] Breaking changes log

[Domen Kožar]

Given that NixOS evolves rapidly compared to Rust (as a language), it's
going to be really hard to achieve that (without slowing down development
by orders of magnitude).

Note that API in NixOS is not defined, but if you're looking at it as NixOS
modules and packages, we're changing the API multiple times per day. If you
only account NixOS modules, renames.nix
do their job pretty good.

On Fri, Dec 19, 2014 at 4:01 PM, stewart mackenzie <setori88 at gmail.com>
wrote:
>
> Ah indeed thank you for the correction. Though my suggestion is to
> adopt C4 in its entirety. There would be no unstable master branch. At
> all times there is only one branch, that being master, and the stable
> APIs as part of this master branch remain stable, to be depricated and
> eventually made into legacy. Topic branches are only on forks. In
> effect we do a rolling release, with master being production ready at
> all times. Ideally if we could have a similar rather explicit
> stability annotation keyword syntax as demonstrated by rust-lang's
> API, I'd be glowing.
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.science.uu.nl/pipermail/nix-dev/attachments/20141219/d8145393/attachment.html