I agree completely with your rankings of the tools, I just come down on the side of Mercurial rather than Bazaar.
I prefer the simplicity of Mercurial's approach. It doesn't ask you to first figure out how you're going to be using the repository. Bazaar's approach reminds me of doing object-oriented programming in lisp or lua or javascript. "It's so flexible!" they say. "You can implement classes and inheritance in all these different ways!" Bleh. Just give me one that works well and don't make me spend my time on such low-level decisions.
But Bazaar would be my #2 choice after Mercurial. It's certainly better than most.
--bb
On Mon, Oct 25, 2010 at 11:42 AM, Russel Winder
<russel@russel.org.uk> wrote:
On Mon, 2010-10-25 at 10:20 -0700, Bill Baxter wrote:
> I'm not a huge fan of Bazaar :-p ,
Hummm... May I ask why?
Personally I think Bazaar, Mercurial and Git beat Subversion, CVS,
ClearCase, TFS, etc. always. Moreover Bazaar and Mercurial beat Git.
Overall I see two different best cases for Bazaar and Mercurial --
basically when it is important for file hierarchy to be a branch vs
having everything all in one repository.
> but thanks for putting it up somewhere more amenable to collaborative
> revisioning than the wiki where it was!
> I'll take Bazaar over a bizarre wiki interface any day.
:-)
No problem. I have this hatred of source code being stored on wikis as
both the SCons and D communities now know :-)
--