[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 (was: Re: 1.3.0 tarballs up for testing/signing (again))

From: <kfogel_at_collab.net>
Date: 2006-01-30 01:13:00 CET

Erik Huelsmann <ehuels@gmail.com> writes:
> > I would say that if any code changes, it *must* get a new version number.
> > If it's just a re-roll due to a dist.sh or packaging problem, then it can
> > use the same version number. However, there is never a legitimate reason
> > to re-use a version number if the code has actually changed. -- justin
> I agree with Justin that this is how I'd like to handle this in this
> case: there's no difference in the code shipped, nor is there any
> difference in any other significant part of the archive.

Okay, clarified policy committed in r18287, comments welcome.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 30 02:50:58 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.