On Tue, Sep 02, 2008 at 01:14:15PM +0200, viq wrote: > On Tue, Sep 02, 2008 at 11:23:31AM +0100, Stuart Henderson wrote: > > On 2008/09/02 17:57, Dongsheng Song wrote: > > > Could you support both 1.4 & 1.5, like jdk ? > > > > there is a very good reason for doing this with jdk. reading the > > release notes for Subversion, it seems this is not necessary here:- > > > > | "Older clients and servers interoperate transparently with 1.5 servers > > | and clients. However, some of the new 1.5 features (e.g., merge > > | tracking) may not be available unless both client and server are the > > | latest version . There are also cases (e.g., sparse checkouts) where a > > | new feature will work but will run less efficiently if the client is new > > | and the server old. > > | > > | There is no need to dump and reload your repositories. Subversion 1.5 > > | can read repositories created by earlier versions. To upgrade an > > | existing installation, just install the newest libraries and binaries on > > | top of the older ones. > > | > > | Subversion 1.5 maintains API/ABI compatibility with earlier releases, by > > | only adding new functions, never removing old ones. A program written to > > | the 1.0, 1.1, 1.2, 1.3, or 1.4 API can both compile and run using 1.5 > > | libraries. However, a program written for 1.5 cannot necessarily compile > > | or run against older libraries." > > > > what's the reason you want to keep 1.4? > > I've seen some 1.4 clients (or eclipse plugins) not being able to talk to 1.5 > server.
That surprises me. Can you point to mailing list threads or entries in the issue tracker upstream? Stefan
