Stuart Bishop <stuart at stuartbishop.net> writes:
> On Sat, Apr 24, 2010 at 2:59 AM, Christopher Browne
> <cbbrowne at ca.afilias.info> wrote:
>
>> I'd think a "short list" of plausible SCMs would consist of subversion,
>> git, mercurial, darcs.  Subversion *wouldn't* help with the "distributed
>> backups" aspect, which goes a long ways towards disqualifying it, to my
>> mind.
>
> And GNU Bazaar of course. If anybody wants a play, there is already an
> import available at
> https://code.launchpad.net/~vcs-imports/slony-i/trunk. Just install a
> modern version of Bazaar and 'bzr branch lp:slony-i' to get started. I
> recommend 2.1. http://bazaar-vcs.org for more information, including
> the excellent documentation at
> http://doc.bazaar.canonical.com/bzr.2.1/en/.
>
> I'm available for questions, but I'm not going to be a committer in
> the foreseeable future and will leave the discussion to those who are
> going to use the VCS.

You're right, if we're considering a list that includes Mercurial and
Darcs, then Bazaar ought to be on that list.  (Slightly embarrassing
that I forgot about it!)

On the other hand, there's a reasonably strong reason to prefer Git, in
that the PostgreSQL project appears to be seriously contemplating using
Git, and there would be a fair bit of value in allowing peoples'
learning curves (in learning about Git for PostgreSQL work) to pay off
twice.

My own preference would be to wait until there's a bit more indication
of the certainty (or lack thereof!) of PostgreSQL migration, hence
waiting 'til, say, early June to decide for sure.  That's just my
preference :-).

Does that repo track all the branches?  [Possibly a lazy question!  :-)]
It would seem like a keen idea to have a repo or two up, and track them
for a while, before deciding to change anything.
-- 
output = reverse("ofni.sailifa.ac" "@" "enworbbc")
Christopher Browne
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"