Hi Christian,
Christian Lohmaier wrote:
Hi Jan, *,
On Mon, Jan 15, 2007 at 02:50:41PM +0100, Jan Holesovsky wrote:
On Monday 15 January 2007 14:18, Kai Backman wrote:
On 1/15/07, Martin Hollmichel <[EMAIL PROTECTED]> wrote:
this. From my point of view the first step would be to review
centralized vs. distributed systems. What impact could the choice of an
SCM model have?
I think this question is not relevant. Git does not in itself decide
which type of development model we will be using. The Xorg developers
use a very centralized development model but Keith still reports they
benefit from the ability to work offline and check in local revisions.
This discussion is purely about the technical decision to replace one
tool in the process (CVS) with another (git).
Interestingly ;-) - from my point of view the OOo development model is closer
to the distributed development, than the centralized one. Each CWS is
supposed to be very self-contained, and it does not matter much if it's
developed inside the up-stream CVS (in a CWS), or in ooo-build as a patch.
The important thing is that the focus is up-stream - however long the
up-streaming could take.
How would one work together on a given cws if the changes are not
upstream?
Do you have to fiddle with 20+ Repository-URLs?
And: If the changes are not central anymore (not committed early), then
tinderbox and buildbot probably cannot test the cws during its
development.
Might be minor points, but definitely worth to consider IMHO.
It's definitely not a minor point, it's something that must be taken
into account. I had the need for early CWS code availability for
tinderbox and buildbots not yet in my check list for a new SCM system, I
missed that one completely, thanks for bringing it up. Of course, this
doesn't preclude a distributed SCM like Git per se but requires some
kind of early publishing framework, which I feel would be necessary anyway.
Heiner
--
Jens-Heiner Rechtien
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
