[gmx-developers] Plans for release-2019
Erik Lindahl
erik.lindahl at gmail.com
Mon Jan 22 16:48:47 CET 2018
Good catch - that should definitely be redmine!
On 22 January 2018 at 16:17:52, Kutzner, Carsten (ckutzne at gwdg.de) wrote:
> Hi,
>
> On 22. Jan 2018, at 10:01, 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.
>
> Gerrit or rather Redmine?
>
> Best,
> Carsten
>
> 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.
>
>
> --
> 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.
>
--
Erik Lindahl <erik.lindahl at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.sys.kth.se/pipermail/gromacs.org_gmx-developers/attachments/20180122/500f1f71/attachment.html>
More information about the gromacs.org_gmx-developers
mailing list