Il 26/04/2011 20:14, Julien Rioux ha scritto:
I don't feel the need to move to git. At all.
I'm seeing 2 discussions merged, in this thread:
1) what development model to use (how many branches, what & how often to
commit where, what & how often to release, etc.)
2) what development tools to use to implement (the proposed changes to) 1).
AFAICS vfr is actually asking for a lower number of merges into trunk,
with more testing made on alternate experimental branches, till the
features are rock stable, then merge them as a single (or a reduced
number of) commit. AFAICS, this can be done with svn as well as with git.
While I can share his viewpoint, as he's going through all of the
patches (!), I also suspect this will lead to a lower number of
developers having the chance to try a feature before the merge into main
trunk, because it's being developed in an alternate branch, and I'm not
sure everybody wants to download and synchronize tens of other branches,
with all the burden for compiling each one of them (unless you have a
48-core over which to do that).
Concerning the fragmentation of a feature into multiple patches, I'm
suspecting the point is not actually in svn vs git, but rather the key
is in the proper use of other tools (e.g., quilt or who knows what else)
which help in "managing patches".
So, I wish it could be clarified to other developers:
-) what model do we want to switch to -- concerning 1);
-) what advantages would git actually bring in the loop -- concerning 2)
-- but especially what other tools would it be necessary to learn.
My 2 cents. Thanks, bye,
T.
