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

Re: Need to bump repos format number for 1.4.0

From: Malcolm Rowe <malcolm-svn-dev_at_farside.org.uk>
Date: 2006-08-16 16:24:32 CEST

On Tue, Aug 15, 2006 at 03:35:28PM +0100, Max Bowsher wrote:
> We need to bump the repos format number for 1.4.

Oh, see also: this thread:


which was about the last time we considered bumping the repos version number.

So the situation is:

* We have been using a repository version number of 3 for ever (well,
  since 1.0).

* We introduced a filesystem version number in 1.2, but it's only checked
  by 1.2 and later clients.

* We introduced an optional feature (svndiff1) in 1.4 that requires the
  filesystem version number to be bumped.

* But no clients < 1.2 will check the filesystem version number, so
  they'll merrily try to read or write to the filesystem (which will
  probably work until they hit an svndiff1 stream, at which point
  it won't).

* So we need to bump the repository version number to 4, not to account
  for a change in the repository format per se, but to ensure that any
  clients take account of the filesystem version number. (We could
  choose to only bump it to 4 if the filesystem version ends up as >1,
  rather than tying to a specific feature flag.)

I think I agree that we need to do this, even if it _might_ be safe
in this particular case, but I'd like to understand what the impact
will be to our users.

The last time this was discussed, there was some concern that this would
impact mixed-client users of file:/// repositories, but I don't think
that's so much of a problem here (particularly because an explicit
dump/load cycle is necessary to enable svndiff1 repositories in the
first place).


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 16 16:33:53 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.