On Saturday, 23 November 2013, Michael-O <[email protected]> wrote: > Am 2013-11-23 19:02, schrieb Hervé BOUTEMY: > >> I updated https://cwiki.apache.org/confluence/display/MAVEN/Git+Migrationwith >> .gitattributes instructions, and made a global cleanup >> Seems like plugin-tools is ready for migration, or even did it without >> having >> the page updated >> >> Now, I did not have any feedback about SCM report problems with git, >> solutions >> actually found (including link to github mirror): I added a section in the >> page. Feedback appreciated >> >> >> Then what do we really win with this git migration? Did it give us more >> contributions? >> I know what I lost (easy commit reference, SCM report, a lot of time >> dealing >> with unexpected state of my local clone, merge commit because bad rebase >> habits, ...) >> And nobody seems working on enhancements: Apache Jenkins has actually >> issues >> with git updates >> >> I hope someone really wins something with this git migration, because I >> really >> don't see benefits for myself >> > > In terms of contributions zero. If someone not keen enough to dig into > code and prepare a patch or are simply too lazy. > > Now -- you need to fork, clone, push, create a pull request. Even more > work. > > I don't see any benefit.
I often find the only time I get to work on maven is when I'm off-line. Svn stopped me doing more work on doxia because I wanted to commit per issue, not one big mess as I would have been trampling over myself. But on the other hand I think the real issue is what our issue has been for a long time... We are stuck with crappy modelVersion 4.0.0 until we get past that we cannot significantly evolve and grow in the direction people want to help us grow How often do we have people chime in on the M/L with some suggestion or wanting to try and fix something and we have to point out that we are still stuck with the modelVersion 4.0.0 problem? I think it is about ever 2-3 weeks... That's 20 potential committers we've list this year Git vs SVN is not the issue... The real issue is our major techical issue: schema migration (and how to not screw over all the pom parsers who we don't write but everyone else uses)... We've been dodging this issue for at least 3-4 years now... I think once 3.2 is out the door we need to finally tackle it head or give up and ask the board for the attic. -Stephen (speaking person opinions, *not* as PMC chair) > Michael > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Sent from my phone
