Lan Barnes wrote: > Thanks, Matt, solid experience to share. I am forwarding it. > > My major gripe is the lack of true (data based) version labels.
Can't the "memo" for a version serve that purpose? > Also, I've > become quite fond of change sets, and can't remember if svn supports > those. I tend to drop SW as soon as I decide it doesn't have the > facilities I need. Not sure what a changeset is. Do you mean an easy way to find the difference between 2 versions? svn diff can do that for you. > But svn is a godsend to web based OSS projects. Why is svn great for *web* based projects? > A buddy of mine worked in a commercial shop that used Svn, and he agrees > that it's not ready for the enterprise. The lack of > merge/branch/integration history was a real pain in the rump for him. Not sure what you mean....every commit and every branch creation requires creation of comments and history to go along with it. > It also lacks (lacked?) a decent integration with Microsoft tools. TortoiseSVN? > I didn't > even consider deploying it at my current company because I knew we'd have > at least a couple of branches, and literally some sort of deployment every > day. I wouldn't have time for anything else but Svn admin. Creating a branch is easy in SVN. Not sure what your problem is with branches. Merging is bad in SVN but I heard they are working on that. cs -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
