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

Re: Release policy question

From: <kfogel_at_collab.net>
Date: 2006-01-31 21:27:25 CET

Daniel Rall <dlr@collab.net> writes:
> I'm saying it's simplest to call the new tarball x.y.(z + 1), if the
> previous tarball was named x.y.z. I'm advocating that approach even
> when nothing meaningful in the source code has changed between
> tarballs. I believe we've done this in the past when a tarball has
> been DOA.

Yes, that's also what Greg is advocating. I'm +1 on it too.

Sanity check: you also mean that if we put out X.Y.Z-rc3, and five
minutes later we discover a trivial typo in a README, and reroll a new
tarball before *anyone* has signed the RC, that we will still call the
new tarball X.Y.Z-rc4, right?

IOW, this applies to RCs as well as non-RCs.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 31 23:07:03 2006

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.