I wish every flame was this considerate : ) I absolutely defer to CVS' performance/functionality advantages over M$ Sourcesafe (not to mention the cost), but I would argue that there are specific situations where it's an option worth considering (flinching ahead of times for flames :). I haven't setup of a SourceSafe repository, so I can't speak to it's ease of administration, but I can speak to working w/ it from a developer perspective. I found that it was pretty simple to work w/, but it sounds like that's a credit to the person who maintained it (they never really had any huge complaints on it though). I can understand those checkout times...our builds weren't as sizey as yours, but still took some time.
I would throw out SourceSafe as an option if you (or any team members) have never worked w/ CVS, you are under pressure to deploy some sort of version control, and you have a smaller development team (not to mention funding for the product). But I'd agree w/ you, Peter, in the sense that if you need higher levels of performance/functionality/robustness CVS is the way to go. ----- Original Message ----- From: "Peter Davison" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Tuesday, November 20, 2001 7:12 AM Subject: Re: CVS > > Consider yourself flamed. :-) > > My experience with VSS was that it "did not work". We actually had a person in one of our offices who > was responsible for "maintaining VSS" - this wasn't their only job of course, but it > consumed a great deal of their time. Our team was working on a separate unrelated module of > the project and were using CVS as the repository. I don't think that we had to do anything > as far as maintainence was concerned, just regular backups to tape (but that should be done > regardless). > > The other problem we had with VSS was trying to use remote access. We had another project > that we were collaborating on - several thousand files. It would take hours > to check out the project and this was over a T1. Through weeks of lobbying we were able to > convince our colleagues to switch to CVS. Check out times came down a few minutes. > They have never looked back. > > Just my $0.02. > > Regards, > Pete. > > > I may get flamed for this, but if you're organization is small you may want > > to consider M$'s Sourcesafe. It's concepts may be a little bit easier to > > adapt to if you have no experience w/ CVS. CVS is a great and powerful > > tool, but if you have no experience w/ it, you could run into some serious > > migration problems. > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > > > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
