Version Control/Configuration Management/Bug tracking - Page 2

Do you have a question? Post it now! No Registration Necessary

Translate This Thread From English to

Threaded View
Re: Version Control/Configuration Management/Bug tracking
Quoted text here. Click to load it

I would throw in SubVersion. This is a GNU (I think) licensed
version-control system with many improvements over CVS. It's still in beta
but usable. It supports atomic checkins, binary files, directories, moves
and renames, etc. It has an HTTP base (webdav actually) client-server
protocol so it plays nicely with firewalls and proxies, and provides
security too if you use the HTTPS transfer protocol. One drawnback I
discovered is speed. Still, I kind of like it. The project I use it for is
~1GB in size.

Regrads,
Andras Tantos



Re: Version Control/Configuration Management/Bug tracking
Quoted text here. Click to load it

I'm not about to risk my company's past and future code and
documentation base on something thats "still in beta".


Cheers
TW

Re: Version Control/Configuration Management/Bug tracking

Quoted text here. Click to load it
beta

Remember that different people have different ideas about when code changes
from "beta" to "release" - I've seen plenty of commercial software that I
wouldn't even give an "alpha" classification.  Subversion beta may be far
more stable and reliable than certain other version control software for
which you pay plenty of money (other posters have complained about certain
other commercial version control software - I haven't tried it myself, and
don't intend to).  But it is worth noting that subversion is being actively
developed, and they have made changes that required a dump/restore of the
data (although they tell you about it) due to format changes.  It's got more
features than cvs, but is less mature - take your choice.

From the subversion faq:


Is Subversion stable enough for me to use for my own projects?

We think so! Subversion has small bugs here and there, but in general is
reliable enough for real use. If it were any other project, it probably
would have been declared "1.0" long ago; but because it's version-control
software, we're being extra paranoid about labeling.
We believe that Subversion is stable and have confidence in our code, in
fact, we've been self-hosting since September of 2001--eating our own caviar
so to speak. We declared "alpha" because we're ready for the world to try
Subversion.
After nearly two years of self-hosting, we haven't lost any data at all.





Re: Version Control/Configuration Management/Bug tracking
On 10 Oct 2003 02:34:44 -0700, snipped-for-privacy@ornette.freeserve.co.uk (Ted

Quoted text here. Click to load it

For Windows development platforms, we use PVCS Version Manager & PVCS
Tracker for defect reporting. The two work together & there can be
associations established between source versions and Tracker issues.

Ken.

+====================================+
I hate junk email. Please direct any
genuine email to: kenlee at hotpop.com

Re: Version Control/Configuration Management/Bug tracking
snipped-for-privacy@noname.com (Ken Lee) wrote in message
Quoted text here. Click to load it

Ken

We've just had Merant in to demo PVCS.
You don't seem to be able to branch at a project level. Is that right?
We were told that PVCS could only branch on a file by file basis.
Is that correct?

Cheers
TW

Re: Version Control/Configuration Management/Bug tracking
On 15 Oct 2003 04:43:59 -0700, snipped-for-privacy@ornette.freeserve.co.uk (Ted

Quoted text here. Click to load it

I haven't needed to branch at the project level, but you're probably
right. Basically we manage product variants by using file branching &
judicious labelling. I'm not an advocate of branching & would
recommend that for an extensive product variant, a complete copy of
the project would be preferable.

Ken.

+====================================+
I hate junk email. Please direct any
genuine email to: kenlee at hotpop.com

Site Timeline