Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
On 12.12.17 09:14, Romain Manni-Bucau wrote: > This is the part I really don't understand since it will never work. Yes, I know. And I agree. But it's the process in commons as of now. Let's get this out of the door and save the discussion for later. Please? Bye, Thomas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
This is the part I really don't understand since it will never work. Either we respect the tag and therefore need yet another release to have a final which makes the RC pointless or we do not respect the tag which is worse IMHO. From my point of view it is way less hurting to not do the RC than doing it for literally nothing. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-12-12 9:09 GMT+01:00 Thomas Vandahl : > On 11.12.17 22:43, Romain Manni-Bucau wrote: >> I can drop the rc2, no problem but can you confirm rc3 will be this exact >> vote with revisions as only change? > > yes, and the RC-tag is probably required. > > 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
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
On 11.12.17 22:43, Romain Manni-Bucau wrote: > I can drop the rc2, no problem but can you confirm rc3 will be this exact > vote with revisions as only change? yes, and the RC-tag is probably required. Bye, Thomas. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Hmm, I can drop the rc2, no problem but can you confirm rc3 will be this exact vote with revisions as only change? If so can try next week yes. Le 11 déc. 2017 22:15, "Thomas Vandahl" a écrit : > Hi Romain, > > On 20.11.17 09:15, Romain Manni-Bucau wrote: > > do we have a real blocker on the release? Being said having the RC or > > not now is pointless since the tag is there, are we waiting for > > anything particular? Happy to drop the RC if it brings more confusion > > than it helps. > > Would you please drop RC2 and start a new round with RC3? I abstained > from voting because the vote mail did not follow the rules (SVN > revisions and stuff). Give it another try, ok? > > Bye, Thomas > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Hi Romain, On 20.11.17 09:15, Romain Manni-Bucau wrote: > do we have a real blocker on the release? Being said having the RC or > not now is pointless since the tag is there, are we waiting for > anything particular? Happy to drop the RC if it brings more confusion > than it helps. Would you please drop RC2 and start a new round with RC3? I abstained from voting because the vote mail did not follow the rules (SVN revisions and stuff). Give it another try, ok? Bye, Thomas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Hmmm, sorry Gary but I'm not sure how to read this answer. Le 9 déc. 2017 20:04, "Gary Gregory" a écrit : I know releasing is a pain but folks do it all the time, this is what we have released since the last board report: → *BCEL-6.1* was released on Sun Sep 17 2017 → *BCEL-6.2* was released on Thu Dec 07 2017 → *CODEC-1.11* was released on Thu Oct 19 2017 → *COMPRESS-1.15* was released on Mon Oct 16 2017 → *CONFIGURATION-2.2* was released on Wed Oct 11 2017 → *DAEMON-1.1.0* was released on Tue Nov 21 2017 → *IO-2.6* was released on Sat Oct 14 2017 → *JELLY-1.0.1* was released on Sat Sep 23 2017 → *LANG-3.7* was released on Tue Nov 07 2017 → *POOL-2.4.3* was released on Fri Oct 27 2017 → *VFS-2.2* was released on Thu Oct 05 2017 Personally, I do most steps manually instead of using the release plugin. YMMV. Gary On Sat, Dec 9, 2017 at 9:04 AM, Romain Manni-Bucau wrote: > Last up guys, from what has been said there is no clean way to do a > commons release (RC procedure *does not* work cause it does not enable > to do a final release through a copy) so the original vote mail is > probably the best compromise we can have today. Since the vote is a > bit old now I ping a last time to try to get the needed binding votes > and if we judge it must be cancelled/restarted I will just delete all > the stagings next week (probably friday). > > Romain Manni-Bucau > @rmannibucau | Blog | Old Blog | Github | LinkedIn > > > 2017-11-21 6:58 GMT+01:00 Romain Manni-Bucau : > > > > > > Le 20 nov. 2017 19:44, "Gary Gregory" a écrit : > > > > Please delete the tag > > https://svn.apache.org/repos/asf/commons/proper/jcs/tags/ > commons-jcs-2.2.1/ > > ; it should not exist since the software is not released. > > > > > > No, the RC should not exist. This one is the only correct one since it is > > aligned between version, name and source content. All other tag would be > > wrong and unusable for a vote and there is no other way to handle it on > svn > > except a branch which is not what we want. > > > > > > > > Personally, I'd like to see a clean VOTE email at the very least with all > > the bits in place in the message instead of reading through this whole > > thread again. > > > > If we also need another RC to pick up loose ends, then go ahead. This > > thread is so old by now (in VOTE 'years') and there are so many replies > > that I'd rather have a clean start (new VOTE and new RC.) but that's just > > me. > > > > Gary > > > > On Mon, Nov 20, 2017 at 1:15 AM, Romain Manni-Bucau < > rmannibu...@gmail.com> > > wrote: > > > >> Guys, > >> > >> do we have a real blocker on the release? Being said having the RC or > >> not now is pointless since the tag is there, are we waiting for > >> anything particular? Happy to drop the RC if it brings more confusion > >> than it helps. > >> > >> Romain Manni-Bucau > >> @rmannibucau | Blog | Old Blog | Github | LinkedIn > >> > >> > >> 2017-11-11 16:05 GMT+01:00 Thomas Vandahl : > >> > On 06.11.17 21:11, Romain Manni-Bucau wrote: > >> >> created http://svn.apache.org/repos/asf/commons/proper/jcs/tags/ > >> commons-jcs-2.2.1-RC2/ > >> >> (rev 1814438) > >> > > >> > Thanks, Romain. However, the POM file in this RC tag contains now > >> > > >> > --8<-- > >> > > >> > > >> > > >> > scm:svn:http://svn.apache.org/repos/asf/commons/proper/jcs/ > >> tags/commons-jcs-2.2.1 > >> > > >> > > >> > > >> > scm:svn:https://svn.apache.org/repos/asf/commons/proper/ > >> jcs/tags/commons-jcs-2.2.1 > >> > > >> > > >> > http://svn.apache.org/viewvc/commons/proper/jcs/tags/ > >> commons-jcs-2.2.1 > >> > > >> > > >> > --8<-- > >> > > >> > See my point? If you created the RC tag first and then copied, the > >> > scm-entries would still point to the RC tag. In this case, it's the > >> > other way round. It is difficult for me to see why this is believed to > >> > make sense. I'd prefer to match tag name and file content. > >> > > >> > 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 > >> > >> > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
I know releasing is a pain but folks do it all the time, this is what we have released since the last board report: → *BCEL-6.1* was released on Sun Sep 17 2017 → *BCEL-6.2* was released on Thu Dec 07 2017 → *CODEC-1.11* was released on Thu Oct 19 2017 → *COMPRESS-1.15* was released on Mon Oct 16 2017 → *CONFIGURATION-2.2* was released on Wed Oct 11 2017 → *DAEMON-1.1.0* was released on Tue Nov 21 2017 → *IO-2.6* was released on Sat Oct 14 2017 → *JELLY-1.0.1* was released on Sat Sep 23 2017 → *LANG-3.7* was released on Tue Nov 07 2017 → *POOL-2.4.3* was released on Fri Oct 27 2017 → *VFS-2.2* was released on Thu Oct 05 2017 Personally, I do most steps manually instead of using the release plugin. YMMV. Gary On Sat, Dec 9, 2017 at 9:04 AM, Romain Manni-Bucau wrote: > Last up guys, from what has been said there is no clean way to do a > commons release (RC procedure *does not* work cause it does not enable > to do a final release through a copy) so the original vote mail is > probably the best compromise we can have today. Since the vote is a > bit old now I ping a last time to try to get the needed binding votes > and if we judge it must be cancelled/restarted I will just delete all > the stagings next week (probably friday). > > Romain Manni-Bucau > @rmannibucau | Blog | Old Blog | Github | LinkedIn > > > 2017-11-21 6:58 GMT+01:00 Romain Manni-Bucau : > > > > > > Le 20 nov. 2017 19:44, "Gary Gregory" a écrit : > > > > Please delete the tag > > https://svn.apache.org/repos/asf/commons/proper/jcs/tags/ > commons-jcs-2.2.1/ > > ; it should not exist since the software is not released. > > > > > > No, the RC should not exist. This one is the only correct one since it is > > aligned between version, name and source content. All other tag would be > > wrong and unusable for a vote and there is no other way to handle it on > svn > > except a branch which is not what we want. > > > > > > > > Personally, I'd like to see a clean VOTE email at the very least with all > > the bits in place in the message instead of reading through this whole > > thread again. > > > > If we also need another RC to pick up loose ends, then go ahead. This > > thread is so old by now (in VOTE 'years') and there are so many replies > > that I'd rather have a clean start (new VOTE and new RC.) but that's just > > me. > > > > Gary > > > > On Mon, Nov 20, 2017 at 1:15 AM, Romain Manni-Bucau < > rmannibu...@gmail.com> > > wrote: > > > >> Guys, > >> > >> do we have a real blocker on the release? Being said having the RC or > >> not now is pointless since the tag is there, are we waiting for > >> anything particular? Happy to drop the RC if it brings more confusion > >> than it helps. > >> > >> Romain Manni-Bucau > >> @rmannibucau | Blog | Old Blog | Github | LinkedIn > >> > >> > >> 2017-11-11 16:05 GMT+01:00 Thomas Vandahl : > >> > On 06.11.17 21:11, Romain Manni-Bucau wrote: > >> >> created http://svn.apache.org/repos/asf/commons/proper/jcs/tags/ > >> commons-jcs-2.2.1-RC2/ > >> >> (rev 1814438) > >> > > >> > Thanks, Romain. However, the POM file in this RC tag contains now > >> > > >> > --8<-- > >> > > >> > > >> > > >> > scm:svn:http://svn.apache.org/repos/asf/commons/proper/jcs/ > >> tags/commons-jcs-2.2.1 > >> > > >> > > >> > > >> > scm:svn:https://svn.apache.org/repos/asf/commons/proper/ > >> jcs/tags/commons-jcs-2.2.1 > >> > > >> > > >> > http://svn.apache.org/viewvc/commons/proper/jcs/tags/ > >> commons-jcs-2.2.1 > >> > > >> > > >> > --8<-- > >> > > >> > See my point? If you created the RC tag first and then copied, the > >> > scm-entries would still point to the RC tag. In this case, it's the > >> > other way round. It is difficult for me to see why this is believed to > >> > make sense. I'd prefer to match tag name and file content. > >> > > >> > 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 > >> > >> > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Last up guys, from what has been said there is no clean way to do a commons release (RC procedure *does not* work cause it does not enable to do a final release through a copy) so the original vote mail is probably the best compromise we can have today. Since the vote is a bit old now I ping a last time to try to get the needed binding votes and if we judge it must be cancelled/restarted I will just delete all the stagings next week (probably friday). Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-11-21 6:58 GMT+01:00 Romain Manni-Bucau : > > > Le 20 nov. 2017 19:44, "Gary Gregory" a écrit : > > Please delete the tag > https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1/ > ; it should not exist since the software is not released. > > > No, the RC should not exist. This one is the only correct one since it is > aligned between version, name and source content. All other tag would be > wrong and unusable for a vote and there is no other way to handle it on svn > except a branch which is not what we want. > > > > Personally, I'd like to see a clean VOTE email at the very least with all > the bits in place in the message instead of reading through this whole > thread again. > > If we also need another RC to pick up loose ends, then go ahead. This > thread is so old by now (in VOTE 'years') and there are so many replies > that I'd rather have a clean start (new VOTE and new RC.) but that's just > me. > > Gary > > On Mon, Nov 20, 2017 at 1:15 AM, Romain Manni-Bucau > wrote: > >> Guys, >> >> do we have a real blocker on the release? Being said having the RC or >> not now is pointless since the tag is there, are we waiting for >> anything particular? Happy to drop the RC if it brings more confusion >> than it helps. >> >> Romain Manni-Bucau >> @rmannibucau | Blog | Old Blog | Github | LinkedIn >> >> >> 2017-11-11 16:05 GMT+01:00 Thomas Vandahl : >> > On 06.11.17 21:11, Romain Manni-Bucau wrote: >> >> created http://svn.apache.org/repos/asf/commons/proper/jcs/tags/ >> commons-jcs-2.2.1-RC2/ >> >> (rev 1814438) >> > >> > Thanks, Romain. However, the POM file in this RC tag contains now >> > >> > --8<-- >> > >> > >> > >> > scm:svn:http://svn.apache.org/repos/asf/commons/proper/jcs/ >> tags/commons-jcs-2.2.1 >> > >> > >> > >> > scm:svn:https://svn.apache.org/repos/asf/commons/proper/ >> jcs/tags/commons-jcs-2.2.1 >> > >> > >> > http://svn.apache.org/viewvc/commons/proper/jcs/tags/ >> commons-jcs-2.2.1 >> > >> > >> > --8<-- >> > >> > See my point? If you created the RC tag first and then copied, the >> > scm-entries would still point to the RC tag. In this case, it's the >> > other way round. It is difficult for me to see why this is believed to >> > make sense. I'd prefer to match tag name and file content. >> > >> > 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 >> >> > > - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Le 20 nov. 2017 19:44, "Gary Gregory" a écrit : Please delete the tag https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1/ ; it should not exist since the software is not released. No, the RC should not exist. This one is the only correct one since it is aligned between version, name and source content. All other tag would be wrong and unusable for a vote and there is no other way to handle it on svn except a branch which is not what we want. Personally, I'd like to see a clean VOTE email at the very least with all the bits in place in the message instead of reading through this whole thread again. If we also need another RC to pick up loose ends, then go ahead. This thread is so old by now (in VOTE 'years') and there are so many replies that I'd rather have a clean start (new VOTE and new RC.) but that's just me. Gary On Mon, Nov 20, 2017 at 1:15 AM, Romain Manni-Bucau wrote: > Guys, > > do we have a real blocker on the release? Being said having the RC or > not now is pointless since the tag is there, are we waiting for > anything particular? Happy to drop the RC if it brings more confusion > than it helps. > > Romain Manni-Bucau > @rmannibucau | Blog | Old Blog | Github | LinkedIn > > > 2017-11-11 16:05 GMT+01:00 Thomas Vandahl : > > On 06.11.17 21:11, Romain Manni-Bucau wrote: > >> created http://svn.apache.org/repos/asf/commons/proper/jcs/tags/ > commons-jcs-2.2.1-RC2/ > >> (rev 1814438) > > > > Thanks, Romain. However, the POM file in this RC tag contains now > > > > --8<-- > > > > > > > > scm:svn:http://svn.apache.org/repos/asf/commons/proper/jcs/ > tags/commons-jcs-2.2.1 > > > > > > > > scm:svn:https://svn.apache.org/repos/asf/commons/proper/ > jcs/tags/commons-jcs-2.2.1 > > > > > > http://svn.apache.org/viewvc/commons/proper/jcs/tags/ > commons-jcs-2.2.1 > > > > > > --8<-- > > > > See my point? If you created the RC tag first and then copied, the > > scm-entries would still point to the RC tag. In this case, it's the > > other way round. It is difficult for me to see why this is believed to > > make sense. I'd prefer to match tag name and file content. > > > > 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 > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Please delete the tag https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1/ ; it should not exist since the software is not released. Personally, I'd like to see a clean VOTE email at the very least with all the bits in place in the message instead of reading through this whole thread again. If we also need another RC to pick up loose ends, then go ahead. This thread is so old by now (in VOTE 'years') and there are so many replies that I'd rather have a clean start (new VOTE and new RC.) but that's just me. Gary On Mon, Nov 20, 2017 at 1:15 AM, Romain Manni-Bucau wrote: > Guys, > > do we have a real blocker on the release? Being said having the RC or > not now is pointless since the tag is there, are we waiting for > anything particular? Happy to drop the RC if it brings more confusion > than it helps. > > Romain Manni-Bucau > @rmannibucau | Blog | Old Blog | Github | LinkedIn > > > 2017-11-11 16:05 GMT+01:00 Thomas Vandahl : > > On 06.11.17 21:11, Romain Manni-Bucau wrote: > >> created http://svn.apache.org/repos/asf/commons/proper/jcs/tags/ > commons-jcs-2.2.1-RC2/ > >> (rev 1814438) > > > > Thanks, Romain. However, the POM file in this RC tag contains now > > > > --8<-- > > > > > > > > scm:svn:http://svn.apache.org/repos/asf/commons/proper/jcs/ > tags/commons-jcs-2.2.1 > > > > > > > > scm:svn:https://svn.apache.org/repos/asf/commons/proper/ > jcs/tags/commons-jcs-2.2.1 > > > > > > http://svn.apache.org/viewvc/commons/proper/jcs/tags/ > commons-jcs-2.2.1 > > > > > > --8<-- > > > > See my point? If you created the RC tag first and then copied, the > > scm-entries would still point to the RC tag. In this case, it's the > > other way round. It is difficult for me to see why this is believed to > > make sense. I'd prefer to match tag name and file content. > > > > 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 > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Guys, do we have a real blocker on the release? Being said having the RC or not now is pointless since the tag is there, are we waiting for anything particular? Happy to drop the RC if it brings more confusion than it helps. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-11-11 16:05 GMT+01:00 Thomas Vandahl : > On 06.11.17 21:11, Romain Manni-Bucau wrote: >> created >> http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC2/ >> (rev 1814438) > > Thanks, Romain. However, the POM file in this RC tag contains now > > --8<-- > > > > scm:svn:http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1 > > > > scm:svn:https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1 > > > http://svn.apache.org/viewvc/commons/proper/jcs/tags/commons-jcs-2.2.1 > > > --8<-- > > See my point? If you created the RC tag first and then copied, the > scm-entries would still point to the RC tag. In this case, it's the > other way round. It is difficult for me to see why this is believed to > make sense. I'd prefer to match tag name and file content. > > 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
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
On 06.11.17 21:11, Romain Manni-Bucau wrote: > created > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC2/ > (rev 1814438) Thanks, Romain. However, the POM file in this RC tag contains now --8<-- scm:svn:http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1 scm:svn:https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1 http://svn.apache.org/viewvc/commons/proper/jcs/tags/commons-jcs-2.2.1 --8<-- See my point? If you created the RC tag first and then copied, the scm-entries would still point to the RC tag. In this case, it's the other way round. It is difficult for me to see why this is believed to make sense. I'd prefer to match tag name and file content. Bye, Thomas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
created http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC2/ (rev 1814438) Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-11-06 20:46 GMT+01:00 Gary Gregory : > On Mon, Nov 6, 2017 at 11:11 AM, Thomas Vandahl wrote: > >> On 06.11.17 04:48, Gary Gregory wrote: >> > The document http://commons.apache.org/releases/prepare.html clearly >> shows >> > an example of an RC tag being labeled with the "RC1" postfix. >> >> Not in the maven-release-plugin chapter. And with reason. The problem of >> the later copy would be, that the tagged pom.xml contains the pathes to >> the tag created originally (read: with the RC suffix) so that if you >> checkout the copied tag (read: the release version), the settings in >> pom.xml will still point to the RC tag. >> >> Therefore, with a Maven build you should always create the release >> version, tag it, vote on it and let it be. If the vote fails, the tag >> can as well be removed. What's the point of keeping it around? The vote >> failed, after all. The tag is invalid anyway. >> > > The tag should not be removed. Ever. Look in svn and git and you will see > tags for every RC ever created. > > If you want to change the release requirements, well, that's another story. > Feel free to start a separate thread for that. For now I urge you to follow > the current release process. Yes, it is ponderous and requires many steps, > but creating a tag is not the biggest pain point. > > Gary > > >> BTW, using the SVN revisions given in the vote mail (this is why they >> are important), you can always access the failed RC tag, ok? >> >> 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
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
On Mon, Nov 6, 2017 at 11:11 AM, Thomas Vandahl wrote: > On 06.11.17 04:48, Gary Gregory wrote: > > The document http://commons.apache.org/releases/prepare.html clearly > shows > > an example of an RC tag being labeled with the "RC1" postfix. > > Not in the maven-release-plugin chapter. And with reason. The problem of > the later copy would be, that the tagged pom.xml contains the pathes to > the tag created originally (read: with the RC suffix) so that if you > checkout the copied tag (read: the release version), the settings in > pom.xml will still point to the RC tag. > > Therefore, with a Maven build you should always create the release > version, tag it, vote on it and let it be. If the vote fails, the tag > can as well be removed. What's the point of keeping it around? The vote > failed, after all. The tag is invalid anyway. > The tag should not be removed. Ever. Look in svn and git and you will see tags for every RC ever created. If you want to change the release requirements, well, that's another story. Feel free to start a separate thread for that. For now I urge you to follow the current release process. Yes, it is ponderous and requires many steps, but creating a tag is not the biggest pain point. Gary > BTW, using the SVN revisions given in the vote mail (this is why they > are important), you can always access the failed RC tag, ok? > > Bye, Thomas > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Think the idea was to avoid to have a tag which can have been checked out already but fundamentally agree there is no point to have such a rule and it just makes the project handling hard with no benefit in practise. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-11-06 19:11 GMT+01:00 Thomas Vandahl : > On 06.11.17 04:48, Gary Gregory wrote: >> The document http://commons.apache.org/releases/prepare.html clearly shows >> an example of an RC tag being labeled with the "RC1" postfix. > > Not in the maven-release-plugin chapter. And with reason. The problem of > the later copy would be, that the tagged pom.xml contains the pathes to > the tag created originally (read: with the RC suffix) so that if you > checkout the copied tag (read: the release version), the settings in > pom.xml will still point to the RC tag. > > Therefore, with a Maven build you should always create the release > version, tag it, vote on it and let it be. If the vote fails, the tag > can as well be removed. What's the point of keeping it around? The vote > failed, after all. The tag is invalid anyway. > > BTW, using the SVN revisions given in the vote mail (this is why they > are important), you can always access the failed RC tag, ok? > > 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
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
On 06.11.17 04:48, Gary Gregory wrote: > The document http://commons.apache.org/releases/prepare.html clearly shows > an example of an RC tag being labeled with the "RC1" postfix. Not in the maven-release-plugin chapter. And with reason. The problem of the later copy would be, that the tagged pom.xml contains the pathes to the tag created originally (read: with the RC suffix) so that if you checkout the copied tag (read: the release version), the settings in pom.xml will still point to the RC tag. Therefore, with a Maven build you should always create the release version, tag it, vote on it and let it be. If the vote fails, the tag can as well be removed. What's the point of keeping it around? The vote failed, after all. The tag is invalid anyway. BTW, using the SVN revisions given in the vote mail (this is why they are important), you can always access the failed RC tag, ok? Bye, Thomas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Hi, On Sun, Nov 5, 2017 at 11:26 PM, Romain Manni-Bucau wrote: > Answers inline. > > 2017-11-06 7:08 GMT+01:00 Gary Gregory : > > The blocker part is that the VOTE email does not follow the process or > the > > format outlined on http://commons.apache.org/releases/prepare.html > > > > Specifically, > > - the tag does not contain an "RC2" postfix (since this is the 2nd RC). > This tag is required. > > - there is not tag for RC1 so we've lost what we voted on for RC1 (too > late > > for that.) > > It is fine I think to not have the tags since they are "dead tags" > anyway. No need to recreate them now probably. > > > - the email does not contain the file names with hashes (see the email > > Nexus sent you when you "closed" the repository.) > > Will need to check but seems our nexus is not accessible ATM > You should have received an email from Nexus when you closed the repo. Gary > > > - the links to SVN resources do not contain SVN revision numbers > (required > > since SVN tags are mutable) > > r1809493 > > > > > This is all fixable without an RC3, you just need to send a VOTE email > that > > follows the format in http://commons.apache.org/releases/prepare.html > > > > Gary > > > > On Sun, Nov 5, 2017 at 10:55 PM, Romain Manni-Bucau < > rmannibu...@gmail.com> > > wrote: > > > >> Dist/Nexus is a manual step but ok. Rc creation is a blocker since it > >> prevent to use maven tools - release plugin. Did we - as commons - > already > >> open a feature request to maven? > >> > >> Anyway dont think it blocks the release *now* so can we proceed? > >> > >> Also moving to git can solve it by design too since we dont need to push > >> upstream the branch before the release is done. > >> > >> Le 6 nov. 2017 04:50, "Gary Gregory" a écrit : > >> > >> > On Sat, Oct 28, 2017 at 1:01 AM, Benedikt Ritter > >> > wrote: > >> > > >> > > > >> > > > >> > > > Am 27.10.2017 um 12:51 schrieb Thomas Vandahl : > >> > > > > >> > > > Hi Gary, > >> > > > > >> > > > On 25.10.17 05:24, Gary Gregory 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. > >> > > > > >> > > > as this release is created using the Maven Release plugin, the > >> > automatic > >> > > > process is to create a tag identical to the release version. The > docs > >> > > > you mention tell nothing about how to handle the RC case. Does > the RC > >> > > > tag need to be renamed, copied or re-created? > >> > > > > >> > > > BTW, there was no such request when I created the previous three > >> > > releases. > >> > > > >> > > I agree, we shouldn’t be to picky, since releasing components is > >> already > >> > a > >> > > PITA. > >> > > > >> > > >> > I agree that the release process is a PITA. I've complained about it > many > >> > times before on this ML but I've never contributed a solution to > improve > >> > the process. > >> > > >> > I think there is talk of improving the commons build plugin... but I > am > >> not > >> > sure how. > >> > > >> > Surely, having to publish to both "dist" and Nexus is a pain. > >> > > >> > Gary > >> > > >> > > >> > > > >> > > Benedikt > >> > > > >> > > > > >> > > > 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 > >> > > > >> > > > >> > > >> > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Answers inline. 2017-11-06 7:08 GMT+01:00 Gary Gregory : > The blocker part is that the VOTE email does not follow the process or the > format outlined on http://commons.apache.org/releases/prepare.html > > Specifically, > - the tag does not contain an "RC2" postfix (since this is the 2nd RC). > - there is not tag for RC1 so we've lost what we voted on for RC1 (too late > for that.) It is fine I think to not have the tags since they are "dead tags" anyway. No need to recreate them now probably. > - the email does not contain the file names with hashes (see the email > Nexus sent you when you "closed" the repository.) Will need to check but seems our nexus is not accessible ATM > - the links to SVN resources do not contain SVN revision numbers (required > since SVN tags are mutable) r1809493 > > This is all fixable without an RC3, you just need to send a VOTE email that > follows the format in http://commons.apache.org/releases/prepare.html > > Gary > > On Sun, Nov 5, 2017 at 10:55 PM, Romain Manni-Bucau > wrote: > >> Dist/Nexus is a manual step but ok. Rc creation is a blocker since it >> prevent to use maven tools - release plugin. Did we - as commons - already >> open a feature request to maven? >> >> Anyway dont think it blocks the release *now* so can we proceed? >> >> Also moving to git can solve it by design too since we dont need to push >> upstream the branch before the release is done. >> >> Le 6 nov. 2017 04:50, "Gary Gregory" a écrit : >> >> > On Sat, Oct 28, 2017 at 1:01 AM, Benedikt Ritter >> > wrote: >> > >> > > >> > > >> > > > Am 27.10.2017 um 12:51 schrieb Thomas Vandahl : >> > > > >> > > > Hi Gary, >> > > > >> > > > On 25.10.17 05:24, Gary Gregory 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. >> > > > >> > > > as this release is created using the Maven Release plugin, the >> > automatic >> > > > process is to create a tag identical to the release version. The docs >> > > > you mention tell nothing about how to handle the RC case. Does the RC >> > > > tag need to be renamed, copied or re-created? >> > > > >> > > > BTW, there was no such request when I created the previous three >> > > releases. >> > > >> > > I agree, we shouldn’t be to picky, since releasing components is >> already >> > a >> > > PITA. >> > > >> > >> > I agree that the release process is a PITA. I've complained about it many >> > times before on this ML but I've never contributed a solution to improve >> > the process. >> > >> > I think there is talk of improving the commons build plugin... but I am >> not >> > sure how. >> > >> > Surely, having to publish to both "dist" and Nexus is a pain. >> > >> > Gary >> > >> > >> > > >> > > Benedikt >> > > >> > > > >> > > > 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 >> > > >> > > >> > >> - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
The blocker part is that the VOTE email does not follow the process or the format outlined on http://commons.apache.org/releases/prepare.html Specifically, - the tag does not contain an "RC2" postfix (since this is the 2nd RC). - there is not tag for RC1 so we've lost what we voted on for RC1 (too late for that.) - the email does not contain the file names with hashes (see the email Nexus sent you when you "closed" the repository.) - the links to SVN resources do not contain SVN revision numbers (required since SVN tags are mutable) This is all fixable without an RC3, you just need to send a VOTE email that follows the format in http://commons.apache.org/releases/prepare.html Gary On Sun, Nov 5, 2017 at 10:55 PM, Romain Manni-Bucau wrote: > Dist/Nexus is a manual step but ok. Rc creation is a blocker since it > prevent to use maven tools - release plugin. Did we - as commons - already > open a feature request to maven? > > Anyway dont think it blocks the release *now* so can we proceed? > > Also moving to git can solve it by design too since we dont need to push > upstream the branch before the release is done. > > Le 6 nov. 2017 04:50, "Gary Gregory" a écrit : > > > On Sat, Oct 28, 2017 at 1:01 AM, Benedikt Ritter > > wrote: > > > > > > > > > > > > Am 27.10.2017 um 12:51 schrieb Thomas Vandahl : > > > > > > > > Hi Gary, > > > > > > > > On 25.10.17 05:24, Gary Gregory 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. > > > > > > > > as this release is created using the Maven Release plugin, the > > automatic > > > > process is to create a tag identical to the release version. The docs > > > > you mention tell nothing about how to handle the RC case. Does the RC > > > > tag need to be renamed, copied or re-created? > > > > > > > > BTW, there was no such request when I created the previous three > > > releases. > > > > > > I agree, we shouldn’t be to picky, since releasing components is > already > > a > > > PITA. > > > > > > > I agree that the release process is a PITA. I've complained about it many > > times before on this ML but I've never contributed a solution to improve > > the process. > > > > I think there is talk of improving the commons build plugin... but I am > not > > sure how. > > > > Surely, having to publish to both "dist" and Nexus is a pain. > > > > Gary > > > > > > > > > > Benedikt > > > > > > > > > > > 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 > > > > > > > > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Dist/Nexus is a manual step but ok. Rc creation is a blocker since it prevent to use maven tools - release plugin. Did we - as commons - already open a feature request to maven? Anyway dont think it blocks the release *now* so can we proceed? Also moving to git can solve it by design too since we dont need to push upstream the branch before the release is done. Le 6 nov. 2017 04:50, "Gary Gregory" a écrit : > On Sat, Oct 28, 2017 at 1:01 AM, Benedikt Ritter > wrote: > > > > > > > > Am 27.10.2017 um 12:51 schrieb Thomas Vandahl : > > > > > > Hi Gary, > > > > > > On 25.10.17 05:24, Gary Gregory 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. > > > > > > as this release is created using the Maven Release plugin, the > automatic > > > process is to create a tag identical to the release version. The docs > > > you mention tell nothing about how to handle the RC case. Does the RC > > > tag need to be renamed, copied or re-created? > > > > > > BTW, there was no such request when I created the previous three > > releases. > > > > I agree, we shouldn’t be to picky, since releasing components is already > a > > PITA. > > > > I agree that the release process is a PITA. I've complained about it many > times before on this ML but I've never contributed a solution to improve > the process. > > I think there is talk of improving the commons build plugin... but I am not > sure how. > > Surely, having to publish to both "dist" and Nexus is a pain. > > Gary > > > > > > Benedikt > > > > > > > > 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 > > > > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
On Sat, Oct 28, 2017 at 1:01 AM, Benedikt Ritter wrote: > > > > Am 27.10.2017 um 12:51 schrieb Thomas Vandahl : > > > > Hi Gary, > > > > On 25.10.17 05:24, Gary Gregory 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. > > > > as this release is created using the Maven Release plugin, the automatic > > process is to create a tag identical to the release version. The docs > > you mention tell nothing about how to handle the RC case. Does the RC > > tag need to be renamed, copied or re-created? > > > > BTW, there was no such request when I created the previous three > releases. > > I agree, we shouldn’t be to picky, since releasing components is already a > PITA. > I agree that the release process is a PITA. I've complained about it many times before on this ML but I've never contributed a solution to improve the process. I think there is talk of improving the commons build plugin... but I am not sure how. Surely, having to publish to both "dist" and Nexus is a pain. Gary > > Benedikt > > > > > 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 > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
On Fri, Oct 27, 2017 at 4:51 AM, Thomas Vandahl wrote: > Hi Gary, > > On 25.10.17 05:24, Gary Gregory 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. > > as this release is created using the Maven Release plugin, the automatic > process is to create a tag identical to the release version. The docs > you mention tell nothing about how to handle the RC case. Does the RC > tag need to be renamed, copied or re-created? > The document http://commons.apache.org/releases/prepare.html clearly shows an example of an RC tag being labeled with the "RC1" postfix. Gary > > BTW, there was no such request when I created the previous three releases. > > Bye, Thomas > > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
> Am 27.10.2017 um 12:51 schrieb Thomas Vandahl : > > Hi Gary, > > On 25.10.17 05:24, Gary Gregory 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. > > as this release is created using the Maven Release plugin, the automatic > process is to create a tag identical to the release version. The docs > you mention tell nothing about how to handle the RC case. Does the RC > tag need to be renamed, copied or re-created? > > BTW, there was no such request when I created the previous three releases. I agree, we shouldn’t be to picky, since releasing components is already a PITA. Benedikt > > 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
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Hi Gary, On 25.10.17 05:24, Gary Gregory 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. as this release is created using the Maven Release plugin, the automatic process is to create a tag identical to the release version. The docs you mention tell nothing about how to handle the RC case. Does the RC tag need to be renamed, copied or re-created? BTW, there was no such request when I created the previous three releases. Bye, Thomas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Ok, will try this week-end. Thanks for the feedback. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-10-25 6:42 GMT+02:00 Gary Gregory : > 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 > 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" a écrit : >> >> > On Tue, Oct 24, 2017 at 9:28 PM, kenneth mcfarland < >> > kennethpmcfarl...@gmail.com> 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" >> 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 < >> > > rmannibu...@gmail.com >> > > > > >> > > > 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" 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" < >> rmannibu...@gmail.com >> > > >> > > > > 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" >> 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" < >> > rmannibu...@gmail.com >> > > > >> > > > > > 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: 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
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
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 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" a écrit : > > > On Tue, Oct 24, 2017 at 9:28 PM, kenneth mcfarland < > > kennethpmcfarl...@gmail.com> 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" > 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 < > > > rmannibu...@gmail.com > > > > > > > > > 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" 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" < > rmannibu...@gmail.com > > > > > > > > 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" > 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" < > > rmannibu...@gmail.com > > > > > > > > > > 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: dev-unsubscr...@commons.apache.org > > > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
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" a écrit : > On Tue, Oct 24, 2017 at 9:28 PM, kenneth mcfarland < > kennethpmcfarl...@gmail.com> 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" 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 < > > rmannibu...@gmail.com > > > > > > > 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" 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" > > > > > 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" 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" < > rmannibu...@gmail.com > > > > > > > > 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: dev-unsubscr...@commons.apache.org > > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > > > > > > > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
On Tue, Oct 24, 2017 at 9:28 PM, kenneth mcfarland < kennethpmcfarl...@gmail.com> 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" 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 < > rmannibu...@gmail.com > > > > > 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" 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" > > > 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" 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" > > > > > 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: dev-unsubscr...@commons.apache.org > > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > > > > > > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
On 22 October 2017 at 16:17, Romain Manni-Bucau wrote: > So i just copy the mvn release tag? Sounds quite useless since the tag is > done no? > A release candidate is supposed to match the eventual release at some point; that's why it's a "candidate". Making a copy of an RC tag to make the final release tag makes perfect sense in that context. -- Matt Sicker
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
Gary, I can't help but say great work on all of these releases. #praise On Oct 24, 2017 8:24 PM, "Gary Gregory" 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 > > 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" 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" > > 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" 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" > > > 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: dev-unsubscr...@commons.apache.org > > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > > > > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
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 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" 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" > 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" 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" > > 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: dev-unsubscr...@commons.apache.org > > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
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" 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" 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" 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" > 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: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
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" 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" 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" 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: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org >
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
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" 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" 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: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [VOTE] Release Apache Commons JCS 2.2.1 (roll 2)
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" 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: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org