[cvsnt] Server upgrade from 184.108.40.206 rc1 (Build 53) to 2.0.34
ldlapolla at yahoo.com
Mon Mar 29 12:52:14 BST 2004
I'm still concerned with the working copies checked out from the old server
that will have it's modifications commited to the new server.
Should I expect any problems or the working copy structure independs on
"Czarnowski, Aric" <aczarnowski at unimax.com> escreveu na mensagem
news:mailman.62.1080313052.14560.cvsnt at cvsnt.org...
> I'm concerned with the working copies that have
> been checked out from 220.127.116.11 and whose
> modifications will be commited in 2.0.34.
> The working copy format is compatible? Does anyone
> had any trouble with a situation like that?
You shouldn't have any ,v format issues to deal with on the upgrade. We
went from CVSNT 1.11.X to 2.0.27 with no problems. Older clients could
have troubles with some new information that CVSNT stores (like merge
points) but the ,v files will be fine.
I don't know of any backward compatibility issues with a 2.0.24 (the
WinCVS CVSNT version) and a 2.0.34 server but I suppose there could be
some in the WinCVS macros or something. I don't use WinCVS myself
preferring the command line. ViewCVS for windows R5 had problems with
newer CVSNT releases so I'm still running 2.0.27 in our office.
There's an upgrade Q/A in the FAQ on the cvsnt homepage:
Unimax Systems Corporation
More information about the cvsnt