Bo Peng wrote:
Not quite true. In a git world, a bug fixing would _always_ happen in a
specific branch and be merged to the main repo when it's done;
This is not that useful if we keep the one developer - one feature
developing model. Right now, when you work on a feature, all others
are forced to check it out and test for you. If you use git, your
feature is unlikely to be well tested (if no one else check out your
branch) before merge and bigger merges just increase the chance of
conflict and decrease early review.
IMHO, we do not have enough manpower to use the git model.
Well, we are not _forced_ to use only one merging per feature, this can
be split into logical steps (at the intiative of the developer). But
this is the first good argument I hear indeed.
Abdel
