Hi Jason,
This is good BUT I think we ultimately need better versioning that this. For
example the GPU code I have v1.0 (AMBER 10), V2.0 AMBER 11 release, V2.1
AMBER 11 bugfix8 and V2.2 AMBER 11 bugfix17. I think we need to come up with
a better AND consistent way of versioning ALL of our code.
I also think we should be consistent across everything. Thus everything
released as AMBER 12 - an I still maintain that AMBER 12 should be a
complete package and we break out the free sections for download later (call
them AMBERLite or AMBERTools) - Thus everything should be V12.0.000 at the
point of release. Then any bugfixes should increment this. Although I'm
still not sure the best way to do this. Perhaps we just have V12.DATE where
date is the date of the latest bugfix. - I think this should be distribution
wide though. With the AMBER and AMBERTools merged together as AMBER 12 -
Then we only need one bugfix tree. WOW!!!, what a novel idea... The script
for applying the bugfixes, like the compilation scripts can be made smart
and it can detect if your tree contains a FULL AMBER 12 or an AMBERLite 12.
All the best
Ross
> -----Original Message-----
> From: git repository hosting [mailto:gitosis.amber.sdsc.edu]
> Sent: Thursday, November 03, 2011 10:52 AM
> To: cvs-notification.ambermd.org
> Subject: [CVS-notification] [GIT] git repository for AMBER:
>
>
> The project "git repository for AMBER":
>
> The branch, master has been updated
> via d7c8b50ffca0c6ad8f9fea0a03b4fa6e7b7eba5f (commit)
> via f4fbe037d14c747ed46a4d49607bba12d7ca7a97 (commit)
> from aead22f79ee54003b46bea9744e800d4e67647b2 (commit)
>
>
> - Log -----------------------------------------------------------------
> commit d7c8b50ffca0c6ad8f9fea0a03b4fa6e7b7eba5f
> Merge: f4fbe03 aead22f
> Author: Jason Swails <jason.swails.gmail.com>
> Date: Thu Nov 3 13:11:02 2011 -0400
>
> Merge branch 'master' of git.ambermd.org:amber
>
> commit f4fbe037d14c747ed46a4d49607bba12d7ca7a97
> Author: Jason Swails <jason.swails.gmail.com>
> Date: Thu Nov 3 13:09:43 2011 -0400
>
> Add an MPI-safe --version/-V flag to sander and pmemd.
> In pmemd, VERSION is in gbl_constants.fpp. In sander, VERSION is in
> multisander.f. This is the only variable that needs to be changed for
> version updates.
>
> -----------------------------------------------------------------------
>
> Summary of changes:
> src/pmemd/src/gbl_constants.fpp | 5 ++-
> src/pmemd/src/get_cmdline.fpp | 37 +++++++++++++++++++++---
> src/pmemd/src/master_setup.fpp | 16 ++++++++---
> src/pmemd/src/multipmemd.fpp | 11 +++++++-
> src/pmemd/src/pmemd.fpp | 17 ++++++++---
> src/pmemd/src/pmemd_lib.fpp | 58
> +++++++++++++++++++++++++++++++++++++++
> src/sander/mdfil.f | 45 +++++++++++++++++++++++++++++-
> src/sander/multisander.f | 17 ++++++++++-
> 8 files changed, 185 insertions(+), 21 deletions(-)
>
> --
> git repository for AMBER
>
> _______________________________________________
> Cvs-notification mailing list
> Cvs-notification.ambermd.org
> http://lists.ambermd.org/mailman/listinfo/cvs-notification
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Thu Nov 03 2011 - 11:30:07 PDT
