[Nix-dev] Stable NixOS releases

[Eelco Dolstra]

Hi,

On 14/05/13 17:44, Mathijs Kwik wrote:

>> But the risk with this approach is that people will be tempted to squeeze in
>> wildly destabilizing changes at the last moment :-)  I don't think this needs a
>> lot of bureaucracy or rules though, just some good sense not to (say) merge a
>> major GCC update into master just before the release is about to be branched.
> 
> I think stdenv-updates is still the only right place for those.
> Same for x-updates. We should not declare master
> "anything-can-break-now" just because we have stable, so maintaining
> master somewhat the same as we do now (with feature branches for
> larger undertakings) seems best.

Yes, I agree.  My point is that you want to give big changes like a
stdenv-updates merge some time to soak in master before they end up in a stable
release.

-- 
Eelco Dolstra | LogicBlox, Inc. | http://nixos.org/~eelco/