Personaly I think the Git stuff is more easy than it seems by the amount of mails we are sharing. But hope all this mails will serve for people to learn more about a better SCM system.
My vote counts like yours, but if there's many non-binding votes point to GIT and PPMCs vote for SVN but there's significante less votes, I think PPMC should considere to take into account the community option. If you have a project in SVN, migrate to GIT is easy. Even you can have a project be synced with both GIT and SVN at the same time. You can ignore files in SCMs to avoid commit files from svn to git and vicevecersa. 2012/8/14 João Fernandes <joaopedromartinsfernan...@gmail.com> > Carlos, I just can speak for myself and my vote counts nothing > (non-binding) but I'm willing to learn anything that is required but my > question is, besides the branching model to adopt, how much work is > required to have everything working under GIT? > Can it be a working process while code can keep being improved and fixed? > Can we use both side by side till everything is ready for GIT only? > > I'm not assuming we'll moving to GIT right away but as Bertrand mentioned, > we need to work as a team and if PPMC members aren't able to find a > strategy for Apache Flex when it comes to source control, how is it going > to work for code additions/changes? > > João Fernandes > -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 35 57 77 <http://www.codeoscopic.com> CODEOSCOPIC S.A. <http://www.codeoscopic.com> Avd. del General Perón, 32 Planta 10, Puertas P-Q 28020 Madrid
