[Kde-scm-interest] Distributed model VS accountability

[Thiago Macieira]

Johannes Sixt wrote:
>Thiago Macieira schrieb:
>> Em Tuesday 27 November 2007 18:16:07 você escreveu:
>>> Both check out branch 'master'. Developer A pushes his fix onto
>>> branch 'master' into the repo. Developer B wants to push to 'master',
>>> but is denied, because his change does not fast-forward. So he must
>>> fetch again, rebase his fix on the new 'master', push again. If he's
>>> lucky and nobody else had pushed something in the meantime, he can
>>> ultimately push onto 'master'.
>>
>> This is the workflow that I had envisioned, yes.
>>
>> It requires a lot more fetch + rebase.
>
>This will not take off. DSCMs simply won't work in this way (once you
> have more than two people who are not within earshot). If you really
> mean to stay with this kind of workflow, then a transition to any DSCM
> will be a disaster.

This is not a choice: this is what I expect it will be based on how people 
work today and how little they like to change their behaviours.

We will have a lot of work in our hands educating people in the proper 
ways of using a distributed SCM. But they will still want to do pull + 
changes + push, then go home and forget about it.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-scm-interest/attachments/20071128/0a1e0fe5/attachment.pgp