Christopher Browne wrote:
> 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 :-).
> 

I agree that it makes senes to wait to see what PostgreSQL decides to do 
for 9.1 (if anything) before we make a decision.

In the meantime I've posted my clone of the slony repository (from git 
cvsimport) on github at http://github.com/ssinger/slony (The 1.2 and 2.0 
branches are included) but there are no automatic syncs between that and 
the slony cvs repo.








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


-- 
Steve Singer
Afilias Canada
Data Services Developer
416-673-1142