Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 9/7/18 2:11 PM, sebb wrote: > If the tag contains files that are not in the distribution, why are > they present at all? Because they are experimental code, for example. Not ready for prime time. > If they are needed, why are they not in the distribution? They are not needed, at least not

[RESULT][VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 8/23/18 5:32 PM, Thomas Vandahl wrote: > I would like to make another attempt to release Apache Commons JCS 2.2.1 > (a bugfix release) > > Apache Commons JCS 2.2.1 RC4 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/jcs/ (svn revision 28918) Time to wrap up.

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 6 September 2018 at 17:24, Thomas Vandahl wrote: > On 27.08.18 18:12, Benedikt Ritter wrote: >> ~/w/a/r/r/t/jcs git:(upstream ⚡ master) > diff -r commons-jcs-2.2.1-RC4/ >> commons-jcs-2.2.1-src >> Only in commons-jcs-2.2.1-RC4/: .gitignore >> Only in commons-jcs-2.2.1-RC4/: .svn >> Only in

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 27.08.18 18:12, Benedikt Ritter wrote: > ~/w/a/r/r/t/jcs git:(upstream ⚡ master) > diff -r commons-jcs-2.2.1-RC4/ > commons-jcs-2.2.1-src > Only in commons-jcs-2.2.1-RC4/: .gitignore > Only in commons-jcs-2.2.1-RC4/: .svn > Only in commons-jcs-2.2.1-RC4/: .travis.yml > Only in

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

be in the future we can exclude it from the site menu, to prevent the 404. Cheers Bruno From: Thomas Vandahl To: Commons Developers List Sent: Thursday, 6 September 2018 5:06 AM Subject: Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4 On 23.08.18 17:

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 23.08.18 17:32, Thomas Vandahl wrote: > I would like to make another attempt to release Apache Commons JCS 2.2.1 > (a bugfix release) > > Apache Commons JCS 2.2.1 RC4 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/jcs/ (svn revision 28918) Could I please ask

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 27 August 2018 at 17:12, Benedikt Ritter wrote: > Hi, > > - sigs and hashes are good > - builds fine with maven 3.5.4 from src distribution > - website looks good > - release notes look good > - there are some differences between the src distribution and release tag: > > ~/w/a/r/r/t/jcs

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

Hi, - sigs and hashes are good - builds fine with maven 3.5.4 from src distribution - website looks good - release notes look good - there are some differences between the src distribution and release tag: ~/w/a/r/r/t/jcs git:(upstream ⚡ master) > diff -r commons-jcs-2.2.1-RC4/

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

+1, thanks Le jeu. 23 août 2018 20:07, Thomas Vandahl a écrit : > On 23.08.18 17:32, Thomas Vandahl wrote: > > I would like to make another attempt to release Apache Commons JCS 2.2.1 > > (a bugfix release) > > > > Apache Commons JCS 2.2.1 RC4 is available for review here: > > > [X] +1

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

On 23.08.18 17:32, Thomas Vandahl wrote: > I would like to make another attempt to release Apache Commons JCS 2.2.1 > (a bugfix release) > > Apache Commons JCS 2.2.1 RC4 is available for review here: > [X] +1 Release these artifacts Bye, Thomas

[VOTE] Release Apache Commons JCS 2.2.1 based on RC4

I would like to make another attempt to release Apache Commons JCS 2.2.1 (a bugfix release) Apache Commons JCS 2.2.1 RC4 is available for review here: https://dist.apache.org/repos/dist/dev/commons/jcs/ (svn revision 28918) The SVN tag commons-jcs-2.2.1-RC4 commit for this RC4 is here:

[CANCEL][VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

cancelling then (and updating the subject) Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-12-12 17:13 GMT+01:00 Thomas Vandahl : > On 12.12.17 09:14, Romain Manni-Bucau wrote: >> This is the part I really don't understand since it will never work. >

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

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

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

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

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

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 →

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

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

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

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

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

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<--

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

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

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

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

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

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

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

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

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

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 > >

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

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

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

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

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

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

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

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

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

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

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

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"

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

[VOTE] Release Apache Commons JCS 2.2.1 (roll 2)

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

Re: [CANCEL][VOTE] Release Apache Commons JCS 2.2.1

Hello guys A quick ping to say I ll try to work on that this week end (from 2.2.x branch). If you need to merge anything or want to do some jira tweak this is the time before the "review". Le 29 sept. 2017 18:34, "Romain Manni-Bucau" a écrit : > Cancelling then :(.

[CANCEL][VOTE] Release Apache Commons JCS 2.2.1

Cancelling then :(. Thanks guys for your help and feedbacks. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: [VOTE] Release Apache Commons JCS 2.2.1

On 28.09.17 19:23, Romain Manni-Bucau wrote: > Do I need to cancel this vote? Cant relaunch a vote before ~2 weeks if so > (will be travelling) but happy to catch up after if you think it is the way > to go. I'm afraid so. You published 2.2.2-SNAPSHOT to the release area. You probably need to

Re: [VOTE] Release Apache Commons JCS 2.2.1

Do I need to cancel this vote? Cant relaunch a vote before ~2 weeks if so (will be travelling) but happy to catch up after if you think it is the way to go. Le 28 sept. 2017 19:13, "Gary Gregory" a écrit : > The file >

Re: [VOTE] Release Apache Commons JCS 2.2.1

The file https://dist.apache.org/repos/dist/dev/commons/jcs/source/commons-jcs-dist-2.2.2-SNAPSHOT-src.zip looks like it has the right folders... :-) Gary On Thu, Sep 28, 2017 at 10:37 AM, Romain Manni-Bucau wrote: > tried to reupdate the dist area, can you let me know

Re: [VOTE] Release Apache Commons JCS 2.2.1

tried to reupdate the dist area, can you let me know if it is better this way please? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github |

Re: [VOTE] Release Apache Commons JCS 2.2.1

Hi Gary, I added a zip of the site in the dist/dev area. Will try to fix the source bundle tonight once I get back my computer (and my key ;)). Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: [VOTE] Release Apache Commons JCS 2.2.1

You really need to publish a site for an RC IMO so I can compare your reports to mine (CLIRR, RAT in particular). Gary On Wed, Sep 27, 2017 at 1:40 PM, Romain Manni-Bucau wrote: > Hi Thomas > > Didn't run the site one yet - was planned post vote - but did the others >

Re: [VOTE] Release Apache Commons JCS 2.2.1

On 27.09.17 21:40, Romain Manni-Bucau wrote: > Didn't run the site one yet - was planned post vote - but did the others > without the profile since it is configured to be added automatically. Is it > an issue? It might be. I copied these from my actual shell history, so I know them to work. Bye,

Re: [VOTE] Release Apache Commons JCS 2.2.1

Hi Thomas Didn't run the site one yet - was planned post vote - but did the others without the profile since it is configured to be added automatically. Is it an issue? Le 27 sept. 2017 21:06, "Thomas Vandahl" a écrit : On 25.09.17 17:47, Gary Gregory wrote: > -1 > > The file

Re: [VOTE] Release Apache Commons JCS 2.2.1

On 25.09.17 17:47, Gary Gregory wrote: > -1 > > The file > https://dist.apache.org/repos/dist/dev/commons/jcs/source/commons-jcs-dist-2.2.1-src.zip > does not contain any of the modules folders. > Hi Romain, did you do mvn -Duser.name=rmannibucau -Prelease release:prepare mvn

Re: [VOTE] Release Apache Commons JCS 2.2.1

Have to admit I'm not 100% sure how dist module is intended to work (probably a 2 phases build?) but since we don't deploy it on maven I can probably update it in dist without cancelling the release? That said would need some help for it. Romain Manni-Bucau @rmannibucau

Re: [VOTE] Release Apache Commons JCS 2.2.1

-1 The file https://dist.apache.org/repos/dist/dev/commons/jcs/source/commons-jcs-dist-2.2.1-src.zip does not contain any of the modules folders. Gary On Sun, Sep 24, 2017 at 5:01 AM, Romain Manni-Bucau wrote: > As announced on the list, I would like to release the

[VOTE] Release Apache Commons JCS 2.2.1

As announced on the list, I would like to release the [jcs] component to resolve a cdi performance issue ( https://issues.apache.org/jira/browse/JCS-183). Maven artifacts are at: https://repository.apache.org/content/repositories/orgapachecommons-1269/ The Subversion tag is: