On Oct 17, 2014, at 6:05 AM, Jed Brown <j...@jedbrown.org> wrote: > You can get them locally by fetching from open-mpi/ompi-release, but the > only tag in open-mpi/ompi is called "dev" and on a seemingly arbitrary > commit. Isn't that awkward already, and more so with each passing year? > Release tags in the development repository are useful to determine which > released versions have a feature or bug.
I'm not sure what you're asking. Releases are cut from the release branches, which are in the ompi-release repo. They are tagged appropriately for each release. The ompi repo only contains the master branch. Releases are not made from master, and therefore it doesn't make sense to tag it with release tags. master is therefore not (directly) related to any given release. The "dev" tag is there so that we can make nightly tarballs with a logical sequence (via "git describe"). The "dev" tag is basically there as the point at which we converted to git. We could have put it back at the beginning of time (i.e., equivalent to SVN r1 (i.e., the first CVS commit!)), but it didn't really matter, so we just opted for a dev that resulted in a smaller "git describe" number. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
