On Thu, Jul 03, 2014 at 10:58:35AM +0100, Notes Jonny wrote: > I guess the other idea is to promise to only allow ".svn format" > updates every 5 years? I can't think that I've noticed any > improvements since I've been using new formats..
The 1.8 format added support for local move tracking, for instance. http://subversion.apache.org/docs/release-notes/1.8.html#moves > Do GIT repos suffer these same problems? No, they don't. And neither do Subversion repositories (i.e on the the server-side), which are fully backwards compatible. SVN working copies correspond more to the "git working tree" rather than the git repository. SVN working copies are not backwards compatible (yet) and thus clients sharing working copies need to be updated in lock-step. We know that this is problematic for some users, however for now that's the situation. SVNKit-based Subversion clients should be able to use older working copy formats. Most Java-based clinets use SVNKit instead of Subversion (SVNkit is a separate implementation written in Java, see http://svnkit.com/). IIRC Jenkins uses SVNKit, so it should be able to work with working copies in older formats.
