Re: process for including changes in 1.0

> > +A change needs three +1 votes and no vetoes from full committers to go
> > +into the 1.0-stablization branch. We use the STATUS file in the top
>
> It would be nice to include an exception for harmless obviously correct
> fixes such as spelling fixes and most documentation fixes.
>
> It feels a bit strange to revision control the voting. How about
> creating an issue for each thing we want to include in the branch, just
> for the purpose of voting? Each issue would be named something like
> "merge rXXXX to branch-1.0", i.e. it would not be an issue that
> describes a bug. The committers would then vote by adding comments to
> the issue, and the issue can either be resolved or dismissed when the
> voting is complete.

+1.

It feels strange to use a file in the repository for voting. Using the issue
tracker to track the voting for a certain merge operation feels much better.

bye,

Erik.

-- 
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org