Hi I think that we have landed at this: whoever feel like moving something to git announces it to the dev community and if no one objects then goes ahead with the move.
That being said, maven-release is a vital component in this case. We need to be absolutely certain that the release-plugin work correctly for our project/module setup (directory structure) when using git. If it doesn't we could end up in a situation where we need to patch maven-release, but can't release it because maven-release is busted when using git. Now I'm not saying it is busted, although there has been numerous bugs reported on the subject. We just need to sure that it is good enough. I am not that good with git, so I will let others be the judge as to whether git support in maven-release is good enough. Apart from this I have no objections to move maven-release to git. On Sat, Sep 13, 2014 at 6:10 PM, Benson Margulies <[email protected]> wrote: > Since I'm planning a release, it occurs to me that this would be a > convenient moment to move this project. Did we decide to just migrate > things like this with no further discussion, or do we decide one by one? -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
