[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: process for including changes in 1.0

From: Erik Huelsmann <e.huelsmann_at_gmx.net>
Date: 2003-12-15 20:48:51 CET

> Tobias Ringström wrote:
> > 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.
> I'd prefer to keep things all in one place, rather than scattered about
> in various issues, and the STATUS file does that quite nicely. Also,
> there's some history behind this approach, as it's pretty much what the
> Apache projects do for their voting.

But they don't have repository wide log messages and revision numbers. And
besides that: we would have everything about managing subversion issues in one
place: what to fix and what to merge before a certain milestone will nicely
be listed in one list when using the issue tracker.



+++ 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
Received on Mon Dec 15 20:49:30 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.