[cvsnt] Re: cvsnt status
Erv Walter
erv at epicsystems.com
Tue Jul 15 14:50:46 BST 2003
Unfortunately, subversion are going strongly down a non-Microsoft path
(Apache, BerkeleyDB, etc).
CVSNT with a SQL backend will be an improvement (you get a transactional
backend for free, although it seems Tony wants to do it himself for some
reason), but we still have to live with the less-than-ideal client :)
For enterprise team development (400 developers, growing monthly) great
communication tools built into the SCS are needed. Easy (and scalable)
branching and merging are needed. A great (with a low learning curve)
GUI is helpful so that we can worry less about newbies at the company
screwing up a complex command line operation. However, a command line
or API for integrating with build engines and for advanced users is of
course needed. Top notch integration with VS.NET is helpful as well.
Ok, enough of the dreaming :) Heck there, are barely any commercial
products that have all that.
-----Original Message-----
From: John Peacock [mailto:jpeacock at rowman.com]
Sent: Tuesday, July 15, 2003 8:20 AM
To: Tony Hoyle
Cc: CVS-NT Mailing List (E-mail) (E-mail)
Subject: Re: [cvsnt] Re: cvsnt status
Tony Hoyle wrote:
>> Isn't the Subversion project working on this (a database backend for
>> the Code Management system)?
>>
> AFAIK they're not using SQL or anything, just a different backend.
Correct. The current version uses BerkeleyDB as a backend (which is
technically a SQL database, but only just barely ;~). Post 1.0 (which
is probably 3QTR 2003, BTW), there will be some effort to support other
backends, specifically MySQL and PostgreSQL.
FWIW, the intro to Subversion at OSCON last week was standing room only,
so there is definitely a lot of people out there who are not satisfied
with CVS (of any stripe), and looking for something else.
John
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
More information about the cvsnt
mailing list