[gmx-developers] Plans for GROMACS 2016 release
erik.lindahl at gmail.com
Sun May 8 11:24:20 CEST 2016
Sorry for cc:ing a bunch of you (everybody with recent patches in Gerrit) explicitly too, but that’s just in case you use filters to put mailing list traffic in separate folders.
And I’ll just send a reminder for Mark’s message: If you want any new *very small* patches in 2016, they have to be approved in Gerrit today.
From tomorrow and a month forward, we should try focus our efforts on fixing as many bugs as possible in the release branch. Since I expect the load on the Jenkins CI/testing environment can get a bit high, once we have branched off, try to avoid uploading new versions of changes that are not bugfixes for the release branch unless you see that the load on Jenkins is low. The faster we get that phase done, the faster we can get back to normal development.
> On 04 May 2016, at 15:22, Mark Abraham <mark.j.abraham at gmail.com> wrote:
> Apologies for my delays here - many tasks have come up in the last 2 months that have needed lots of my time and focus. I'll have time to do the beta release on Monday May 9. Last drinks in gerrit!
> On Thu, Feb 4, 2016 at 12:13 PM Mark Abraham <mark.j.abraham at gmail.com <mailto:mark.j.abraham at gmail.com>> wrote:
> Hi devs,
> I propose a much lower-key release cycle than we have had in the past. It has dragged out too long and been too stressful for all involved :-)
> On April 1, I'll fool you all and roll a release candidate from master branch HEAD, and branch release-2016 immediately. If stuff isn't merged yet, then it isn't. The one thing that can't get me fired is releasing quality code at a predictable time, and the fewer things we submit to master branch, the easier it is for me to do that job! ;-) If you need/want some code in the release, then it needs to be in Gerrit with Doxygen, user docs and test cases... real soon now! And get your reviewers interested in advance, because they're all super busy people. :-)
> Then May 1, when the worst of the known issues are handled, I'll release GROMACS 2016. That'll then give us ~6 weeks before Swedes disappear on summer holidays if we need to do 2016.1 release then.
> Our long beta phases for 4.6, 5.0 and 5.1 haven't been terribly effective at finding development bugs (e.g. I broke multi-rank-per-simulation replica exchange before 5.1, and nobody noticed until the code had been out for several months; there's various other such examples). Instead, I'll use that month to prioritise the kind of exhaustive testing that has been too onerous for me to contemplate doing after a multi-month beta phase. Hopefully some of my new testing infrastructure can be reviewed and integrated by then, to make that easier.
> I am planning to do a GROMACS 2016 paper, and those of you who've been working actively and regularly on the wider code base will be most welcome to help write that!
> Happy coding and reviewing!
> Gromacs Developers mailing list
> * Please search the archive at http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before posting!
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
> * For (un)subscribe requests visit
> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers or send a mail to gmx-developers-request at gromacs.org.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gromacs.org_gmx-developers