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

Re: Expected post-1.0 release cycle?

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2003-12-24 02:47:30 CET

--On Tuesday, December 23, 2003 5:40 PM -0800 Jack Repenning
<jrepenning@collab.net> wrote:

> A.B.C <-> A.B.C': protocol compatible, API linkable, schema unchanged,
> limited to bug fixes, free to customers on support
> A.B.C <-> A.B'.*: protocol compatible, API linkable, schema unchanged, bug
> fixes and minor features, new protocol and API stuff allowed so long as it
> doesn't compromise compatibility
> A.B.C <-> A'.*.*: protocol upwards compatible, API deprecation-compatible,
> schema changes allowed, bug fixes, major features, protocol and API changes
> allowed with compatibility support / deprecation
> A.B.C <-> A''.*.*: protocol, API, schema incompatibility allowed

If you took A'' and replaced it with A'' (i.e. no major version gap between
removing APIs or compatibility), I think the APR versioning scheme matches
this pretty closely in its spirit (if not precise meaning).

Since we're an open source project, I think we can convince our users (and
developers) to continue support in parallel for older major releases as
conditions/resources warrant: if developers want to support users on 1.x while
everyone else is on 2.x, fine. (See httpd for the prime example of this.)

I'm willing to guess that commercial software might have a harder time
supporting parallel branches, but that's a hunch. ;-) -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 24 02:48:00 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.