[OT] SCM stories (war? horror?)
I'm preparing to make a case for switching to a differenct SCM tool (source code management). The options are CVS, Perforce, and VSS. Anybody have any cogent/credible stories or arguments for choosing one over the other? Thanks, Dennis
Re: [OT] SCM stories (war? horror?)
VSS- walk away, don't make eye contact :-) Pros: umm, it does manage versions, close integration with MS VisualStudio Cons: windows-only administration and probably access too, not intuitive to use, opaque binary files having no discernable relation to the actual artifacts themselves, not cheap to buy although most do not buy a license for every developer. The biggie though, sometimes the database will get corrupted and you will have to restore your repository from backup, although this may have been fixed. CVS- Pros: simple model for developers to understand how it works, changes can be made to local version without locking a file (some would consider this a con, so it can be changed), integrated into almost any open-source IDE and many OSS applications (such as cruise-control), trivial to access remote repository from local desktop, repository artifacts are stored as regular files rather than an opaque binary-format file Cons: directories not versioned, file moves are not versioned so if you want to preserve file history you have the hack of copying the file to the new location in a repository, and binary file versioning is non-existant--it stores a full copy of each version No experience with perforce. By the way, what is your current SCM? -ed On 9/16/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm preparing to make a case for switching to a differenct SCM tool (source code management). The options are CVS, Perforce, and VSS. Anybody have any cogent/credible stories or arguments for choosing one over the other? Thanks, Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] SCM stories (war? horror?)
[EMAIL PROTECTED] wrote: I'm preparing to make a case for switching to a differenct SCM tool (source code management). The options are CVS, Perforce, and VSS. Anybody have any cogent/credible stories or arguments for choosing one over the other? Thanks, Dennis CVS seems to be the de-facto standard for SCM tools that are integrated with IDEs. Subversion (SVN) is becoming more and more prevalent with new OSS projects and many IDEs are moving towards integration with it. If you don't use an IDE, then this will probably not be an issue. -david- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] SCM stories (war? horror?)
On 9/16/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm preparing to make a case for switching to a differenct SCM tool (source code management). The options are CVS, Perforce, and VSS. Anybody have any cogent/credible stories or arguments for choosing one over the other? Perforce: small, efficient, geeky, takes some getting used to after StarTeam or VSS. Nice feature - transactional check-in, that is, if error occurred when checking in a group of files, all group is not checked in. VSS: maybe now it is better, but 5 years ago it was very basic. CVS: Need to take care of CVS directories, if you remove them, then synchronization can be a problem. Though, I am not a CVS pro. Setting up a client takes some knowledge in regards to passwords and protocols. I could not set up WinCVS and installed TortoiseCVS instead. StarTeam: this is what we use now. Windows only, but pretty nice. Easy to see all versions of file, easy to compare versions. This is what I like about StarTeam: select a file and all its history with dates, comments are immediately in front of you. Moving Java class is a semi-manual process, since you need to update package name in the file too, and StarTeam cannot do this for you. Possible to edit unlocked file, and to merge later. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] SCM stories (war? horror?)
Seriously consider SVN, too if possible. From what I am hearing, all Apache projects will be on SVN within the next year. CVS is getting a bit long in the tooth but works well for everything i have ever needed. VSS is IMO a waste of digital storage that could have been better used for something like AOL CDs. :-D I looked at Perforce recently, but could not make the case for the $$$ over CVS. No added features (beyond VS.NET integration). Larry On 9/16/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm preparing to make a case for switching to a differenct SCM tool (source code management). The options are CVS, Perforce, and VSS. Anybody have any cogent/credible stories or arguments for choosing one over the other? Thanks, Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] SCM stories (war? horror?)
[EMAIL PROTECTED] wrote: I'm preparing to make a case for switching to a differenct SCM tool (source code management). The options are CVS, Perforce, and VSS. VSS: *hurl* I can' recall a time where I've ever thought Whew, thank goodness I'm using VSS and horror stories abound. Perforce: No experience, but one VERY large company I worked for used and generally liked it (although I remember them having a LOT of problems with the Eclipse Perforce plugin, probably fixed by now). CVS: Renaming, directories non-trivial/not supported. Didn't care for the tagging/branching stuff so much. Subversion: My current SCM of choice; trivial branching/tagging/merging, renaming, directories. Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] SCM stories (war? horror?)
I would avoid VSS at all costs, its merge capabilities are less than stellar, which makes it hard for two developers to change the same file. Perforce works well. I like the changelist concept and it integrates well with bug tools like TeamTrack, etc. Its biggest con is cost. CVS while very popular and works well, has some issues but those issues are well known and most projects know how to deal with them. Currently, we're using SVN on my project. I love it. It has great merge capabilities, the ability to atomically commit a set of files, it will be pretty familiar to CVS users. The biggest annoyance is how svn merge requires you to use URLs to the repository, but that's pretty small. If I were going to setup a new project I'd choose SVN. The price is right and does a good job as an SCM tool. Jesus Rodriguez Senior Software Engineer Red Hat Network [EMAIL PROTECTED] wrote: I'm preparing to make a case for switching to a differenct SCM tool (source code management). The options are CVS, Perforce, and VSS. Anybody have any cogent/credible stories or arguments for choosing one over the other? Thanks, Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] SCM stories (war? horror?)
[EMAIL PROTECTED] wrote: I'm preparing to make a case for switching to a differenct SCM tool (source code management). The options are CVS, Perforce, and VSS. Anybody have any cogent/credible stories or arguments for choosing one over the other? Don't touch Perforce with a barge pole it doesn't integrate very well with IDE's or Cruise Control etc and is a general pain in the arse. VSS, are you being serious...? Out of those three I'd take CVS every time, although you may want to look at Subversion as well. Cheers, -- Bob Arnott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [OT] SCM stories (war? horror?)
Ed (et al) VSS Pro:If your client is died in the wool dedicated to Microsoft environment and Visual Studio IDE and MS2k,MS2003 servers then VSS makes sense VSS Con: Keep in mind it is a fairly useless code control when ported to Unix or Mac..the reliance on NT attributes and file permissions is pervasive CVS Pro: Works everywhere and supports ssh ..login in once using ssh and you can update, delete or whatever..branch and merge work great CVS Con: The files of a cvs client can be manipulated thru regular shell commands e.g. rm -rf filename.ext removes the file (and cvs loses it as well) (if you're using CVS on a Unix box with lots of admins floating about..be safe take a backup every night) My 2 pennies/HTH Martin- - Original Message - From: Ed Griebel [EMAIL PROTECTED] To: Struts Users Mailing List user@struts.apache.org Sent: Friday, September 16, 2005 11:22 AM Subject: Re: [OT] SCM stories (war? horror?) VSS- walk away, don't make eye contact :-) Pros: umm, it does manage versions, close integration with MS VisualStudio Cons: windows-only administration and probably access too, not intuitive to use, opaque binary files having no discernable relation to the actual artifacts themselves, not cheap to buy although most do not buy a license for every developer. The biggie though, sometimes the database will get corrupted and you will have to restore your repository from backup, although this may have been fixed. CVS- Pros: simple model for developers to understand how it works, changes can be made to local version without locking a file (some would consider this a con, so it can be changed), integrated into almost any open-source IDE and many OSS applications (such as cruise-control), trivial to access remote repository from local desktop, repository artifacts are stored as regular files rather than an opaque binary-format file Cons: directories not versioned, file moves are not versioned so if you want to preserve file history you have the hack of copying the file to the new location in a repository, and binary file versioning is non-existant--it stores a full copy of each version No experience with perforce. By the way, what is your current SCM? -ed On 9/16/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm preparing to make a case for switching to a differenct SCM tool (source code management). The options are CVS, Perforce, and VSS. Anybody have any cogent/credible stories or arguments for choosing one over the other? Thanks, Dennis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
