Jan Evert van Grootheest <j.grootheest@euronext.nl> writes:
> Is there a history somewhere that lists compatibility breaks like this? That
> would allow people to easily check when upgrading from older versions.
> I recall that 0.28 introduced a new DB schema and required a dump/load
> cycle.
> Now 0.32.1 introduces ra_dav client/server incompatibilities.
There's a huge difference between those 'events'.
db-schema changes happen maybe once a year, and we scream real loud
about it, because the effect is much more drastic: you upgrade to the
latest svn, and suddenly no program is able to read your repository at
all.
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!)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 24 15:06:34 2003