Hi devs,<div><br></div><div>Here's another reminder, now that most people are back from holidays.</div><div><br></div><div>For code for the GROMACS 2019 release, to have an impact on users (or hardware sales ;-)), the design and architecture discussion should be pretty much over. Code needs to hit Gerrit ASAP, with the usual caveats about modularity, conformance to the style guide, with unit tests, developer documentation and user documentation. On Oct 15 we will roll the beta!</div><div><br></div><div>I will try to get to get back to several of you this week :-) </div><div><br></div><div>Mark</div><div><br><div class="gmail_quote"><div dir="ltr">On Fri, Jun 22, 2018, 17:40 Mark Abraham <<a href="mailto:mark.j.abraham@gmail.com">mark.j.abraham@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi devs,<div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>Reminder - the current guidelines for getting code contributed to GROMACS is here: <a href="http://jenkins.gromacs.org/job/Documentation_Nightly_master/javadoc/dev-manual/contribute.html" target="_blank">http://jenkins.gromacs.org/job/Documentation_Nightly_master/javadoc/dev-manual/contribute.html</a></div></div><div dir="ltr"><div><br></div><div>Mark<br><br><div class="gmail_quote"><div dir="ltr">On Mon, Jan 22, 2018 at 10:02 AM Erik Lindahl <<a href="mailto:erik.lindahl@gmail.com" target="_blank">erik.lindahl@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>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.</div><div><br></div><div>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.</div><div><br></div><div>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:</div><div><br></div><div><br></div><div>Oct 15: Release-2018 branch is created in Gerrit, and first beta.</div><div>Nov 1: Second beta</div><div>Nov 15: Third beta</div><div>Dec 1: rc1</div><div>Dec 15: (maybe) rc2</div><div>Dec 31: Release</div><div><br></div><div>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.</div><div><br></div><div>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 :-)</div><div><br></div><div>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.</div><div><br></div><div>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 :-)</div><div><br></div><div>Cheers,</div><div><br></div><div>Erik</div><div><br></div><div><br></div><div><br></div><div><div><br></div>-- <br><div class="m_-7033182494877797727m_4633884529902000845gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Erik Lindahl <<a href="mailto:erik.lindahl@dbb.su.se" target="_blank">erik.lindahl@dbb.su.se</a>></div><div>Professor of Biophysics, Dept. Biochemistry & Biophysics, Stockholm University</div><div>Science for Life Laboratory, Box 1031, 17121 Solna, Sweden</div></div></div></div></div></div></div></div></div>
</div></div>
-- <br>
Gromacs Developers mailing list<br>
<br>
* Please search the archive at <a href="http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List" rel="noreferrer" target="_blank">http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List</a> before posting!<br>
<br>
* Can't post? Read <a href="http://www.gromacs.org/Support/Mailing_Lists" rel="noreferrer" target="_blank">http://www.gromacs.org/Support/Mailing_Lists</a><br>
<br>
* For (un)subscribe requests visit<br>
<a href="https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers" rel="noreferrer" target="_blank">https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers</a> or send a mail to <a href="mailto:gmx-developers-request@gromacs.org" target="_blank">gmx-developers-request@gromacs.org</a>.</blockquote></div></div></div>
</blockquote></div></div>