Re: Version control
- From: "Tom Reiertsen" <tom@xxxxxxxxxxxxx>
- Date: Fri, 27 Oct 2006 17:41:47 +0200
"Brian Moelk" <bmoelk@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4542269a$1@xxxxxxxxxxxxxxxxxxxxxxxxx
If I had to select something for a team, I'd look into using Subversion
and Trac. We use TeamCoherence here and I'm reasonably satisfied with it.
TeamSystem is more than version control, so they are only comparable on
certain pieces. I didn't think that TeamSystem was included with an
MSDN subscription though. If you mean VSS, my experience with VSS has
been less than pleasant.
We're currently leaving TeamCoherence because of lack of support, and it seems the product is dying. We've been using it for both version control and tracking bugs.
Now, I've spent some time on this the last couple of weeks and it seems we will end up with the following:
1. Version Control, SubVersion. Why? It's free and we're spending all our bucks on the tracking software.
2. Tracking Software: AQdevTeam.
I personally wouldn't go for VSS as it seems to be a dying product too. Team System is the replacement for VSS, and Microsoft themselves are calling VSS a migration path to Team System. I would only use Team System if my code were 100% Visual Studio.
If I had unlimited amounts to spend on this I would probably go for Perforce as it seems many of the big guys are using it.
When I did my research I had plenty use of this page:
http://en.wikipedia.org/wiki/Comparison_of_revision_control_software
Enjoy!
Best Regards,
Tom Reiertsen
.
- Follow-Ups:
- Re: Version control
- From: Markus Humm
- Re: Version control
- From: Steve Troxell
- Re: Version control
- From: Nathaniel L. Walker
- Re: Version control
- References:
- Version control
- From: Brad White
- Re: Version control
- From: Brian Moelk
- Version control
- Prev by Date: Re: Version control
- Next by Date: Re: Delphi jobs
- Previous by thread: Re: Version control
- Next by thread: Re: Version control
- Index(es):
Relevant Pages
|