Boost logo

Boost :

Subject: Re: [boost] [convert] How to promote it from 'develop' to 'master'?
From: Edward Diener (eldiener_at_[hidden])
Date: 2015-04-20 23:09:10

On 4/20/2015 8:04 PM, Daniel James wrote:
>> On 4/20/2015 1:10 PM, Vicente J. Botet Escriba wrote:
>>> Le 20/04/15 00:09, Vladimir Batov a écrit :
>>>> Daniel James created an entry point for 'convert' in the Boost
>>>> 'develop' branch and 'convert' has been sitting there for quite some
>>>> time. Now that Boost 1.58.0 has been released I would like to have
>>>> 'convert' promoted from 'develop' to 'master' so that 'convert' would
>>>> make it to 1.59. Is there anything that *I* can/need to do to have an
>>>> entry point created for 'convert' in the Boost 'master' branch?
>>> Hi,
>>> I would start a new thread and add you review manager. It is the review
>>> manager that should check everything is okay.
> The review manager should have approved it before it was added to
> develop, release managers check that something is okay for release.
> I'll take it a look at it soon-ish if no one else does first (although
> it would be nice if someone else did). Give me a shout if I forget.
> On 20 April 2015 at 20:38, Edward Diener <eldiener_at_[hidden]> wrote:
>> My educated guess is that it would involve a fork of boostorg/boost, a local
>> 'pull --rebase' from that fork, changes locally that add the library
>> submodule to 'master' with the necessary commit, a 'push' back to the fork,
>> and then a pull request so that it shows up at boostorg/boost and eventually
>> gets merged into the superproject. I believe part of the local changes are
>> also that status/jamfile.v2 has to be changed so that the library's tests
>> are added to it.
> When I do it, I usually just copy the changes over. I don't know why
> you want to rebase.

What do you mean by "I usually just copy the changes over." ?

Do you mean that you 'pull' from boostorg/boost, make the change locally
and then push to the fork ?

Boost list run by bdawes at, gregod at, cpdaniel at, john at