On 14 April 2016 at 14:11, Benson Margulies <bimargul...@gmail.com> wrote: > On Thu, Apr 14, 2016 at 9:09 AM, Benson Margulies <bimargul...@gmail.com> > wrote: >> The instructions offer two approaches as equivalent: manual tagging >> and pom-editing, and the release plugin. >> >> If you just use the default options and hit <enter> a few times, >> you'll get the tag: commons-io-2.5, NOT commons-io-2.5-RCx. The manual >> process will, on the other hand, name the tag commons-io-2.5-RCx. >> >> It seems to me that the doc should mention this. > > However, there's more. The SCM elements in the pom will refer to the > RC tag, which is not what you want once the release is finalized. So I > think that the release plugin procedure has to be to let it create the > commons-io-2.5 tag, and then manually add the -RCx tag for the record.
-1 That sounds backwards. The commons-io-2.5 tag should only be created when the RCn vote has succeeded. It is created by copying the successful RCn tag. If you create the 2.5 tag first, and create RCn from it,what happens when the RCn vote fails or is withdrawn? That implies the 2.5 tag will have to be deleted and recreated. But tags are supposed to be immutable. I don't use the Maven Release plugin myself, partly because of such issues. But others who do may be able to clarify the instructions. > --------------------------------------------------------------------- > 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
