From: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
---|---|
To: | PostgreSQL-development hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [Monotone-devel] Re: SCMS question |
Date: | 2007-02-23 17:26:33 |
Message-ID: | 3B40E171-4D4F-4271-8CD0-60FD7D69E47C@themactionfaction.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Feb 23, 2007, at 11:24 , Andreas Pflug wrote:
>>
> It probably _can_ never happen, because that would have to be a
> one-for-all solution, embracing both centric and distributed
> repositories, combining contradictionary goals. So the first
> question to
> answer is: Will PostgreSQL continue with a single repository (the
> project was managed very successfully this way for a long time), or
> try
> a distributed approach. IMHO facts would quote for a central
> repository,
> which would drastically reduce SCM candidates.
Any distributed SCM can be inherently be used as a central repo. The
project leaders would merely designate one place from whence builds
are generated and developers would simply sync with the "central" repo.
In fact, distributed SCMs fit the open source development model
better because any failure of the "central" repo (crash, buy-out,
sabotage, needing a project fork) cannot cause chaos: a new "central"
repo is designated- essentially an instant failover.
Cheers,
M
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2007-02-23 17:27:51 | Re: Simple Column reordering |
Previous Message | Jim C. Nasby | 2007-02-23 17:21:21 | Re: autovacuum next steps, take 2 |