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

Re: When to upgrade repository format number?

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2005-03-12 18:53:24 CET

--On Saturday, March 12, 2005 11:23 AM -0600 kfogel@collab.net wrote:

> For exactly the same reason: so if someone downgrades to pre-1.2, all
> their repositories would still work.
> I wasn't trying to avoid the "overhead of an automatic upgrade"; there
> is no such overhead, the automatic upgrade of the repository is easy
> and painless. The pain comes if one downgrades one's server code
> after that.

I honestly don't think we should concern ourselves with admins who downgrade
across minor versions. I believe this turns out to be a really minor issue.
Plus, when we set out our versioning rules, we explicitly agreed that the file
system would always be forwards-compatible, but not backwards-compatible
across minor releases (see HACKING). I see no reason to alter that policy. I
think we're being overly conservative when there is little pragmatic need to
do so.

Now, I'll agree with Greg Hudson on IRC that we could do ourselves a favor and
delay the automatic format upgrade until a user performs a locking function.
But, I'm really against requiring admins to take explicit action to 'upgrade'
a repository to enable a feature. I feel this is being way too burdensome on
real-world admins. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 12 18:54:36 2005

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.