No no no - Scott and I have a bunch of code optimization to do that has
not been possible without the tree frozen - so once it is frozen we will
complete this. It is unrelated to features and will include the extensive
testing and bugfixing needed prior to release so it fits in correctly.
Hindsight says we probably should have had a feature freeze about 2 months
ago to force all these last minute changes then.
I'd rather get this done between now and release than having to have a big
bugfix update a month after release.
On 2/12/14, 3:03 PM, "Jason Swails" <jason.swails.gmail.com> wrote:
>On Wed, Feb 12, 2014 at 5:35 PM, Ross Walker <ross.rosswalker.co.uk>
>wrote:
>
>>
>> The problem is how to deal with this and yes I fully agree ALL of this
>> should have gone in over the last year. I vote once things are locked on
>> Friday we have at least another 6 weeks to work on cleaning up pmemd and
>> optimizing things ready for release. This may include gutting some
>>stuff.
>> Otherwise yes we will just end up with a slow pmemd. :-(
>>
>
>Nooooooo. "We're just about to release, so let's do a major code
>overhaul."
>
>Famous last words. I vote the "overhaul" comes after release so it's not
>rushed and sloppy (nor does it push back Amber 14 to Amber 15). The time
>between the freeze and the release should be working out minor issues on
>different platforms, not cramming a bunch of issues in just before the
>deadline so we can hastily fix them as they manifest in the tests. I've
>spent a _lot_ of time fixing bugs post-freeze and pre-release; I'm not a
>fan.
>
>--
>Jason M. Swails
>BioMaPS,
>Rutgers University
>Postdoctoral Researcher
>_______________________________________________
>AMBER-Developers mailing list
>AMBER-Developers.ambermd.org
>http://lists.ambermd.org/mailman/listinfo/amber-developers
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Wed Feb 12 2014 - 15:30:04 PST
