[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: <kfogel_at_collab.net>
Date: 2003-12-15 20:02:42 CET

Tobias Ringström <tobias@ringstrom.mine.nu> writes:
> > +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.

I'm fine with these being excepted. For example, we want the book
documentation up-to-date in the 1.0 tarball, as much as possible.
They should still get fixed in trunk first, then ported, of course.

> 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.

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:52:02 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.