[gmx-users] stable branch using git

[Sikandar Mashayak]

Thanks Justin and Mark

I think I would checkout and create a branch from v4.6 tag.

One more thing, would it be an issue if I install mulitple
version's/branche's binaries and libraries in the same folder with branch
specific suffixes to distinguish between them?

Thanks
Sikandar


On Wed, May 1, 2013 at 3:25 AM, Mark Abraham <mark.j.abraham at gmail.com>wrote:

> On Wed, May 1, 2013 at 2:50 AM, Sikandar Mashayak <symashayak at gmail.com
> >wrote:
>
> > Hi Justin
> >
> > Thanks for explanation. But I am a bit confused because I am new to git.
> > When I check out release-4-6 branch, the source code should be the same
> as
> > the one in tarball from Gromacs website, right?
>
>
> No. The tarball is made from a particular commit and that commit has a git
> tag identifying it (though I did mess that up slightly for 4.6.1). History
> then continues in the branch. Its head commit only coincides with a tag
> immediately after a release.
>
>
> > When I run git status I get
> > # On branch release-4-6
> > nothing to commit (working directory clean), I believe that means I have
> > the released version of the code.
> >
>
> No, you have the head of the development branch from which releases are
> currently being made. Do check out some git tutorial material.
>
> The reason I am doing this is that I want to have just one directory for
> > gromacs with subdirectories for its src, build and binaries. And in
> future,
> > instead of downloading new releases, I want to just pull the changes and
> > re-build.
>
>
> In principle, that workflow can work, but you need to (e.g.) use "git
> checkout v4.6" to check out the commit we tagged when we built the 4.6
> tarball.
>
>
> > Also, I plan to clone the same src directory on my different
> > machines, so that I can have the same version on all machines.
>
>
> You can do similar things with the tarball, so I don't see what you're
> gaining :-)
>
> Mark
>
> Hopefully,
> > in the future I may start doing some modifications here n there.
> >
> > Thanks
> > Sikandar
> >
> >
> > On Tue, Apr 30, 2013 at 7:38 PM, Justin Lemkul <jalemkul at vt.edu> wrote:
> >
> > >
> > >
> > > On 4/30/13 8:28 PM, Sikandar Mashayak wrote:
> > >
> > >> Thanks Justin.
> > >>
> > >> I replaced release-4-5-patches with release-4-6 while checking out the
> > >> branch.
> > >> When I installed it and checked the version string I get VERSION
> > >> 4.6.2-dev-20130429-d13fc48.
> > >> Does that mean I got the version which is still under development and
> > not
> > >> stable and tested?
> > >> Should I be concerned using it to do a production run?
> > >>
> > >>
> > > We generally discourage anyone from doing production work with anything
> > > that's not an official release.  Anything you pull from the git repo
> is a
> > > work in progress.  Periodic releases are generated when the code is
> > > believed to be production-ready.  We do code review and build testing
> and
> > > each patch is as reliable as we believe it to be :)
> > >
> > > The reference to a "stable branch" is probably a bit misleading, but
> the
> > > master branch is currently undergoing large-scale changes, leaving it
> > > perhaps a bit more "unstable" than release-4-6.  The release-4-6 branch
> > is
> > > the one from which the development team is producing actual releases.
> > >
> > > If you want the latest version, just download the 4.6.1 tarball from
> the
> > > Gromacs website.  Version 4.6.2 should be out fairly soon, but there
> are
> > > some issues that are still being cleaned up.
> > >
> > >
> > > -Justin
> > >
> > > --
> > > ==============================**==========
> > >
> > > Justin A. Lemkul, Ph.D.
> > > Research Scientist
> > > Department of Biochemistry
> > > Virginia Tech
> > > Blacksburg, VA
> > > jalemkul[at]vt.edu | (540) 231-9080
> > > http://www.bevanlab.biochem.**vt.edu/Pages/Personal/justin<
> > http://www.bevanlab.biochem.vt.edu/Pages/Personal/justin>
> > >
> > > ==============================**==========
> > > --
> > > gmx-users mailing list    gmx-users at gromacs.org
> > > http://lists.gromacs.org/**mailman/listinfo/gmx-users<
> > http://lists.gromacs.org/mailman/listinfo/gmx-users>
> > > * Please search the archive at http://www.gromacs.org/**
> > > Support/Mailing_Lists/Search<
> > http://www.gromacs.org/Support/Mailing_Lists/Search>before posting!
> > > * Please don't post (un)subscribe requests to the list. Use the www
> > > interface or send it to gmx-users-request at gromacs.org.
> > > * Can't post? Read http://www.gromacs.org/**Support/Mailing_Lists<
> > http://www.gromacs.org/Support/Mailing_Lists>
> > >
> > --
> > gmx-users mailing list    gmx-users at gromacs.org
> > http://lists.gromacs.org/mailman/listinfo/gmx-users
> > * Please search the archive at
> > http://www.gromacs.org/Support/Mailing_Lists/Search before posting!
> > * Please don't post (un)subscribe requests to the list. Use the
> > www interface or send it to gmx-users-request at gromacs.org.
> > * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
> >
> --
> gmx-users mailing list    gmx-users at gromacs.org
> http://lists.gromacs.org/mailman/listinfo/gmx-users
> * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/Search before posting!
> * Please don't post (un)subscribe requests to the list. Use the
> www interface or send it to gmx-users-request at gromacs.org.
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
>