[gmx-developers] impending 5.1.4 and 2016.1, and new bugfix policy
mark.j.abraham at gmail.com
Wed Sep 7 11:24:59 CEST 2016
We have a handful of minor fixes to amber03 and oplsaa charges (either
propagating ancient fixes made upstream, or handling problems we made
through duplicate definitions) that would be good to include in 5.1.4.
Review won't take long, please!
On Fri, Sep 2, 2016 at 6:35 PM Schulz, Roland <roland.schulz at intel.com>
> This will also mean that come next release phase, we will close
> release-2016 for the duration of the release phase. Once we release 2017,
> probably we'll have bug fixes that make sense to backport to release-2016,
> but clearly we can't do more than one thing at a time efficiently.
> *[RS] I’m not sure how this follows from the rest. If backporting is the
> responsibility of the author (or whoever else is interested in doing so)
> why would we disallow him to backport already during the release phase by
> closing the branch? Or do you suggest we just close it to anything other
> than backports/cherry-picks?*
> Gromacs Developers mailing list
> * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
> * For (un)subscribe requests visit
> 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