Will not recopy what i said in jcs vote thread but git solves it creating the tag locally so you can immediately copy it *locally* and only push the rc tag for the vote duration. That said most of communities push the tag on a fork and avoid any issue with the asf repo. This is how git can solve that issue.
2017-11-06 19:16 GMT+01:00 Thomas Vandahl <t...@apache.org>: > On 06.11.17 09:01, Romain Manni-Bucau wrote: >> 2017-11-06 8:59 GMT+01:00 Jochen Wiedmann <jochen.wiedm...@gmail.com>: >>> On Mon, Nov 6, 2017 at 7:27 AM, Romain Manni-Bucau >>> <rmannibu...@gmail.com> wrote: >>> >>>> due to the RCx procedure we cant use the maven release plugin, any >>>> plan to make it working with commons release procedure or do we just >>>> wait to move all to git? >>> >>> What problem is there when using the plugin? >> >> the plugin doesn't support the RCx branch creation without corrupting >> the final release - due to nexus. It would be fancy to be able to >> *automatically* create the right tag if flagged as such in the pom. > > There is nothing wrong with the plugin. If you read the commons release > docs, the chapter about the maven-release-plugin says nothing about RCs, > let alone tags. Moving to git would not help as long as the POM > scm-section still points to the original tag. (And I'm not suggesting to > change that!) > > Bye, Thomas. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
