Re: cvs server VS cvsnt server

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Deborah Comeau \(LCL\) <address@hidden> writes:

> Our current setup is:
> 
> Server: Concurrent Versions System (CVS) 1.11.11 (client/server)
> 
> on Red Hat Linux Advanced Server release 2.1AS/i686
> 
>  
> 
> We are in the process of switching all of our version control over to
> CVS. Some of our developers were using CVS long before we began our
> project to use one version control product within our company. Due to
> certain limitations in CVS, we have been looking at CVSNT Server. We
> have read the documentation on the benefits of using CVSNT server VS
> the CVS server.

As always, there are pros and cons to such a decision. If your primary
user community will be using CVSNT on windows (or WinCVS), then you may
find this is on the whole a good choice.

If you do make the switch, I think many folks would be interested in how
things go for you. Especially in what features of CVSNT you would most
like to have ported into CVS and vice versa.

> 
>  
> 
> Our current developers have a number of concerns:
> 
> 1) Does the Linux version of CVSNT have all the features of the
> Windows version on CVSNT?

I would expect that some of the windows authentication methods that
require windows authentication methods may not be available.

> This is important because we will be running CVSNT on Linux
> 
> 2) Is there any CVS functionality that will be lost if we move to CVSNT?

Well, the 'stable' version of cvs 1.11.x (x==17 at present) does not
have all of the features of CVSNT, but I believe most of the CVS
features are available in CVSNT.

CVSNT and the 'feature' version of cvs 1.12.x (x==9 at present) does
have some features that are not yet available on CVSNT.

> 3) Is CVSNT 100% compatible with CVS?

The protocol they use is compatible in that they will negotiate the
subset of functionality that will be compatible. However, some features
of the CVSNT client will not be available with a CVS server. Most of the
features of the CVS client should work fine with a CVSNT server.

> Meaning the IDE interfaces designed for CVS work with CVSNT.

There are many possible IDE interfaces, I doubt if all of them have been
tested. You may wish to specify which IDE packages you are considering.

> 4) Will new features of CVS be added to CVSNT?
>
> Meaning will CVSNT be kept as compatible as possible with CVS except with
> additional features

That is up to the CVSNT community. In general, I would favor efforts to
cross-port the features of CVSNT into CVS and CVS into CVSNT.

> 5) Is the file locking of CVSNT better than that of CVS?
> 
>             Some developers require file locking.

The locking is different. CVS feature branch has just gotten an advisory
locks patch integration added that has been around for a long time.

To be honest, I have not played much at all with exclusive locks as I
believe that to be a bit foreign to what CVS does best.

> 6) Is there anyone who has switched over to CVSNT server on a Linux
> server who is willing to share his or her experiences with us?

I am not able to answer this question. I continue to use CVS instead of
CVSNT.

> 7) Was there any changes to your process, or changes in functionality?
> 
>  
> 
> Any information would be appreciated.

        Good luck,
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFBYr8G3x41pRYZE/gRAgV3AJ45V8HD0qxoZb9IXaZb/1wQGygzMwCdE2gy
cbTbX6fZiYBlroCehEoiT8w=
=LX/H
-----END PGP SIGNATURE-----