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

Locking: repos upgrades?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-11-19 18:28:54 CET

We have a standing promise that "no dump/loads will be necessary until
2.0". That means no fs schema changes.

But I'm a bit fuzzy on how this promise interacts with the repos/format

Specifically, svn 1.2 will now have two new BDB tables (and FSFS will
also have grow some new data storage). How are users going to upgrade
to 1.2 smoothly?

1. I seem to recall that when we added the 'uuids' table, there was
some magic code that instantly created the table if not present. Do we
need to repeat that technique?

2. Are we allowed to increment the 'format' file? I'd certainly like
to. Otherwise, a process using libsvn_fs 1.1 can create a lock, but
then a process using libsvn_fs 1.0 would silently ignore the lock
without realizing it. Does incrementing 'format' break our
compatibility promises?

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 19 18:30:30 2004

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.