Re: [boost] [1.45] REMINDER: Release branch is closed! (was: [1.45.0] Permission to merge trunk to release for (Polygon))

Subject: Re: [boost] [1.45] REMINDER: Release branch is closed! (was: [1.45.0] Permission to merge trunk to release for (Polygon))
From: Robert Ramey (ramey_at_[hidden])
Date: 2010-11-12 14:38:07

Simonson, Lucanus J wrote:
> Eric Niebler wrote:

> If not then our next best option is probably to lock the release
> branch and unlock it manually for specific users who have show
> stopper fixes that they want to commit and ask for permission on the
> dev list or directly from the release manager.  Once the release
> branch is unlocked for a developer it remains unlocked because it is
> assumed they know what is going on because they asked for it to be
> unlocked and that they need it to remain unlocked so that they can
> address any regression failure caused by bad merges or whatever might
> go wrong with their commit.  Once the release goes out the release
> branch can be unlocked for everyone until the next code freeze.

This was suggested and tried soon after SVN was installed.  The
problem is that SVN took hours to do the lock.

For now, I don't think that there is a practical fix for this -
other than to just be more careful and recognise that from
time to time it will occure.

Robert Ramey