Re: Version Control

2005-07-31 Thread jonathan vanasco
Free bitkeeper is gone though, so its not really an option On Jul 31, 2005, at 1:00 AM, David Christensen wrote: I wrote: I was going to say, "watch out for subversion's license" (free only for free projects with public access; otherwise a paid commercial license is required), ... My mista

FW: Version Control

2005-07-30 Thread David Christensen
I wrote: > I was going to say, "watch out for subversion's license" (free only > for free projects with public access; otherwise a paid commercial > license is required), ... My mistake. The above comment applies to BitKeeper: http://www.bitkeeper.com/Products.BK_Pro.FAQ.html David

RE: Version Control

2005-07-27 Thread David Christensen
use a branch/merge development process, I implemented one for a client using the commercial version control product they were already using (MKS Source Integrity): http://www.mks.com/ To me, the main advantage of MKS SI over CVS (and RCS) was that MKS SI implemented version control on sets

Re: Version Control

2005-07-27 Thread Jonathan Vanasco
I really like Subversion but i'm not too crazy about it without trac. i don't use trac for ticketing though - i use it for viewing changesets and versions of files -- its absolutely amazing at that

Re: Version Control

2005-07-27 Thread Mike Whitaker
On 27 Jul 2005, at 17:22, David Hofmann wrote: My company looking at setting up some kind of versioning control software. Currently we have about 10 programs. We use Perl or C depending on the project. I understand just enough to be dangerous with CVS. Which is the current suggestion to

Re: Version Control

2005-07-27 Thread Philip M. Gollucci
David Hofmann wrote: My company looking at setting up some kind of versioning control software. Currently we have about 10 programs. We use Perl or C depending on the project. Having used PerForce(PERL's system), CVS(FreeBSD/Redhat), SVN(Apache-ASF,mod_perl) I'm saying SVN is the clear winne

Re: Version Control

2005-07-27 Thread Praveen Ray
Depends on your team size and your development process. subversion is pretty good. However, it doesn't do merging of branches as neatly as I'd like it to. But if you dont branch too often, it's excellent. --- David Hofmann <[EMAIL PROTECTED]> wrote: > My company looking at setting up some kind

Re: Version Control

2005-07-27 Thread Ken Simpson
Set yourself up with Subversion. It's easy to configure especially if you are running Apache 2 already and there is an excellent client for Windows (TortoiseSVN). If you're gung ho, you could even set up trac for issue tracking. It integrates really well with SVN and is a good solution for small t

Version Control

2005-07-27 Thread David Hofmann
My company looking at setting up some kind of versioning control software. Currently we have about 10 programs. We use Perl or C depending on the project. I understand just enough to be dangerous with CVS. Which is the current suggestion to use. However before we make use of it I want ask opin