[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: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2003-12-15 19:40:30 CET

On Mon, 2003-12-15 at 12:47, kfogel@collab.net wrote:
> +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
> +level of the release branch for recording votes. Each item is a short
> +identifying string (a revision number, an issue number, etc), a brief
> +description of the change, followed by the votes. For example:
> +
> + * r98765
> + Make the svn_read_user_mind() function accept NULL input.
> + See mailing list thread http://...
> +
> + Votes for merging into 1.0:
> + +1 ghudson
> + +1 bliss

I would suggest including an at-most-one-line justification for why this
should go into 1.0. ("Critical bug-fix", "API change", "Fixes privacy
violation", etc.)

Otherwise, this looks fine.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 15 19:41: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.