[Nix-dev] Preparing for 14.04

[Shea Levy]

Hi all,

I've now gone through all of the open nixpkgs issues and tried
to label them correctly. Please take a look at issues labeled "bug",
issues labeled "documentation", and *especially* issues with the "14.04"
milestone. If you have comments or, better yet, are willing to take
ownership of an issue, please do! Of particular importances is #2112[1]:
If you've made or know of any significant change since 13.10 that isn't
yet documented, *please* make note of it there so we can be sure to
capture it. Note that I've been through a lot of issues and almost
certainly made errors on some of them, so if something is labeled wrong
or has the wrong milestone please let me know or fix it.

The current plan is to branch on 4/18 and use the next week for testing
and bugfixes, so please take that into account as you start addressing
issues. Also note that if you need some fix or feature to be part of the
stable release, create the issue and mark it for 14.04 soon!

Cheers,
Shea

[1]: https://github.com/NixOS/nixpkgs/issues/2112

On Wed, Apr 02, 2014 at 05:26:24PM -0400, Shea Levy wrote:
> Hi all,
> 
> April is upon us, and April Fool's Day is behind us, and that means it's
> time for the next NixOS stable release! I'm going to be going through
> the open issues and marking some with the 14.04 milestone and others
> with the 14.10, and if you have something you'd really like to get into
> the release or you know for sure will have to wait, please do the same.
> And please also assign yourself (or, if you're not a team collaborator
> on github, mention you'll do the work in the comments) to any issues you
> want to tackle. In particular, we'll need anyone who worked on a major
> change in the past several months to pitch in on
> https://github.com/NixOS/nixpkgs/issues/2112.
> 
> If you have any thoughts on how the release process should go, please
> chime in! I think collecting a list of github issues, pruning down to
> the ones we can realistically finish, and then just doing the work is
> one way to do it, but there may be better approaches out there.
> 
> ~Shea
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev