Re: [Exist-development] DVCS - Distributed Version Control?

[Adam R. <ad...@ex...>]

> 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?

Mercurial sounds very interesting and SourceForge even have some
support for it -

http://sourceforge.net/apps/trac/sourceforge/wiki/Mercurial

However, the biggest limitation in my mind is that write access to
repository can only be achieved over SSH.

Before we moved to Subversion, CVS used to be a major pain in the ass
for me, because I work from far too many locations (offices, airports,
trains, cafes etc) where the only access out is HTTP, Subversion works
perfectly over HTTP. If SourceForge were to enable Mercurial writes
over HTTP then I might be sold on the idea ;-)

> --
> Andrzej Taramina
> Chaeron Corporation: Enterprise System Solutions
> http://www.chaeron.com
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Exist-development mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-development
>



-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb