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 controversia
Hi,
As an alternative idea: What about using branches to mark "stable" and
"development"?
Tags are for fixed versions and so users will not receive updates unless they
update their update scripts manually?!
When "development" is stable just merge into "stable".
Regards
Christoph
PS: For all in
+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) bra
