On 2/8/06, Marc Brooks <[EMAIL PROTECTED]> wrote: > > Well, Team Server isn't even released yet, so I wouldn't put much stock into > > any stability reports on it yet. > > I would have to disagree... I've been using it for 4 months with a > small team, and Microsoft has been dogfooding it for much longer with > HUGE numbers of users and files. It's good. Check the dogfood > statistics http://blogs.msdn.com/johnlawr/archive/2006/01/31/516439.aspx > > > I've used a number of source control tools: > > > > VSS > > CVS > > PVCS
I mentioned VSS earlier. I worked with CVS and PVCS "in their heyday" because that's what was at the client site. In both cases, companies would be better off to hire someone with a library degree (yes, they have them), "technify" them, and have them work as the archival, retrieval, branch, merge, and anything else you can think of on a full-time, realtime basis. I know you have to put food on the table, even with inferior products, but those belong in the club of, "I'd rather be pushing a peanut with my nose up & down the entrance ramps of interstates giving people something to laugh at while they wait their turn to merge into traffic. There's no perfect software, but there has to be quality software. Those aren't the worst of the bunch but they are nowhere near the belonging on the tolerant list, either. p =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
