On Thu, Nov 10, 2005 at 11:07:57PM -0800, Jon A. Cruz wrote:
Well, I'm not quite sure that it speaks to an extreme need. We do have branches and different CVS modules for working out in, but many different developers have different work-styles and some prefer to play around a bit before going to far. It might be like a change from
It's true a lot of people have gotten used to CVS's way of doing things, and certainly it makes sense to stick with it for preventing having people forced to learn new things.
However, I've used a bunch of different scm's and while I still prefer CVS myself, I view subversion as a worthwhile conversion. First, it's similar enough to CVS that you won't be losing anything. Second, you gain the benefits that SVN provides. ;-)
There are several downsides to SVN but in my view they mostly boil down to provisioning. If we have someone to provide SVN service we're good, otherwise we have a host of issues.
Bryce