On 19/05/15 05:11, Jeff Squyres (jsquyres) wrote:
> We've reached internal consensus, and would like to present this to the
> larger community for feedback.
My gut feeling is that this is very good; from a cluster admin point of
view it means we keep a system tracking one level up from where we
Hi Mark,
ideally, we would like to use a single repository with the following
constraints :
- all Open MPI developers can commit to the master
- only Release Manager and Gatekeepers can commit to the release branch
(v1.8, ...)
unfortunatly, github does not (yet ?) implement per branch access
Hi Jeff, all,
Thanks for bringing this to the wider community.
I hope this will eventually address my main concern: the relatively old
versions that get deployed on HPC systems around the world, which I assume
is/was because of the "odd ;-)" numbering.
What I didn't see in the doc, will you co
Devel community --
Over the past few weeks, the core Open MPI members have been internally
discussing a proposal to change to the version numbering of Open MPI public
releases. We've reached internal consensus, and would like to present this to
the larger community for feedback.
Here's the sh
