Re: [boost] Is merging to the release branch allowed again?

Subject: Re: [boost] Is merging to the release branch allowed again?
From: Henrik Sundberg (storangen_at_[hidden])
Date: 2010-12-01 15:10:15

On Wed, Dec 1, 2010 at 10:32 AM, Daniel James <dnljms_at_[hidden]> wrote:
> On 1 December 2010 05:25, Henrik Sundberg <storangen_at_[hidden]> wrote:
>> On Wed, Dec 1, 2010 at 4:25 AM, Eric Niebler <eric_at_[hidden]> wrote:
>>> On 11/30/2010 2:23 PM, Beman Dawes wrote:
>>>> Yep, OK to merge to release.
>>>
>>> I guess you've now (indirectly) answered in the negative my question
>>> about a point release to address the type_traits vc-7.1 regression.
>>> That's too bad.
>>
>> Shouldn't point releases be originating from the actual release anyway?
>
> Our regression testing system currently only supports two fixed
> branches (trunk and release), so to test a point release we need to
> keep the release branch dedicated to it.

Not really a problem. It's possible to move the current release
branch. Copy the released version to be the release branch again and
fix the point release. Reverse merges are also possible.
I would suggest fixing the precommit hook to only allow point release
fixes during this time.

/$