My experiences with Mercurial

[Michael P. Soulier]

On 17/06/07 Milen Dzhumerov said:

> Hi all,
> 
> I just wanted to describe my experiences with Mercurial and let you  
> know why we're going to be using subversion for now. The main reasons  
> for considering Mercurial were:
> 
> 1. Distributed model
> 2. Works on Windows & Unix
> 3. It's fast
> 
> We decided that there was no point _for us_ to deploy Mercurial in a  
> centralised fashion - we would then just keep on using subversion. As  
> the source which we're tracking is closed, we cannot afford not to  
> encrypt the traffic. So really what we need is a simple & secure way  
> for the users (developers in this case) to share their changesets.  
> "hg serve" seems to fit the definition of simple but not secure. The  
> trouble of setting up IIS/Apache and configuring SSL or setting up  
> ssh servers on each developer's machine (win & unix) outweighs the  
> benefits of using mercurial. We were mainly looking to remove the  
> need for the central server.
> 
> So my question really is, are the developers looking to incorporate  
> SSL into the built-in "hg serve" server? Has the unencrypted (non- 
> SSL) built-in server been a problem for anyone else or is it just us?  
> We're going back to using subversion because it's much easier for us  
> to set up the central server once instead of setting up each client  
> to act as a server/client.

I would say that you are overestimating the amount of time required to
accomplish this. I can set up a centralized svn or hg repository in the same
amount of time. 

Pushing changes to windows clients directly via ssh is non-trivial, yes, as
windows does not support ssh natively. You likely wouldn't want to give write
access in that fashion anyway. 

I would push changes to a central location, and integration branch if you
will, run nightly builds there, and if they pass, push those changes to a head
branch that everyone can then pull from. 

Or, you could simply email patches around, and encrypt them with PGP or even
S/MIME, although the latter is commercial. 

Is there some reason why you can't run hgweb from behind apache+ssl? I do that
and it works fine. 

Cheers,
Mike
-- 
Michael P. Soulier <msoulier at digitaltorque.ca>
"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the opposite
direction." --Albert Einstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20070617/bb9098e8/attachment-0001.asc>