Re: [MTT devel] MTT: let's use git tags

2014-06-30 Thread Jeff Squyres (jsquyres)
ve Goodell (dgoodell)" <dgood...@cisco.com> > To: "Development list for the MPI Testing Tool" <mtt-de...@open-mpi.org> > Sent: Thursday, June 26, 2014 2:47:35 PM > Subject: Re: [MTT devel] MTT: let's use git tags > > Published Git tags are *not* movable (by d

Re: [MTT devel] MTT: let's use git tags

2014-06-30 Thread Christoph Niethammer
ing gpg fortifying them even more. ;) > > - Original Message - > From: "Dave Goodell (dgoodell)" <dgood...@cisco.com> > To: "Development list for the MPI Testing Tool" <mtt-de...@open-mpi.org> > Sent: Thursday, June 26, 2014 2:47:35 P

Re: [MTT devel] MTT: let's use git tags

2014-06-27 Thread Christoph Niethammer
odell (dgoodell)" <dgood...@cisco.com> To: "Development list for the MPI Testing Tool" <mtt-de...@open-mpi.org> Sent: Thursday, June 26, 2014 2:47:35 PM Subject: Re: [MTT devel] MTT: let's use git tags Published Git tags are *not* movable (by design). You're better off making

Re: [MTT devel] MTT: let's use git tags

2014-06-26 Thread Jeff Squyres (jsquyres)
I've thought about this a little, and I'm still inclined to use the simple/lazy method of tags on master. Some random points, in no particular order: 1. master should always be for development, IMHO. If we start using a multi-branch scheme, then the branches should be for releases, etc. 2.

Re: [MTT devel] MTT: let's use git tags

2014-06-24 Thread Gilles Gouaillardet
+1 for using branches : branch usage is less error prone plus git makes branching unexpensive. as far as i am concerned, i'd rather have the default master branch is the for the "stable" version and have one branch called devel (or dev, or whatever) : - git clone => get the stable (aka master)

[MTT devel] MTT: let's use git tags

2014-06-24 Thread Jeff Squyres (jsquyres)
The topic came up today that MTT sometimes has bugs, particularly w.r.t. ongoing MTT development. It seems like we should use git tags to let the OMPI/testing community know which tag they should be using (vs. HEAD). To that end, I have created a "v3.0.0" tag that exists before the