Re: [OMPI devel] Open MPI 3.x branch naming

+1 from IBM on removing the v3.x branch sooner rather than later. I've switched our MTT and Jenkins setups - so we should be in good shape. On Wed, May 31, 2017 at 9:57 AM, Barrett, Brian via devel < devel@lists.open-mpi.org> wrote: > > > On May 31, 2017, at 7:52 AM, r...@open-mpi.org wrote: >

Re: [OMPI devel] Open MPI 3.x branch naming

> On May 31, 2017, at 7:52 AM, r...@open-mpi.org wrote: > >> On May 31, 2017, at 7:48 AM, Jeff Squyres (jsquyres) >> wrote: >> >> On May 30, 2017, at 11:37 PM, Barrett, Brian via devel >> wrote: >>> >>> We have now created a v3.0.x branch based

Re: [OMPI devel] Open MPI 3.x branch naming

> On May 31, 2017, at 7:48 AM, Jeff Squyres (jsquyres) > wrote: > > On May 30, 2017, at 11:37 PM, Barrett, Brian via devel > wrote: >> >> We have now created a v3.0.x branch based on today’s v3.x branch. I’ve >> reset all outstanding v3.x PRs

Re: [OMPI devel] Open MPI 3.x branch naming

On May 30, 2017, at 11:37 PM, Barrett, Brian via devel wrote: > > We have now created a v3.0.x branch based on today’s v3.x branch. I’ve reset > all outstanding v3.x PRs to the v3.0.x branch. No one has permissions to > pull into the v3.x branch, although I’ve left

Re: [OMPI devel] Open MPI 3.x branch naming

On May 31, 2017, at 9:59 AM, Jeff Squyres (jsquyres) wrote: > >https://www.open-mpi.org/nightly/v3.0/ Ah, you actually already moved it to: https://www.open-mpi.org/nightly/v3.0.x/ Got it; thanks. -- Jeff Squyres jsquy...@cisco.com

Re: [OMPI devel] Open MPI 3.x branch naming

Brian -- Do we need to change the nightly snapshot URL from https://www.open-mpi.org/nightly/v3.x/ to https://www.open-mpi.org/nightly/v3.0/ > On May 30, 2017, at 11:37 PM, Barrett, Brian via devel > wrote: > > We have now created a v3.0.x branch based

Re: [OMPI devel] Open MPI 3.x branch naming

We have now created a v3.0.x branch based on today’s v3.x branch. I’ve reset all outstanding v3.x PRs to the v3.0.x branch. No one has permissions to pull into the v3.x branch, although I’ve left it in place for a couple of weeks so that people can slowly update their local git repositories.

Re: [OMPI devel] Open MPI 3.x branch naming

For various reasons, the rename didn’t happen on Saturday. It will, instead, happen tonight at 6:30pm PDT. Sorry for the delay! Brian On May 23, 2017, at 9:38 PM, Barrett, Brian > wrote: All - Per the discussion on today’s telecon, we’re

Re: [OMPI devel] Open MPI 3.x branch naming

All - Per the discussion on today’s telecon, we’re going to rename the branch Saturday (5/27) morning (Pacific time). We’ll branch v3.0.x from v3.x and update all the nightly builds and web pages. I’m going to push through all the PRs on 3.x which are currently outstanding, but please be

Re: [OMPI devel] Open MPI 3.x branch naming

+1 Go for it :-) > On May 5, 2017, at 2:34 PM, Barrett, Brian via devel > wrote: > > To be clear, we’d do the move all at once on Saturday morning. Things that > would change: > > 1) nightly tarballs would rename from openmpi-v3.x--.tar.gz > to

Re: [OMPI devel] Open MPI 3.x branch naming

To be clear, we’d do the move all at once on Saturday morning. Things that would change: 1) nightly tarballs would rename from openmpi-v3.x--.tar.gz to openmpi-v3.0.x--.tar.gz 2) nightly tarballs would build from v3.0.x, not v3.x branch 3) PRs would need to be filed against v3.0.x 4) Both

Re: [OMPI devel] Open MPI 3.x branch naming

As a maintainer of non-MTT scripts that need to know the layout of the directories containing nighty and RC tarball, I also think that all the changes should be done soon (and all together, not spread over months). -Paul On Fri, May 5, 2017 at 2:16 PM, George Bosilca wrote:

Re: [OMPI devel] Open MPI 3.x branch naming

If we rebranch from master for every "major" release it makes sense to rename the branch. In the long term renaming seems like the way to go, and thus the pain of altering everything that depends on the naming will exist at some point. I'am in favor of doing it asap (but I have no stakes in the

[OMPI devel] Open MPI 3.x branch naming

Hi everyone - We’ve been having discussions among the release managers about the choice of naming the branch for Open MPI 3.0.0 as v3.x (as opposed to v3.0.x). Because the current plan is that each “major” release (in the sense of the three release points from master per year, not necessarily