On Tue, Dec 20, 2016 at 12:10 AM, Matt Garman <matthew.gar...@gmail.com> wrote: > Looking at the Subversion 1.7 release notes[2], and also my own > testing, it appears that what I could do to make this easy for > everyone is to upgrade all CentOS 6 clients to subversion-1.7 (i.e. > have subversion-1.7 everywhere on the client side). Then everyone can > do an "svn upgrade" on all their working copies and go about their > business as usual. The svn server can stay CentOS 6 / subversion-1.6 > for now (probably done much later in the overall upgrade process).
Unless a working copy / checkout is shared between 1.6 and 1.7 clients there's no need to update the clients right? -- Olaf
