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

Re: What do Subversion version numbers mean?

From: Erik Huelsmann <e.huelsmann_at_gmx.net>
Date: 2003-12-22 11:46:19 CET

> On Sun, 2003-12-21 at 17:00, Branko ibej wrote:
> > * A minor version change implies backward compatible changes in the
> > API, schema and protocols. For example, a client built against
> > library version X.Y.Z will work correctly with library version
> > X.Y+1.n; and an X.Y+1.n server will work correctly with a
> > repository created by svnadmin X.Y.Z.
>
> I'd also throw in backward-compatible changes to the programs we ship.
> A script written to svn X.Y.Z should work with SVN X.Y+1.n. (For the
> most part, anyway. I don't think we need to bump to svn 2.0 if we
> change the meaning of "svn diff -r X:Y foo" according to CMike's plan,
> for instance, even though it's *conceivable* that a script could be
> relying on the old meaning.)
:-) In this case the svn command line client could be viewed as a library
for the script. (Which indeed means to imply that the APR versioning document
could be applicable.) :-)

Note that this schema for version numbering does not imply that a new minor
number contains new functionality. The new minor could also be a bugfix which
would not be satisfied by the 'forward and backward' compatibility
constraint. From an earlier post from you I concluded that to you a new minor number
implies new functionality.

bye,

Erik.

-- 
+++ GMX - die erste Adresse fr Mail, Message, More +++
Neu: Preissenkung fr 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 22 11:47:05 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.