Related to How to upgrade SVN server from 1.6 to 1.7 and Will TortoiseSVN 1.7 work properly against a SVN 1.6 repository?.
Updated VisualSVN-Server to 2.6.0 (SVN 1.8) and local TortoiseSVN clients to 1.8. I've upgraded local working copies to 1.8.
My question is simply is there anything to do to the actual repository? How can you determine the repository version? Can/Does it need to be upgraded?
I can easily update the working copy, but I can't seem to find anything that mentions the actual server repository.
svn update brings changes from the repository into your working copy. If no revision is given, it brings your working copy up-to-date with the HEAD revision. Otherwise, it synchronizes the working copy to the revision given by the --revision option.
Installation of VisualSVN Server on windows. The visual server has completed almost 3M downloads. It is the most favorable way for setting up and maintaining the Apache Subversion server on the Windows platform. VisualSVN Server is easy to install because it is distributed under a single package installer.
SVN stands for Subversion. So, SVN and Subversion are the same. SVN is used to manage and track changes to code and assets across projects.
It's not mandatory that you do anything on the server to upgrade your repository. To take advantage of new features in the FSFS backend going forward, you can run svnadmin upgrade but to get the full benefit for your whole history, you'll need to perform a dump/load cycle.
That said, there is a bug with svnadmin upgrade
in 1.8.0 which results in a crash if you have an unsharded repository. So you may want to wait until 1.8.1, or do the full dump/load.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With