Subject: Re: [boost] 1.56 release
From: Klaim - JoÃ«l Lamotte (mjklaim_at_[hidden])
Date: 2014-03-21 07:58:56
On Fri, Mar 21, 2014 at 12:43 PM, Daniel James <dnljms_at_[hidden]> wrote:
> Are we going to do this? Since we haven't got the new branching structure
> in place, I could stop automatically updating the master branch of the
> super project on Monday, or perhaps on April 7th.
If the idea is to follow gitflow, then starting a release branch to prepare
the release would be the way to go.
It would mean that the update is never stopped, the release fixes/changes
would get into the release branch and once the release is published,
these changes would get merged back to master.
That being said, it's the gitflow way but it don't mean that it works for
boost: I don't see clearly how this could work with the super project setup.
Maybe asking for libraries which want to release something to do this and
then have the super repo release branch use the release branch of each
subrepo would work
but it seem complicated (but automatable like for the master udpate).
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk