[asterisk-dev] Proposed change to branch revision blocking policy

[Tilghman Lesher]

On Tuesday 17 March 2009 09:19:33 Sean Bright wrote:
> Kevin P. Fleming wrote:
> > So, I'm proposing that once a 1.6.x branch has reached the release
> > candidate phase, we stop using svnmerge to block revisions there, as it
> > results in useless 'noise' commits. When there are multiple 1.6.x
> > branches that have had releases, this problem would only multiply.
>
> Did this ever become the policy?  Or did it never make it out of the
> proposal stage?

I've been doing it for a long time for 1.6.0.  I suppose I should now stop
doing it for 1.6.1, too, though it's been awhile since I blocked anything in
1.6.1.

-- 
Tilghman