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

Re: Subversion questions

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-05-22 00:09:09 CEST

On Wed, May 21, 2003 at 11:53:15AM -0500, cmpilato@collab.net wrote:
> Paul L Lussier <pll@lanminds.com> writes:
>
> > >2) Does upgrading Subversion requires (or will require in a near future)
> > >any special procedure for the existing repositories ? Basically, if
> > >someone uses Subversion right now, does a migration is to be planned
> > >when Subversion 1.0 comes out, for example ?
> >
> > My understanding is that if you keep up with the releases, there is
> > nothing to worry about, and that a best effort toward
> > backward compatibility is made for at least one revision. So, if you
> > are running 0.22 and svn 0.23 is released, then your safe. If you
> > continue on with 0.22, and 0.27 is released, there are no
> > guarantees.
>
> This is correct, but I'd like to supplement your response by saying
> that once Subversion hits 1.0, this compatibility window of a single
> revision will be *greatly* widened. We don't want to scare people by
> making them think they'll have to update their companies' 1.0-or-later
> Subversion installations bi-monthly. :-)

Actually, Paul's response is not correct.

The question was about *repositories*. The repository is directly usable
except when we change the schema. As Garrett noted, we plan to change that
once more before 1.0, but a simple dump/load will rectify the schema change.

*Protocol* changes have the compatibility window issue.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 22 00:07: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.