> > From: Gavin Beau Baumanis [mailto:b...@palcare.com.au]
> >
> > For our production repositories we're using 1.5.1
> >
> > My question is - is there an appropriate version to upgrade to?
> > We're tossing up between;
> >
> > Update to the latest 1.5.x
> > Update to 1.6.x
> > Or simply wait it out  - for 1.7
> >
> > Is there a "suggested" upgrade path?
> 
> Basically, whatever you want is fine.  You should upgrade to at
> least a
> newer version of 1.5, for bugfixes and so forth.  And maybe you
> care about
> new features of 1.6.  I find the performance improvement in 1.6 to
> be quite
> noticeable.
> 
> On the server, there's no need to dump/load your repository, if you
> simply
> start using 1.6 server process, it's compatible.  That being said -
> All the
> stuff that was written in repo by 1.5 will continue having 1.5
> performance,
> while new stuff will be written in 1.6 format and faster.  If you
> want
> optimal performance, and can afford to extend the downtime, then
> doing a
> dump/load to upgrade your repository might possibly enhance
> performance.

Of course you can run svnadmin upgrade to bring the repository to version 1.6. 
If you don't it will keep storing stuff in the 1.5 format and you will lose 
many of the advantages of 1.6.

BOb

Reply via email to