I've been having a look through Mercurial's list of Hg hosting providers but can't really distinguish much about the real quality of the services.
What are other peoples' experiences with free services? Which would you recommend and why?
I've been having a look through Mercurial's list of Hg hosting providers but can't really distinguish much about the real quality of the services.
What are other peoples' experiences with free services? Which would you recommend and why?
I'm very new to Mercurial, but the consensus seems to be that BitBucket is the place to go.
NOTE: This seems to be a consensus only for open source projects, I'm not sure about closed source projects. It seems to me like their closed-source (private repositories) offering isn't too great.
Kiln is really nice, and the "students and startups" edition makes it free for 1 or 2 developers.
Google Code allows Mercurial repositories (along with SVN). Their service is very good, fast and reliable. Projects can have multiple "official" repos, and users can have personal repos of their own (but only as clones of other, public repos). They also only impose initial size limits (like 2GB for downloads), but you only need to ask to have it increased. The limits are there to prevent spam projects.
They also have a great web UI, which is something a lot of people don't care about until they've used a good one and then had to go back. A great online code review feature, a simple and easy to use wiki system, an amazing issue tracker etc.
I've used BitBucket too, and I think GC is better by a wide margin.
It's only for OSS projects though.
From my research - if you are interested in private repositories, then you are probably going to have to pay for them. Many of the services I've looked at charge based on the number of private repos but allow unlimited public repos. Having said that, some of the services are pretty cheap.
I asked a similar question back in January, but your post reminded me that I intended to update it with the research I did since. The best laid plans etc...
Anyway, I've updated it now and though my requirements were a little different (the driving force being issue tracking rather than just repository hosting) the answers there and the summary in the question, might be useful.