Hi Guido, > -----Original Message----- > From: Stefan Sperling > Sent: Friday, 14 February 2014 1:03 AM > > On Thu, Feb 13, 2014 at 10:57:15AM -0200, Guido Larrain wrote: > > Hello; > > > > I'm planning to upgrade my SVN from version 1.5.6 (r36142) to 1.8.5 > > and i wanna know if i need to do some "special" steps to > perform this.
Is that the client or the server? If it's the client, you should have no problems. The only potential problem will be if you have working copies on a shared drive (it's not recommended, but it happens) and other people who access these are using different versions. If it's the server, you might need to upgrade any BDB repositories to FSFS. Regardless, read the notes on the links that Stefan provided. > > Thanks in advance!! > > > > -- > > Guido > > The most special step (most people don't seem to do this ;) > is to read the upgrade documentation in the release notes for > each intermediate release (1.6 to 1.8 in your case), which > document the special steps, if any, better than any > subscriber of this list could recite from memory. > > http://subversion.apache.org/docs/release-notes/1.6.html#compatibility > http://subversion.apache.org/docs/release-notes/1.7.html#compatibility > http://subversion.apache.org/docs/release-notes/1.8.html#compatibility > > If you still have questions after reading, feel free to ask. Regards, Geoff -- Apologies for the auto-generated legal boilerplate added by our IT department: - The contents of this email, and any attachments, are strictly private and confidential. - It may contain legally privileged or sensitive information and is intended solely for the individual or entity to which it is addressed. - Only the intended recipient may review, reproduce, retransmit, disclose, disseminate or otherwise use or take action in reliance upon the information contained in this email and any attachments, with the permission of Australian Arrow Pty. Ltd. - If you have received this communication in error, please reply to the sender immediately and promptly delete the email and attachments, together with any copies, from all computers. - It is your responsibility to scan this communication and any attached files for computer viruses and other defects and we recommend that it be subjected to your virus checking procedures prior to use. - Australian Arrow Pty. Ltd. does not accept liability for any loss or damage of any nature, howsoever caused, which may result directly or indirectly from this communication or any attached files.
