Hi all, my team has moved from CVS to GIT few months ago and besides the obvious benefits there are two things that surprised us.
One is the speed of working with GIT, we were hoping to get more speedup and after the transition only branching is faster. Second thing is complication of versioning process. It turned out that if we would not have GIT expert onsite, we would probably went back to CVS due to misuses on our behalf. To sum it up, have at least one GIT expert in core team and don't expect too much. Best greetings, Paweł Wielgus. 2013/6/14 Dave Newton <[email protected]>: > +1 all 'round; the ability to work off-line on multiple branches, the > ability to cherry-pick merges, etc. is so helpful. > > I haven't done anything with versioned releases, not am I sure what the > best practice is. > > I have started using gitflow too, which seems nice, and a decent way to > normalize processes. > > Dave > On Jun 14, 2013 4:14 AM, "Christian Grobmeier" <[email protected]> wrote: > >> Hello, >> >> I would like to collect some feelings on GIT here. We have discussed a >> bit to move on to Git for S3. If we would vote on it today, what would >> you vote? >> >> Personally I would vote +1. >> >> There is of course a risk that things become complicated first. But >> there is a lot of experience with in ASF now. Finally we can create >> branches more easily (i have a feature I would love to see in a branch >> right now) and integration with GitHub et al is more easy too. >> >> I have tried Git at log4php and even the incubating projec tRipple. >> Those are much smaller than Struts, but given Apache Cordova is using >> Git successfully too, I am not so much afraid. >> >> What would you vote, and why? >> >> Cheers >> Christian >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
