Re: Compatibility, and Frustration.

On Wed, 12 Mar 2003, Karl Fogel wrote:

A question and a few suggestions:

How does this relate to the repository? Can I expect the server not
to croak on the repository after an upgrade?

How about maintaining an "UPDATING" file like the FreeBSD project
does. It's a bit like the CHANGES file, except it only has notes
about compatibility related changes and it's updated continuously.
After updating your source tree and before compiling and installing
you'll do a quick check of the UPDATING file.

Maybe it would be useful to have the client print a warning when
it's accessing a server that's too new or too old? Maybe using
something like the Apache httpd flag used for binary modules (I
momentarily forgot the name). When an incompatible change is
introduced the version/flag is bumped and the client will be able to
tell.

   - ask

-- 
ask bjoern hansen, http://www.askbjoernhansen.com/ !try; do();
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org