On Mon, 17 Jan 2000 08:42:40 +0000, David Warnock wrote:

>From: David Warnock <david@...>
>
>Edward,
>
>> If it came to votes, I'll definitely give my voice to CVS. Myself, I find
>> even RCS quite enough. However, there are people who don't know about these
>> systems, also there are people aware of another packages. The idea is to
>> work out a list of criteria and evaluate every major code control system with
>> the help of this list.
>> We can't just say `It's good, period'. First we have to realize what params
>> are essential, then prove that the system of our choice is good. And let the
>> best win :)
>
>Sorry I don't agree, if we want Open Source Interbase to suceed then we
>have to make sure that you only need the standard open source tools to
>work with it. This applies to version control, compilers - the lot. So
>for version control we should just go with CVS.

After some thinking I have to agree with you... When IB source becomes
available, it's very worth to attract OSS from other projects.
So, if this is a need (and I guess it are) CVS is good for start. If later we
discover its a s*, maybe we look for another or simply review these messages
about this type of stuff for voting. Maybe a trial test ( a simple OSS project
for community test CVS in the real life) are a good idea.... It's only a idea, however...

[]s Fabricio

>
>Dave
>
>--------------------------- ONElist Sponsor ----------------------------
>
>Independent contractors: Find your next project gig through JobSwarm!
> You can even make money by referring friends.
><a href=" http://clickme.onelist.com/ad/jobswarm2 ">Click Here</a>
>
>------------------------------------------------------------------------
>
>Community email addresses:
> Post message: IBDI@onelist.com
> Subscribe: IBDI-subscribe@onelist.com
> Unsubscribe: IBDI-unsubscribe@onelist.com
> List owner: IBDI-owner@onelist.com
>
>Shortcut URL to this page:
> http://www.onelist.com/community/IBDI
>