[Scilab-Dev] Re: Re: Leaving SVN to GIT

[Jonathan Blanchard]

First It's true that I do not know the amount of contribution from the
community out of the INRIA. Indeed If external contribution are rare
it will not affect people too much.

Now on the other hand I really do not see how git will fix the problem
you just said. Commit are still made either to branch or trunk in git.
The model is not that different from svn you need to manually shift
around and merge stuff between branches and trunk. (Well that is the
way I see it). I mean each modification from the trunk will either be
fully merged on the branches or merged manually by selecting which
modification get merged into branches. Git work somewhat the same way.

I do not try to discourage your choice. I mean at the end it's
your(Scilab dev team) concerns and this could be more of a
philosophical debate but I do often use the svn repo as I'm coding
from the trunk and the idea of dealing with git is a bit discouraging.
Especially the type of work flow and repository structures git
encourage. Or maybe it's just me who fear changes :) (Or most of
Linus's opinions....).

Jonathan Blanchard



On Tue, Sep 30, 2008 at 11:45 AM, Sylvestre Ledru
<sylvestre.ledru at scilab.org> wrote:
> Le mercredi 24 septembre 2008 à 19:36 -0300, Jonathan Blanchard a
> écrit :
>> I do believe that git shift the
>> difficulty of working with a distributed revision system from the
>> projects managers toward the users and collaborators.
> Hmm, most of the developers of Scilab are working closely at the INRIA.
> We see each others every day. Therefor, shifting the difficulty upon the
> dev is no big deal.
>
> To detail why we need it, I can take an example how it is working now.
>
> At the moment, almost all the team & contributor are working on the
> current trunk.
> However, we have some people who are working on cleaning up and
> rewriting some functions in the  elementary functions module.
> These modifications are risky, therefor, we don't want to include them
> in the trunk but we want to be able to take modifications (on this
> module) from the trunk and merge them into this branch. For this, each
> night, an email is sent to the guy in charge of this to check if the
> modification on trunk/elementary_functions should be incorporated in his
> branch.
>
> It is a boring work and it is common to forget things...
>
> We intend to address this kind of issue.
>
> We also expect to develop collaborative works (ie, some guys working on
> a distinct branch and pushing in the master their work once it is good
> enough).
>
> Sylvestre
>
>
>