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
> <[email protected]> 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 it in place for a couple of
> weeks so that people can slowly update their local git repositories. The
> nightly tarballs are still building, but everything else should be setup.
> Yell when you figure out what I missed.
>
> Brian
>
>> On May 30, 2017, at 2:44 PM, Barrett, Brian <[email protected]> wrote:
>>
>> 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 <[email protected]> wrote:
>>>
>>> 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 careful about
>>> pushing together complex PRs on 3.x for the rest of the week. If something
>>> is submitted before Saturday and doesn’t make it due to reviews, you’ll
>>> have to resubmit.
>>>
>>> Brian
>>>
>>>> On May 5, 2017, at 4:21 PM, [email protected] wrote:
>>>>
>>>> +1 Go for it :-)
>>>>
>>>>> On May 5, 2017, at 2:34 PM, Barrett, Brian via devel
>>>>> <[email protected]> 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-<date>-<git
>>>>> hash>.tar.gz to openmpi-v3.0.x-<date>-<git hash>.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 https://www.open-mpi.org/nightly/v3.x/ and
>>>>> https://www.open-mpi.org/nightly/v3.0.x/ would work for searching for new
>>>>> nightly tarballs
>>>>>
>>>>> At some point in the future (say, two weeks), (4) would change, and only
>>>>> https://www.open-mpi.org/nightly/v3.0.x/ would work. Otherwise, we need
>>>>> to have a coordinated name switch, which seems way harder than it needs
>>>>> to be. MTT, for example, requires a configured directory for nightlies,
>>>>> but as long as the latest_tarball.txt is formatted correctly, everything
>>>>> else works fine.
>>>>>
>>>>> Brian
>>>>>
>>>>>> On May 5, 2017, at 2:26 PM, Paul Hargrove <[email protected]> wrote:
>>>>>>
>>>>>> 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 <[email protected]>
>>>>>> wrote:
>>>>>> 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 game as UTK does not have an MTT).
>>>>>>
>>>>>> George.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, May 5, 2017 at 1:53 PM, Barrett, Brian via devel
>>>>>> <[email protected]> wrote:
>>>>>> 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
>>>>>> in increasing the major number of the release number) is to rebranch off
>>>>>> of master, there’s a feeling that we should have named the branch
>>>>>> v3.0.x, and then named the next one 3.1.x, and so on. If that’s the
>>>>>> case, we should consider renaming the branch and all the things that
>>>>>> depend on the branch (web site, which Jeff has already half-done; MTT
>>>>>> testing; etc.). The disadvantage is that renaming will require everyone
>>>>>> who’s configured MTT to update their test configs.
>>>>>>
>>>>>> The first question is should we rename the branch? While there would be
>>>>>> some ugly, there’s nothing that really breaks long term if we don’t.
>>>>>> Jeff has stronger feelings than I have here.
>>>>>>
>>>>>> If we are going to rename the branch from v3.x to v3.0.x, my proposal
>>>>>> would be that we do it next Saturday evening (May 13th). I’d create a
>>>>>> new branch from the current state of v3.x and then delete the old
>>>>>> branch. We’d try to push all the PRs Friday so that there were no
>>>>>> outstanding PRs that would have to be reopened. We’d then bug everyone
>>>>>> to update their nightly testing to pull from a different URL and update
>>>>>> their MTT configs. After a week or two, we’d stop having tarballs
>>>>>> available at both v3.x and v3.0.x on the Open MPI web page.
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> Brian
>>>>>> _______________________________________________
>>>>>> devel mailing list
>>>>>> [email protected]
>>>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> devel mailing list
>>>>>> [email protected]
>>>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Paul H. Hargrove [email protected]
>>>>>> Computer Languages & Systems Software (CLaSS) Group
>>>>>> Computer Science Department Tel: +1-510-495-2352
>>>>>> Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
>>>>>> _______________________________________________
>>>>>> devel mailing list
>>>>>> [email protected]
>>>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>>>>
>>>>> _______________________________________________
>>>>> devel mailing list
>>>>> [email protected]
>>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>>>
>>>> _______________________________________________
>>>> devel mailing list
>>>> [email protected]
>>>> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
>>>
>>
>
> _______________________________________________
> devel mailing list
> [email protected]
> https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
--
Jeff Squyres
[email protected]
_______________________________________________
devel mailing list
[email protected]
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
