[Nix-dev] Stable NixOS releases

[Vladimír Čunát]

On 05/16/2013 12:31 PM, Peter Simons wrote:
> Now, steps (1) and (2) are easy.
>
> Step (3) is hard, because it's an on-going effort that someone needs to
> pay attention to constantly. Also, propagating changes from master into
> the release branch can be difficult, because the commits in question may
> depend on previous changes in 'master' that we don't want to propagate.
>
> Does that sound right?

Yes, and it's essentially the thing I wrote.

One can see easily how far the changes from master has been 
cherry-picked (by authorship date, or we could have in-repo text file 
describing the ported changes anyway). So if it's forgotten for some 
time, we can still catch up easily. The only thing is to mark somehow 
which changes are suitable for updating the stable branch (we probably 
only want to do it after some time of testing in master).

Porting the changes shouldn't be so difficult, because the non-intrusive 
important bugfixes IMO almost never depend on changing anything else.

As for security updates, I suppose some people who maintain NixOS 
servers watch these (through RSS?)... cherry-picking security updates is 
usually very easy (one-liner patches).


Vlada


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3251 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.science.uu.nl/pipermail/nix-dev/attachments/20130516/fbc32491/attachment.bin