Subject: Re: [boost] Fwd: Boost.Python build error in 1.58 RC1, 2 and 3 (OK in Beta 1)
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2015-04-15 10:49:14
On Wednesday 15 April 2015 16:22:33 Peter Dimov wrote:
> Andrey Semashev wrote:
> > What I'm saying is that once release process has started there should be
> > no restriction on updating master in submodules (i.e. the freeze), the
> > release should branch off the main code base and get finished
> > regardless of the modifications developers make.
> Something like this?
> Nowadays, I'd no longer advocate for the odd branch naming where develop
> corresponds to master - it's too late for that. But the general idea still
I suspect we won't be able to get away with just the superproject branching.
If instead of reverting a broken submodule we want to fix it, and the
maintainer is unresponsive for some reason, we need either a branch in the
submodule or a fork of it. Since the branch can be modified by someone else
than a release manager, the fork seems more preferred. The release branch of
superproject would have to refer to the fork in this case.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk