[gmx-developers] Plans for release-2019

[Mark Abraham]

Hi devs,

As summer starts, and perhaps people head off on holidays, I thought I'd
remind you all of the upcoming important dates for content intended for the
GROMACS 2019 release.

As usual, we're doing a time-based release, so your changes need to have
progressed well so that people will have time to review and integrate
before the Oct 15 beta release. If you need discussion time with core
developers, please get in touch NOW, as we will only get less available
hereafter :-) Code arriving in gerrit in September that gets the feedback
"wouldn't this alternative architecture be clearer / follow style / be more
extensible / be more maintainable / run faster" will likely not be able to
be considered further, given our limited resources.

Reminder - the current guidelines for getting code contributed to GROMACS
is here:
http://jenkins.gromacs.org/job/Documentation_Nightly_master/javadoc/dev-manual/contribute.html

Mark

On Mon, Jan 22, 2018 at 10:02 AM Erik Lindahl <erik.lindahl at gmail.com>
wrote:

> Hi,
>
> Based on discussions both in the team and at the Gromacs developer
> conferences, we've converged to an early release schedule that we'd like to
> share with everyone.
>
> As we've all seen, it simply doesn't work to have feature targets for
> releases, since that inevitably leads to slipping deadlines when we
> underestimate both the implementation and review work.
>
> Instead, this time we will try to have firm date-based targets and make
> sure we put out the release late december. Based on that, we simply count
> backwards to come up with deadlines for various other steps:
>
>
> Oct 15: Release-2018 branch is created in Gerrit, and first beta.
> Nov 1: Second beta
> Nov 15: Third beta
> Dec 1: rc1
> Dec 15: (maybe) rc2
> Dec 31: Release
>
> These are the only really firm dates. However, it also means that any
> significant change that should be in the release should not only have been
> pushed to Gerri, but it must be *merged* by Oct 15.
>
> It's likely that everyone will be quite busy the last few weeks. In the
> end it is up to everyone to prioritise changes we want to go in, but if you
> have stuff that you want to go in, you should likely plan to be a really
> good Gerrit citizen and build karma by reviewing other changes :-)
>
> And, in particular: For large changes touching lots of files, you should
> plan that it can take months to go through review, so those should likely
> be in review already late summer.
>
> Finally, to facilitate the design review and reduce the amount of changes
> required in code review, we've decided it's a good idea for any large
> change to start with a Gerrit thread to discuss the design. That's not
> *formally* required, but if you don't have it, you should expect to instead
> get requests for large design changes during feedback :-)
>
> Cheers,
>
> Erik
>
>
>
>
> --
> Erik Lindahl <erik.lindahl at dbb.su.se>
> Professor of Biophysics, Dept. Biochemistry & Biophysics, Stockholm
> University
> Science for Life Laboratory, Box 1031, 17121 Solna, Sweden
> --
> 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...
URL: <http://maillist.sys.kth.se/pipermail/gromacs.org_gmx-developers/attachments/20180622/a7b859df/attachment.html>