Re: Locking: repos upgrades?

Garrett Rooney <rooneg@electricjellyfish.net> writes:
> Umm, I was under the impression that we only supported downgrading to
> an earlier patch release, not an earlier minor release... Correct me
> if I'm wrong...

I took a look in HACKING, and it's unclear on this point:

> 2. Working copy and repository formats are backward- and
> forward-compatible for all patch releases in the same minor
> series. They are backward-compatible for all minor releases in
> the same major series; however, a minor release is allowed to make
> a working copy or repository that doesn't work with previous minor
> releases, where "make" could mean "upgrade" as well as "create".

The phrase "They are backward-compatible for all minor releases in the
same major series" seems to indicated that they're, well, backward
compatible for all minor releases in the same major series.

But then the next phrase carves out an exception so huge as to
practically eliminate the original rule. (I think I wrote this
language, too, sigh.)

In this particular case, we should be compatible if we can -- and it's
easy to be compatible, so the question is easily resolved.

But I wonder what the heck that language in HACKING really means?

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Nov 20 03:01:29 2004