IMO, you should redo the tag and rewrite the VOTE email following the template in http://commons.apache.org/releases/prepare.html
Gary On Tue, Oct 24, 2017 at 10:40 PM, Romain Manni-Bucau <[email protected]> wrote: > Hmm, > > Read that page but the answer is probably hidden in the commons parent - rc > property? - cause it is not written how a rc version ends in a not rc > version for binaries on nexus with the release plugin. Will check which > magic we do here later this week but anyway shouldnt block the release IMO > since already done, no? > > Le 25 oct. 2017 06:00, "Gary Gregory" <[email protected]> a écrit : > > > On Tue, Oct 24, 2017 at 9:28 PM, kenneth mcfarland < > > [email protected]> wrote: > > > > > Gary, I can't help but say great work on all of these releases. #praise > > > > > > > Thank you Kenneth. > > > > Gary > > > > > > > > > > On Oct 24, 2017 8:24 PM, "Gary Gregory" <[email protected]> > wrote: > > > > > > > Our process documented here http://commons.apache.org/ > > > > releases/prepare.html > > > > makes it pretty clear that the RC tag should be labeled as such and > > that > > > a > > > > tag like "commons-jcs-2.2.1" should only be created after a VOTE > > passes. > > > > > > > > Gary > > > > > > > > On Sun, Oct 22, 2017 at 3:17 PM, Romain Manni-Bucau < > > > [email protected] > > > > > > > > > wrote: > > > > > > > > > So i just copy the mvn release tag? Sounds quite useless since the > > tag > > > is > > > > > done no? > > > > > > > > > > Le 22 oct. 2017 21:14, "Gary Gregory" <[email protected]> a > > > écrit : > > > > > > > > > > > We need a tag for an RC in order to match a VOTE thread with the > > code > > > > > being > > > > > > proposed. > > > > > > > > > > > > Gary > > > > > > > > > > > > On Oct 22, 2017 10:24, "Romain Manni-Bucau" < > [email protected] > > > > > > > > wrote: > > > > > > > > > > > > > Revision is r1812876. > > > > > > > > > > > > > > Have to admit im not sure about the hack to use to have a rc > tag > > > > (name) > > > > > > > without rc artifacts which wouldnt match the target release > with > > > mvn > > > > > > > release plugin but dont think it is a blocker (but still happy > to > > > > learn > > > > > > it > > > > > > > ;)). > > > > > > > > > > > > > > Le 22 oct. 2017 17:29, "Gary Gregory" <[email protected]> > a > > > > > écrit : > > > > > > > > > > > > > > The tag name is wrong because it is not postfixed with RC2. All > > SVN > > > > > links > > > > > > > should be accompanied with a revision number. > > > > > > > > > > > > > > Gary > > > > > > > > > > > > > > On Oct 22, 2017 02:31, "Romain Manni-Bucau" < > > [email protected] > > > > > > > > > > wrote: > > > > > > > > > > > > > > Hello guys, > > > > > > > > > > > > > > I would like to release the [jcs] component to resolve a cdi > > > > > > > performance issue (JCS-183) and a bug in dispose method when > log > > > are > > > > > > > in debug level (JCS-184). > > > > > > > > > > > > > > Maven artifacts are at: > > > > > > > https://repository.apache.org/service/local/repositories/ > > > > > > > orgapachecommons-1281/ > > > > > > > > > > > > > > The Subversion tag is: > > > > > > > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/ > > > > > > commons-jcs-2.2.1/ > > > > > > > > > > > > > > The release notes are available at: > > > > > > > https://issues.apache.org/jira/projects/JCS/versions/12341663 > > > > > > > https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE- > > > NOTES.txt > > > > > > > > > > > > > > The staged sources and binaries are available at > > > > > > > https://dist.apache.org/repos/dist/dev/commons/jcs/ > > > > > > > > > > > > > > Please review the release candidate and vote. > > > > > > > > > > > > > > [ ] +1 Release these artifacts > > > > > > > [ ] +-0 don't care > > > > > > > [ ] -1 I oppose this release because ${reason} > > > > > > > > > > > > > > Romain Manni-Bucau > > > > > > > @rmannibucau | Blog | Old Blog | Github | LinkedIn > > > > > > > > > > > > > > ------------------------------------------------------------ > > > > --------- > > > > > > > To unsubscribe, e-mail: [email protected] > > > > > > > For additional commands, e-mail: [email protected] > > > > > > > > > > > > > > > > > > > > > > > > > > > >
