<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
<br>
I plan to update the TNG version in 5.1 to the latest version of
the library. This should not affect functionality, but the code is
improved. I'll try to break it into smaller patches, but at least
one of them might be fairly big.<br>
<br>
Cheers,<br>
<br>
Magnus<br>
<br>
On 2014-11-26 18:18, Mark Abraham wrote:<br>
</div>
<blockquote
cite="mid:CAMNuMAQDBbHEvggX2Ahk15E0JOviJrcbCp2K42-9YZPVjP-VUQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hi,
<div><br>
</div>
<div>It's time we got organized for the next minor release.
Generally policy is unchanged - we do a feature-change release
at least once a year, and bugfix releases periodically on the
last minor/major release. An "extra" release for some special
purpose is negotiable.</div>
<div><br>
</div>
<div>I propose</div>
<div><br>
</div>
<div>* now:</div>
<div> + get code you want to be considered for 5.1 into
gerrit (tag the first line of the commit message [RFC] or
[WIP] if you know that the current state of the code is not a
serious candidate for merging)</div>
<div> + get your karma up by participating in review of
others' code</div>
<div> + reply to this email (or comment on your patches in
gerrit) to guide other people about what might be important
for them to review</div>
<div><br>
</div>
<div>* mid-January:<br>
</div>
<div> + release 5.0.x</div>
<div> + release 5.1-beta from whatever is the tip of master
branch at the time</div>
<div> + fork release-5-1 branch then (still open for
functionality changes until the 5.1-rc1 releases; gerrit's
feature for cherry picking between branches will make this
fork manageable)</div>
<div><br>
</div>
<div>* early-to-mid February:</div>
<div> + release 5.1-rc1</div>
<div> + close release-5-1 to new functionality, it remains
open for bug fixes, test cases, and documentation only</div>
<div> + test widely on any plausible machine and compiler for
portability and correctness</div>
<div> + release 5.1-rc[234] if that seems like a good idea</div>
<div><br>
</div>
<div>* mid-March:</div>
<div> + release 5.0.x for hopefully the last time, pretty
much close release-5-0 branch</div>
<div> + release 5.1</div>
<div> + remove the group cutoff scheme</div>
<div> + ...</div>
<div> + Profit!</div>
<div><br>
</div>
<div>Do speak up if you have a suggestion for a change / request
for special consideration / whatever. I've deliberately left
the Christmas period open for people who might want to do a
last code push at that time, but a huge patch landing without
warning on January 10... will probably get ignored by me.</div>
<div><br>
</div>
<div>Please note that things like ongoing contribution with
testing and code review are the primary things that might earn
an authorship on Gromacs papers (5.0 is still on my TODO list,
sorry) - adding some feature is awesome, but what reward
structure we can offer needs to focus on the large amount of
inglorious work that has to happen.</div>
<div><br>
</div>
<div>Things team Stockholm are actively working on that we'd
like to have ready for 5.1 (and the names of the primary
people involved)</div>
<div>* new DD communication support (Berk)</div>
<div>* enhancements to pull code (Berk)</div>
<div>* Verlet scheme support for tables, vacuum, Generalized
Born (Berk, Alfredo)</div>
<div>* GPU support for tabulated interactions (Alfredo)</div>
<div>* GPU acceleration of (at least) dihedral interactions
(Iman)</div>
<div>* combined FFTs for LJ-PME (Christian)</div>
<div>* offload of bonded interactions for enhancing load balance
(Mark)</div>
<div>* support for latest CUDA offerings (Szilard)</div>
<div>* OpenCL non-bonded support (mostly Anca from <a
moz-do-not-send="true" href="http://www.streamcomputing.eu">http://www.streamcomputing.eu</a>,
Mark)</div>
<div>* support for CPU-based SIMD on everything on the horizon
(Erik)</div>
<div><br>
</div>
<div>Like everything else, none of that's going to block
releases, but since 5.1 will be the last minor release with
the group cutoff scheme, feature completion of the Verlet
scheme will be an internal priority for development, review,
and testing. Full feature completion is unlikely to happen, so
support for twin-range multiple-time stepping, QM/MM, and
AdReS may disappear unless people want to put the work in.</div>
<div><br>
</div>
<div>There's a lot of code already in Gerrit awaiting review,
particularly from Teemu on the analysis tools. I need to help
out more there, but do check if he's fixing stuff that you
might care about!</div>
<div><br>
</div>
<div>If you're working on code that you might want to get into
5.1, speak up!</div>
<div><br>
</div>
<div>Happy reviewing!</div>
<div><br>
</div>
<div>Mark</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>