<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
Just a note - we are planning to have 4.5.5 out in two weeks (around
Aug. 15th) time when we'll fork-off the 4.6 branch for adding new
functionality.<br>
<br>
Cheers,<br>
Rossen<br>
<br>
On 6/22/11 1:10 PM, Rossen Apostolov wrote:
<blockquote cite="mid:4E01CD94.8050205@kth.se" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Hi,<br>
<br>
We are preparing for a new maintenance release 4.5.5. It will fix
critical open issues with previous releases, so please file your
reports in redmine.gromacs.org by the end of June.<br>
<br>
After the 4.5.5 release, the stable branch will be frozen for
bugfixes only, and new functionality will be added to a new
release-4-6-patches branch, a fork of release-4-5-patches right
after 4.5.5.<br>
<br>
Currently the plan is to have in 4.6:<br>
<ul>
<li>faster native GPU implementation supporting most of current
Gromacs features</li>
<li>collective I/O</li>
<li>lambda dynamics and other free energy extensions</li>
<li>AdResS (<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="http://www.mpip-mainz.mpg.de/%7Epoma/multiscale/adress.php">http://www.mpip-mainz.mpg.de/~poma/multiscale/adress.php</a>)</li>
<li>advanced rotational pulling</li>
<li>file history</li>
<li>several new tools<br>
</li>
<li>autoconf removed - support for building only with CMake</li>
</ul>
Code from contributors will be considered for inclusion also but
it's necessary that<br>
<ul>
<li>comes with support for the code in future releases, e.g.
port it to the completely new C++ structure in the 5.0 release
and maintain it after<br>
</li>
<li>builds against 4.5.5</li>
<li>produces scientifically reliable results</li>
<li>works in parallel and doesn't affect the performance</li>
<li>comes with regression test sets for the new features<br>
</li>
<li>has the necessary documentation for usage</li>
</ul>
After 4.5.5 bug fixes need to be applied as:<br>
<ul>
<li>bugs in 4.5.5:</li>
<ul>
<li>fix in 4.5.5 -> fix in 4.6 -> fix in master</li>
</ul>
<li>bugs in the new features introduced in 4.6:</li>
<ul>
<li> fix in 4.6 -> fix in master</li>
</ul>
</ul>
<br>
The plan is to have 4.5.5 around end of July, and 4.6-gamma a
month later.<br>
<br>
Rossen<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
</body>
</html>