Re: process for including changes in 1.0

> > 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.
>
> Garrett answered this question nicely; I'll just add that issues are
> more cumbersome to work with than text files.

I always say that you have to solve problems at their root. Otherwise
everybody has to keep working around them with different solutions. Seems like
issue 1640 has to have it's priority upped... :-)

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