1.6 dump => 1.5 load => dump => 1.8 load : any issues expected?

[pjaytycy <pi...@gmail.com>]

Hello,


We are planning to migrate our internal SVN servers. We are currently 
running on svn 1.6 on the server. We will get new infrastructure with SVN 
1.5 server setup in the short term and are planning to upgrade to 1.8 at a 
later date. We are planning to do a dump from our current 1.6 server, load 
it into the new 1.5 server, continue working for a few months, dump again 
from the 1.5 server, upgrade to 1.8 (maybe already 1.9 by that time) and 
load the repos again. Ofcourse we would prefer to dump from 1.6 and load in 
1.8 immediately, no need to convince me of that, but that won't happen. 

My question now is: will we lose any data / functionality due to the load 
in and subsequent dump from SVN 1.5? Any difference for the commits that 
were done in the past against 1.6 vs the commits that will be done in the 
transition period against 1.5?


Kind regards,

Pieter-Jan

Re: 1.6 dump => 1.5 load => dump => 1.8 load : any issues expected?

[Andreas Stieger <an...@gmx.de>]

Hi,

On 28/09/15 17:49, pjaytycy wrote:
> We are planning to do a dump from our current 1.6 server, load it into 
> the new 1.5 server, continue working for a few months, dump again from 
> the 1.5 server, upgrade to 1.8 (maybe already 1.9 by that time) and 
> load the repos again.
> [...]
> will we lose any data / functionality due to the load in and 
> subsequent dump from SVN 1.5? Any difference for the commits that were 
> done in the past against 1.6 vs the commits that will be done in the 
> transition period against 1.5?

In the described scenario this will work as you intended, there will be 
no incompatible differences in the commits. (APR hash order changed but 
this is transparent to the repo user)

Andreas

Re: 1.6 dump => 1.5 load => dump => 1.8 load : any issues expected?

[Stefan Sperling <st...@elego.de>]

On Mon, Sep 28, 2015 at 08:49:55AM -0700, pjaytycy wrote:
> Hello,
> 
> 
> We are planning to migrate our internal SVN servers. We are currently 
> running on svn 1.6 on the server. We will get new infrastructure with SVN 
> 1.5 server setup in the short term and are planning to upgrade to 1.8 at a 
> later date. We are planning to do a dump from our current 1.6 server, load 
> it into the new 1.5 server, continue working for a few months, dump again 
> from the 1.5 server, upgrade to 1.8 (maybe already 1.9 by that time) and 
> load the repos again. Ofcourse we would prefer to dump from 1.6 and load in 
> 1.8 immediately, no need to convince me of that, but that won't happen. 
> 
> My question now is: will we lose any data / functionality due to the load 
> in and subsequent dump from SVN 1.5? Any difference for the commits that 
> were done in the past against 1.6 vs the commits that will be done in the 
> transition period against 1.5?
> 
> 
> Kind regards,
> 
> Pieter-Jan

As Andreas said, this should work as far as repository formats go.

But please keep in mind that support for both 1.6 and 1.5 has ended a
long time ago. If you run into problems such as repository corruption,
needless merge conflicts, or server crashes, please don't expect much help.
Rather, those are to be expected. Many such issues have been fixed since.

If you value stability, I would recommend a transition to 1.8.14 right
away, whatever it takes. The 1.9 series is indeed still a bit new to
be fully trusted on servers in production (because virtually nobody
tests our beta releases).

You don't even need to dump/load, if that makes your decision any easier.
See http://subversion.apache.org/docs/release-notes/1.8.html#compatibility

And please refrain from posting to our lists from google groups.
Every time I reply to an email sent this way, and I forget to tweak the
Cc header, I get a bounce from google and my message to this list is
black-holed. The address of this mailing list is users@subversion.apache.org
and not subversion_users@googlegroups.com 
Thank you for your consideration.