Boost logo

Boost :

Subject: Re: [boost] [1.45] REMINDER: Release branch is closed! (was: [1.45.0] Permission to merge trunk to release for (Polygon))
From: Simonson, Lucanus J (lucanus.j.simonson_at_[hidden])
Date: 2010-11-13 16:01:06

Henrik Sundberg wrote:
> On Thu, Nov 11, 2010 at 8:04 PM, Eric Niebler <eric_at_[hidden]>
> wrote:
>> This mistake is understandable and all too easy to make. Our process
>> needs to be improved. It can't rely (as it currently does) on library
>> maintainers following the developer list for hold-your-horses and
>> all's-clear messages from the release managers. Suggestions? Can we
>> lock the release branch? Trac is already smart enough to parse commit
>> comments for bug numbers and close tickets. Can we make it smarter to
>> block commits that aren't closing out a showstopper?
> It's very simple to add a check to the precommit hook that for the
> release branch mandates that (during the beta period) all commit
> messages are prefixed with something like "SHOWSTOPPER FIX: ".
> This way no one will be committing to the release branch by mistake.
> The error message for the precommit can give all needed information.
> I.E. tell the committer how to get allowed to commit, and how to
> prefix the commit messages.
> The extra test shall be removed when the release branch is opened
> again.

I like this suggestion. It gets the job done with the least ammount of fuss.


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