[gmx-developers] impending 5.1.4 and 2016.1, and new bugfix policy

Schulz, Roland roland.schulz at intel.com
Fri Sep 2 18:35:11 CEST 2016


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?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.sys.kth.se/pipermail/gromacs.org_gmx-developers/attachments/20160902/62736839/attachment.html>

More information about the gromacs.org_gmx-developers mailing list