[gmx-developers] remaining timeline for 5.0

[Mark Abraham]

On Mon, Feb 24, 2014 at 9:40 AM, Mark Abraham <mark.j.abraham at gmail.com>wrote:

> Hi,
>
> I've let this second deadline slip a bit - we did have a good merging
> party last week and there are only a few things left to sort out. Of those
> things that were either in gerrit in good shape in November, or affect core
> GROMACS strategy significantly, I think only the Verlet-free-energy,
> Verlet-LJPME, generic-SIMD and RNG-completion remain and they've been
> largely approved. So, I will roll the release candidate on Wednesday. Other
> stuff can get in, but they are a lower priority.
>

Update. Stuff's pretty much in order; major changes are all in. Jenkins was
more our friend than foe, this time! :-) There's still some minor stuff to
sort out tomorrow; Szilard's still finalizing the GPU support for some of
the newest NxN features, there's a bunch of test cases that passed but have
not yet been added, and a few minor features & changes that need a trifle
more Jenkins/review/whatever. Thanks for all the hard work, everyone.

I'm on the road the next few days, but I'll check in and when we seem like
we're good, I'll roll the tarballs.

Mark



>
> Looking forward, we will have a 4.6.6 shortly after that, declare
> release-4-6 branch closed for practical purposes. I am currently thinking
> of a 5.1 in May-June, e.g. beta May 1, rc June 1, release mid-June.
>
> Mark
>
>
> On Wed, Jan 29, 2014 at 11:26 AM, Mark Abraham <mark.j.abraham at gmail.com>wrote:
>
>> Hi devs,
>>
>> Many thanks for all your hard work. I've just made the release of the
>> second 5.0 beta.
>>
>> We still have a number of features close to ready to ship. We originally
>> planned for a February 1 shipping date, which hasn't worked out. That's OK
>> - it's much more important that we ship things that work well, even if a
>> few weeks late.
>>
>> So, I propose we use another fortnight for final merging of the remaining
>> content in gerrit. I don't expect that everything there will get in.
>> Ultimately that's up to you people, voting with your feet on what code you
>> develop, review and test! I propose that I will ship the release candidate
>> on Wednesday, February 12. Happy to move this either way if there's good
>> reason!
>>
>> At that time, a release-5-0-patches branch will appear on our git
>> servers. The only content that can go there must fix a bug or enhance
>> documentation. We will not be dribbling in refactoring and completion work,
>> such as we did during the 4.6 releases. master branch will remain the place
>> for new content, and the content from release-5-0 branch will be merged to
>> it. I plan to have a 5.1 release during this year, probably in spring.
>>
>> We will need another few weeks after feature completion, to go through
>> fixing and adding to the documentation, prompt tutorial authors and
>> third-party software developers to update for 5.0, test for simulation
>> performance on all the different kinds of systems we run on. I'll propose a
>> final release date at about the time of the release candidate.
>>
>> Cheers, and thanks again!
>>
>> Mark
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.sys.kth.se/pipermail/gromacs.org_gmx-developers/attachments/20140227/511497d9/attachment-0001.html>