It's not a matter of thinking that git is like SVN at all. It's the exact opposite in fact; they are different, to the extent that it entails a whole new approach.
We have a well resourced, well understood, well supported tool and mature practices with our current SVN. All I am saying is that we really should stop and think as to whether we want to throw that out. I, personally am not convinced. At the end of the day, it's more about WHAT we produce (maven, plugins etc) than the TOOLS (SVN, git, etc) we use. For those who want to use git, fine stick with git SVN, but don't force me to learn a new tool; I do enough of that already. (and I've just come from a project where the personal preferences of a few immature devs forced the abandonment of good mature practices and had Hg shoved down our throats; and this is a $40 Billion dollar company, let's not make the same mistake here). -Chris Sent from my iPhone On 05/09/2012, at 9:41 PM, Arnaud Héritier <aherit...@gmail.com> wrote: > I think Olivier already replied to some points given few points where Git > is really interesting : performances, branches management .. > But yes there are skills to learn, it's not easy and the error is to think > that Git is like SVN > But it may be an opportunity to learn ? > > On Wed, Sep 5, 2012 at 1:38 PM, Chris Graham <chrisgw...@gmail.com> wrote: > >> -1 Non binding. >> >> I have no desire to setup and learn new tools for no clearly apparent >> advantages. >> There appears to be multitude of ways that DSCM's can be configured. I'm >> not sure if sufficient thought/discussion has been given to the way in >> which it should/can be set up. >> Where it is to be hosted? >> >> My view: Move got a good reason. A fad is not a good reason. >> >> -Chris >> >> On Wed, Sep 5, 2012 at 9:25 PM, Stephen Connolly < >> stephen.alan.conno...@gmail.com> wrote: >> >>> +1. Have no spare time ATM, so cannot volunteer even if I would love to >>> >>> On 5 September 2012 12:04, Olivier Lamy <ol...@apache.org> wrote: >>> >>>> Hi, >>>> This vote is to decide moving our source tree currently located in one >>>> svn repository to git (multiple git repositories). >>>> First, we need to have at least 3 volunteers to help on Apache infra >>>> for this move and more generally on git Apache infrastructure. (if you >>>> are volunteer you must say that with your vote). >>>> The vote will pass on majority (PMC committer) and if we have the >>>> minimum of 3 volunteers ! >>>> BTW contributors can express their opinion by a vote too ! >>>> The vote will decide on moving all the source tree (volunteers time >>>> will the main throttle). >>>> >>>> Volunteers will decide on what they move (notification on dev@ is >>>> mandatory). >>>> The goal is to move simple projects first(scm,surefire, indexer,core, >>>> wagon etc..) then plugins (except if Kristian want to start with >>>> plugins immediately :-) ) >>>> >>>> Vote open for 72H. >>>> >>>> [+1] Move to git scm >>>> [0] No interest >>>> [-1] don't move to git (please explain why) >>>> >>>> >>>> Thanks, >>>> -- >>>> Olivier Lamy >>>> Talend: http://coders.talend.com >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>>> For additional commands, e-mail: dev-h...@maven.apache.org >>>> >>>> >>> >> > > > > -- > ----- > Arnaud Héritier > 06-89-76-64-24 > http://aheritier.net > Mail/GTalk: aherit...@gmail.com > Twitter/Skype : aheritier --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
