On Fri, 2003-10-24 at 06:02, Ben Collins-Sussman wrote:
> But protocol incompatibilities? These happen all the time. They
> happen so frequently, in fact, that most of them don't even get
> announced. That's why we're always telling people about our pre-1.0
> interoperability policy: client and server must be within one version
> of each other. One of the reasons we have this policy is so that we
> don't *have* to announce protocol changes. (Honestly, I have no idea
> why Karl and Mike decided to "announce" the latest client/server
> incompatibility change... we've never done it before!)
... which leads me to ask, if there's a client/server incompatibility,
will we break anything by not observing this one-version difference
rule?
I have at least four different versions of subversion floating around on
different machines. My main repository server is still around version
0.27--I haven't had a chance to do the dump/load cycle--my laptop has
the contrib package for Mandrake 9.2 at 0.28, and my new server is at
0.30. And the workstation I'm currently writing on has, let's see.
0.23.0+. Oh, and my Windows XP partition on the laptop has only a
version or two back of Tortoise...
I've seen the odd error message here and there, and they always went
away after doing an svn update. Other than that, I've noticed no
problems.
Have I likely mangled my repositories by now? Or as long as I don't get
an error, can I merrily continue my mishmash of versions (I promise next
time I'll update everything ;-)
Cheers,
John Locke
--Doing the wrong thing in the name of laziness...
P.S. Is there a target date for the Beta yet?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 25 17:48:52 2003