On 6/17/2010 3:09 PM, Alin wrote:
That is a very good question.
Our subversion server has not been updated in a while and it is still on
version 1.4.2. I was looking into updating it to take advantage of the
new merge tracking features (among others).
Since we are using such an old version, I wanted to replicate our
production environment on a test server (thus requiring version 1.4.2)
and performing the upgrade there first.
1.4.2 is still in the CentOS 5.x base and installable by yum - and that
should mean that RHEL has the same if you are looking for rpms.
Do you think I am being overly cautious? What are the chances for a
problem to occur in the upgrade process?
I wouldn't expect problems - or for you to learn much from a test copy.
What you really need is to make sure you can put things back on the
real server regardless of anything that happens. That means you'll
need snapshots of the repository(ies) made with the server stopped and
copies of the programs and any local configuration - just in case...
Also, note that when you first use a new client version it will modify
any working copies it touches so that older versions can't be used
again. Differing versions of clients and servers will interoperate but
you don't get all the new features until both are new.
--
Les Mikesell
lesmikes...@gmail.com
