Version control
Brad White
We are looking for a replacement for VSS for
storing all of our Delphi code.
I'd like to go to Vault, http://www.sourcegear.com/vault/
but I know my boss is going to ask why we don't
use the team system stuff that comes with MSDN.
I can't find any comparisons that include TeamSystem.
--
Thanks,
Brad.
indy
easy to use, comes with msdn and its stable..
Why would you want to change otherwise?
"Brad White" <bwhite at inebraska.com> wrote in message
news:45421f33$1...@newsgroups.borland.com...
Brian Moelk
> If you're in for the full monty, go to perforce.. Otherwise I think VSS is
> easy to use, comes with msdn and its stable..
VSS <> TeamSystem.
--
Brian Moelk
Brain Endeavor LLC
bmo...@NObrainSPAMendeavorFOR.MEcom
Brian Moelk
> I'd like to go to Vault, http://www.sourcegear.com/vault/
> but I know my boss is going to ask why we don't
> use the team system stuff that comes with MSDN.
I like Vault, I use it at home. I don't know if I'd use it if I had to
pay for it (it's free for one user).
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.
> I can't find any comparisons that include TeamSystem.
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.
Eric Grange
"Stable" isn't really a qualifier suitable for VSS.
Eric
Tom Reiertsen
news:4542269a$1...@newsgroups.borland.com...
>
> 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.
>
> 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
Liz
> "Stable" isn't really a qualifier suitable for VSS.
I also never liked how VSS used to handle creating a new version.. it
may have changed since I last played with it (about 5 years)
--
Liz the Brit
Delphi things I have released: http://www.xcalibur.co.uk/DelphiThings
tony
I have been using Subversion along with the Turtle explorer shell
client and it works AMAZINGLY well. We used to use Team Coherence but
I now prefer Subversion and I don't have to spend gobs of cash to use
it.
Check it out.
Tony Caduto
AM Software Design
Home of Lightning Admin for MySQL and Postgresql
http://www.amsoftwaredesign.com
--
Nathaniel L. Walker
awesome.
There is a SCCI Source Control driver available for it, but Borland IDEs
don't support it without buying third-party software, blech.
- Nate.
"Tom Reiertsen" <t...@reiertsen.com> wrote in message
news:454228bb$1...@newsgroups.borland.com...
Tom Reiertsen
news:454231b1$1...@newsgroups.borland.com...
> Team System is a godsend, if you use all of its components it's just
> awesome.
>
> There is a SCCI Source Control driver available for it, but Borland IDEs
> don't support it without buying third-party software, blech.
>
But don't you have to use Visual Studio to check in/out files? Or is there a
standalone Team System client that you can use for that without using Visual
Studio at all?
Best Regards,
Tom Reiertsen
Eric Grange
> may have changed since I last played with it (about 5 years)
All developers that had to deal with it here only remember horror stories.
We've been running CVSNT here for about 3 years... 11k files in there,
about 1.7 GB of sources, resources and data... and not a single hiccup
or data loss in those 3 years.
Considered migrating to SVN sometime ago until we realized we were using
CVSNT and not CVS, so we already had the "pluses" claimed by SVN over
CVS. Guess we'll stick to it at least for a few more years.
And as a VCS client, Tortoise is just too comfy.
Eric
Steve Troxell
> We're currently leaving TeamCoherence because of lack of support, and it
> seems the product is dying.
I'll second that.
Steve Troxell
MRCarver
We have investigated all (most) version control systems to some degree,
and we ALWAYS return back to Borland's StarTeam. It is relatively
inexpensive if you just use the standard version, which comes with
Delphi Enterprise/Architect. WAY easier to install / configure / and
maintain than MS Team Source.
Any other option is a sacrifice in quality. Life is too short to futz
with an average tool (read sucky) that you use every day....
Just my 2cents..........
Regards,
Monte Carver
Nathaniel L. Walker
VS2005 IDE without all the development stuff for Team Foundation.
There's also an MSCCI API provider for Visual Studio Team
Foundation Version Control.
You don't have to be in VS to check in-out things. The Team Foundation
Explorer allows you to access all features of TFS (Documents, Work Items,
Source Control, etc.). The SCCI provider allows you to work with the
version control system the same way you would use something like
SourceSafe from within supported IDEs (except it's TFS VCS instead).
- Nate.
"Tom Reiertsen" <t...@reiertsen.com> wrote in message
news:4542332f$1...@newsgroups.borland.com...
Markus Humm
I also use StarTeam standard and I'm confident with it.
For bugtracking we're using a web based freeware tool named Mantis which
does the job for us.
Greetings
Markus
Markus Humm
I just added Borland StarTeam to that list:
>
> http://en.wikipedia.org/wiki/Comparison_of_revision_control_software
>
Maybe Borland likes to correct any pending mistakes I made?
Greetings
Markus
Brad White
news:45423621$1...@newsgroups.borland.com...
>> I also never liked how VSS used to handle creating a new version.. it
>> may have changed since I last played with it (about 5 years)
>
> All developers that had to deal with it here only remember horror stories.
>
> We've been running CVSNT here for about 3 years... 11k files in there,
> about 1.7 GB of sources, resources and data... and not a single hiccup or
> data loss in those 3 years.
Unfortunately, we are sitting at 12G in VSS.
I found out to late that they don't recommend
using it for over 2G. It apparently gets even
more unstable above that.
--
Thanks,
Brad.
Brad White
news:4542...@newsgroups.borland.com...
> If you're in for the full monty, go to perforce.. Otherwise I think VSS is
> easy to use, comes with msdn and its stable..
>
> Why would you want to change otherwise?
>
I completely agree. Well except for the part about being stable.
That's kinda' missing.
I did find it amusing that the MS pages describing it are
all excited about how it is a great transition to TeamSystem.
Really, that was the only positive thing I could find that they
had to say about it.
--
Thanks,
Brad.
Diego
I use and highly recommend Subversion, via TortoiseSVN. No need to pay
for version control, just use Subversion.
Nathaniel L. Walker
features that are very nice (like Team Systems storing its db via
SQL Server, and IDE integration).
It's all a matter of personal preference, and depends on what the
developer/organization deems important.
- Nate.
"Diego" <a@b.c> wrote in message news:4543...@newsgroups.borland.com...
Charles Pope
> about 1.7 GB of sources, resources and data... and not a single hiccup
> or data loss in those 3 years.
> Considered migrating to SVN sometime ago until we realized we were using
> CVSNT and not CVS, so we already had the "pluses" claimed by SVN over
> CVS. Guess we'll stick to it at least for a few more years.
>
> And as a VCS client, Tortoise is just too comfy.
>
> Eric
move to Subversion, mergepoints work well for instance. We came to the
same view.
However, I am still interested in a DARCS style distributed/patch type
system. A nice GUI front end to see a graphical view of the patches etc
would help me though.
Charles