Hi Dave,
Just to make sure ... should we change "amber.lyx" in the
amber17-with-patches or the master branch?
All the best,
Ray
--
Ray Luo, Ph.D.
Professor of Structural Biology/Biochemistry/Biophysics,
Chemical Physics, Biomedical Engineering, and Chemical Engineering
Department of Molecular Biology and Biochemistry
University of California, Irvine, CA 92697-3900
On Tue, Mar 28, 2017 at 11:37 AM, David Case <david.case.rutgers.edu> wrote:
> Hi everyone:
>
> 1. The first release candidate for AmberTools17 is here:
>
> http://ambermd.org/downloads/AmberTools17.28mar17.tar.bz2
>
> This *should* be the same as what is in the amber17-with-patches branch
> at git.ambermd.org. But use the tarball for testing, since that is
> what users will actually download.
>
> 2. Once we are ready to release, the "update_amber --upgrade" script will
> be functional, but this is not ready yet for testing.
>
> 3. You may resume making commits to the master branch at git.ambermd.org.
> You *must* email me if you want to propose any changes what will
> be released as a part of AmberTools17.
>
> **Exception** Please to not push changes to Amber.lyx or amber.bib
> that should not be in the AmberTools17 release. There is still time
> to make updates to those files that *will* be a part of the upcoming
> release
>
> 4. Hai: I think you should start building the binary AmberTools releases
> using the amber17-with-patches branch, not the master branch....thx.
>
> ...thx...dac
>
>
> _______________________________________________
> 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 Mar 29 2017 - 14:00:02 PDT