[Exist-development] DVCS - Distributed Version Control?

[Andrzej J. T. <an...@ch...>]

Guys (hey...don't we need some female eXist developers? ;-) ):

I believe that some of the problems that we've seen with functions spread across multiple commits, partial commits of
new features and the like might be partially due to, or at least exacerbated, by our use of a "classic" source code
control system like Subversion.  Branches and merges are a real pain with a tool like Subversion for anything beyond
simple changes.

Now don't get me wrong....I've used Subversion for a long time and like it, and do not relish learning a new approach or
giving up my current SVN tool of choice (the Oxygen SVNClient tool)....

But as our ranks get larger and the subprojects people are interested in and work on become bigger and more elaborate,
maybe we should consider moving to a DVCS - Distributed Version Control system, which would provide much more flexible
and easier branch/merge capability?  Might help alleviate some of the issues in the longer term.

Something like GIT or Mercurial....

For those not familiar with DVCS's, Joel Spolsky posted a great article on DVCSs here:

	http://www.joelonsoftware.com/items/2010/03/17.html

Thoughts?

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com