On Sun, 2008-06-29 at 16:12 -0400, Daryle Walker wrote:
Last week, a was bouncing around sites and found out that Subversion 1.5.0 has gone final. I've downloaded it because I want to try its built-in merging support (to fix up Boost.Integer in a branch). Has our subversion system been updated to 1.5?
No, we're still using Subversion 1.4 on the server.
Obviously, if the client and server use subversion versions 1.x and 1.y respectively, the transactions will proceed as the lower of those versions. Therefore, both individual clients and the server must be at least the 1.5 level to use built-in merging. There's another requirement, though: if the server is upgraded to 1.5, the repositories it manages aren't automatically upgraded. If a repository isn't upgraded to the 1.5 format, then the server will act in 1.4-compatibility mode as needed.
Is there a schedule for these upgrades to be done (if not done already)? Is it possible to tell from the client side which mode a server/repository uses?
I actually don't know how to tell from the client-side which version of Subversion the server is running. As for the upgrade... we're looking into Subversion 1.5, but it appears to be a nontrivial process to perform the upgrade and migrate svnmerge.py merge information appropriately, so we need to read more, do some test runs, check that other projects haven't run into serious problems, etc. So much depends on the Subversion repository that we need to be careful. When we're ready to move, we'll send out an e-mail to the mailing list. - Doug