On Mon, Mar 21, 2016 at 3:58 PM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Mon, Mar 21, 2016 at 10:33:49AM -0700, Safarulla Meerasahib wrote:
>> Hi,
>>
>>
>>
>> We have recently taken over a production application from other team, which uses the SVN 1.5.0 as one of the component. Now we have a requirement to upgrade this to latest version of the subversion.
>>
>> While going through the Apache subversion link we have noticed that Subversion 1.9 can only upgrade working copies created with Subversion 1.6 and Subversion 1.7.
>>
>> Is there any workaround to upgrade 1.5.0 to 1.9?
>
> Use 'svn checkout' to get new working copies after upgrading.
> Note that working copies are only used by the Subversion client.
It can be much safer to designate a second server with a fresh copy of
the new version of Subversion, Subverison 1.9 if available, to create
a slave of the original repository. This leave the original repository
usable until the final switchover It's especially if the repository
has gotten large, over time, with binary commits and many branches.
Then, when ready to switchover, make a good backup of the old system,
*LOCK IT* to prevent any further ocmmits, and switch services to the
new server. You should be able to activate a proxy or port forwarding
for the old service, if needed, so anyone who accidentally tries to
reach the old one actually gets the new one.
> A 1.9 server is fully backwards compatible to repositories created
> by any version of Subversion.
>
> If you are unsure about the differences between working copies and
> repositories, please read this page:
> http://svnbook.red-bean.com/nightly/en/svn.basic.version-control-basics.html
Received on 2016-03-22 05:26:01 CET