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

[Thomas Vandahl]

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

> Lots of discrepancies means lots of checking.

Yes, I understand that. The clean way to handle this would probably be
to create a release branch, tidy that up and release from there.

Bye, Thomas

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

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

[Thomas Vandahl]

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. The following votes were cast (in order of appearance):

Thomas Vandahl: +1
Romain Manni-Bucau: +1 (non binding)
Benedikt Ritter: +1
Bruno P. Kinoshita: +1

The vote has passed. Thanks to all the voters!

I'll proceed with the release procedure.

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 based on RC4

[sebb]

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 commons-jcs-2.2.1-RC4/: .travis.yml
>> Only in commons-jcs-2.2.1-src: LICENSE
>> Only in commons-jcs-2.2.1-RC4/: LICENSE.txt
>> Only in commons-jcs-2.2.1-src: NOTICE
>> Only in commons-jcs-2.2.1-RC4/: NOTICE.txt
>> Only in commons-jcs-2.2.1-RC4/: auxiliary-builds
>> Only in commons-jcs-2.2.1-RC4/: checkstyle.xml
>> Only in commons-jcs-2.2.1-RC4/: commons-jcs-sandbox
>> Only in commons-jcs-2.2.1-RC4/: init-git-svn.sh
>> Only in commons-jcs-2.2.1-RC4/: jcache-fast.sh
>> Only in commons-jcs-2.2.1-RC4/: maven-eclipse-codestyle.xml
>>
>> This should be fixed for the next release.
>
> Is it absolutely necessary that the tag contains the exact same files as
> the distribution or would it be sufficient that the tag is able to
> *build* the identical distribution? That has always been my interpretation.

Reviewers need to be able to account for any discrepancies between the
contents to ensure that:
- the dist does not contain spurious files
- the dist is not lacking any required files.

The source distribution also has to be able to build itself.

If the tag contains files that are not in the distribution, why are
they present at all?
If they are needed, why are they not in the distribution?

Lots of discrepancies means lots of checking.

> 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 based on RC4

[Thomas Vandahl]

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 commons-jcs-2.2.1-src: LICENSE
> Only in commons-jcs-2.2.1-RC4/: LICENSE.txt
> Only in commons-jcs-2.2.1-src: NOTICE
> Only in commons-jcs-2.2.1-RC4/: NOTICE.txt
> Only in commons-jcs-2.2.1-RC4/: auxiliary-builds
> Only in commons-jcs-2.2.1-RC4/: checkstyle.xml
> Only in commons-jcs-2.2.1-RC4/: commons-jcs-sandbox
> Only in commons-jcs-2.2.1-RC4/: init-git-svn.sh
> Only in commons-jcs-2.2.1-RC4/: jcache-fast.sh
> Only in commons-jcs-2.2.1-RC4/: maven-eclipse-codestyle.xml
> 
> This should be fixed for the next release.

Is it absolutely necessary that the tag contains the exact same files as
the distribution or would it be sufficient that the tag is able to
*build* the identical distribution? That has always been my interpretation.

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 based on RC4

[Bruno P. Kinoshita]

+1


Build passing successfully on 

Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_172, vendor: Oracle Corporation
Java home: /opt/jdk1.8.0_172/jre
Default locale: en_NZ, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-33-generic", arch: "amd64", family: "unix"


Minor issues in some reports, but I think they are not blockers.


Parent module's RAT report contains 

1 Unknown Licenses

*

Files with unapproved licenses:

src/scripts/zipcodes.txt

Probably we just need to add an exclusion in RAT plugin configuration.

The JCS Cache module's report has a few FindBugs issues introduced in this 
release, but looks like it's just related to exposing arrays in some methods. A 
few ununsed imports as well in PMD.

The JCS Extras module's RAT report contains

1 Unknown Licenses

*

Files with unapproved licenses:

/home/kinow/Development/java/apache/commons-jcs-2.2.1-RC4/commons-jcs-jcache-extras/src/main/resources/META-INF/services/javax.enterprise.inject.spi.Extension


The current website has a similar warning (just different folder structure). 
But I believe it's just a minor issue caused by some command during the release.

Ditto the above about RAT for the JCS OpenJPA module

1 Unknown Licenses

*

Files with unapproved licenses:

/home/kinow/Development/java/apache/commons-jcs-2.2.1-RC4/commons-jcs-jcache-openjpa/derby.log

The jcs-dist module appears in the website menu, and right now gives a 404. It 
doesn't appear to generate a target/site folder, so maybe 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: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 for one more review?


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 based on RC4

[Thomas Vandahl]

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 for one more review?

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 based on RC4

[sebb]

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

I don't think that can be fixed.

> Only in commons-jcs-2.2.1-RC4/: .travis.yml
> Only in commons-jcs-2.2.1-src: LICENSE
> Only in commons-jcs-2.2.1-RC4/: LICENSE.txt
> Only in commons-jcs-2.2.1-src: NOTICE
> Only in commons-jcs-2.2.1-RC4/: NOTICE.txt
> Only in commons-jcs-2.2.1-RC4/: auxiliary-builds
> Only in commons-jcs-2.2.1-RC4/: checkstyle.xml
> Only in commons-jcs-2.2.1-RC4/: commons-jcs-sandbox
> Only in commons-jcs-2.2.1-RC4/: init-git-svn.sh
> Only in commons-jcs-2.2.1-RC4/: jcache-fast.sh
> Only in commons-jcs-2.2.1-RC4/: maven-eclipse-codestyle.xml
>
> This should be fixed for the next release.

I agree the rest should be fixed.

> +1
>
> Regards,
> Benedikt
>
> Am Do., 23. Aug. 2018 um 17:32 Uhr schrieb Thomas Vandahl :
>
>> 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:
>>
>>
>> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC4
>> (r1838700
>> 
>> )
>>
>> Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1373
>>
>> I have built and tested this using:
>>
>> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
>> 2018-06-17T20:33:14+02:00)
>> Maven home: /Users/thomas/Dev/apache-maven-3.5.4
>> Java version: 1.8.0_144, vendor: Oracle Corporation, runtime:
>> /Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/jre
>> Default locale: de_DE, platform encoding: UTF-8
>> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
>>
>> Details of changes since 2.2 are in the release notes:
>>
>> https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE-NOTES.txt
>>
>>
>> https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/changes-report.html
>>
>> Site:
>> https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/
>>
>> CLIRR Report (compared to 2.2):
>>
>>
>> https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/commons-jcs-core/clirr-report.html
>>
>> RAT Report:
>>
>>
>> https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/commons-jcs-core/rat-report.html
>>
>> KEYS:
>> https://www.apache.org/dist/commons/KEYS
>>
>> Please review the release candidate and vote.
>>
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>>
>> 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 based on RC4

[Benedikt Ritter]

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/
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 commons-jcs-2.2.1-src: LICENSE
Only in commons-jcs-2.2.1-RC4/: LICENSE.txt
Only in commons-jcs-2.2.1-src: NOTICE
Only in commons-jcs-2.2.1-RC4/: NOTICE.txt
Only in commons-jcs-2.2.1-RC4/: auxiliary-builds
Only in commons-jcs-2.2.1-RC4/: checkstyle.xml
Only in commons-jcs-2.2.1-RC4/: commons-jcs-sandbox
Only in commons-jcs-2.2.1-RC4/: init-git-svn.sh
Only in commons-jcs-2.2.1-RC4/: jcache-fast.sh
Only in commons-jcs-2.2.1-RC4/: maven-eclipse-codestyle.xml

This should be fixed for the next release.

+1

Regards,
Benedikt

Am Do., 23. Aug. 2018 um 17:32 Uhr schrieb Thomas Vandahl :

> 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:
>
>
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC4
> (r1838700
> 
> )
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1373
>
> I have built and tested this using:
>
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-17T20:33:14+02:00)
> Maven home: /Users/thomas/Dev/apache-maven-3.5.4
> Java version: 1.8.0_144, vendor: Oracle Corporation, runtime:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"
>
> Details of changes since 2.2 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE-NOTES.txt
>
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/changes-report.html
>
> Site:
> https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/
>
> CLIRR Report (compared to 2.2):
>
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/commons-jcs-core/clirr-report.html
>
> RAT Report:
>
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/commons-jcs-core/rat-report.html
>
> KEYS:
> https://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> 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 based on RC4

[Romain Manni-Bucau]

+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 Release these artifacts
>
> 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 based on RC4

[Thomas Vandahl]

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


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[VOTE] Release Apache Commons JCS 2.2.1 based on RC4

[Thomas Vandahl]

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:

https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC4
(r1838700)

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1373

I have built and tested this using:

Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T20:33:14+02:00)
Maven home: /Users/thomas/Dev/apache-maven-3.5.4
Java version: 1.8.0_144, vendor: Oracle Corporation, runtime:
/Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.11.6", arch: "x86_64", family: "mac"

Details of changes since 2.2 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/changes-report.html

Site:
https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/

CLIRR Report (compared to 2.2):

https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/commons-jcs-core/clirr-report.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/jcs/site-2.2.1-RC4/commons-jcs-core/rat-report.html

KEYS:
https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

Bye, Thomas.

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

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

[Romain Manni-Bucau]

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

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

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

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)

[Romain Manni-Bucau]

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)

[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

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

[Romain Manni-Bucau]

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)

[Thomas Vandahl]

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)

[Romain Manni-Bucau]

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)

[Gary Gregory]

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)

[Romain Manni-Bucau]

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)

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

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

[Gary Gregory]

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)

[Romain Manni-Bucau]

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)

[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

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

[Romain Manni-Bucau]

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)

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

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

[Romain Manni-Bucau]

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)

[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

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

[Gary Gregory]

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)

[Romain Manni-Bucau]

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)

[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.)
- 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)

[Romain Manni-Bucau]

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)

[Gary Gregory]

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)

[Gary Gregory]

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)

[Benedikt Ritter]

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

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

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)

[Romain Manni-Bucau]

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)

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

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

[Romain Manni-Bucau]

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)

[Gary Gregory]

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)

[Matt Sicker]

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)

[kenneth mcfarland]

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)

[Gary Gregory]

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)

[Romain Manni-Bucau]

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)

[Gary Gregory]

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)

[Romain Manni-Bucau]

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)

[Gary Gregory]

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

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

[Romain Manni-Bucau]

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: [CANCEL][VOTE] Release Apache Commons JCS 2.2.1

[Romain Manni-Bucau]

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 :(. Thanks guys for your help and feedbacks.
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github
>  | LinkedIn
> 
>
> 2017-09-29 16:09 GMT+02:00 Thomas Vandahl :
>
>> 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 roll back the tag.
>>
>> Bye, Thomas.
>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>

[CANCEL][VOTE] Release Apache Commons JCS 2.2.1

[Romain Manni-Bucau]

Cancelling then :(. Thanks guys for your help and feedbacks.


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn 

2017-09-29 16:09 GMT+02:00 Thomas Vandahl :

> 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 roll back the tag.
>
> 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

[Thomas Vandahl]

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 roll back the tag.

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

[Romain Manni-Bucau]

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
> 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 <
> rmannibu...@gmail.com>
> wrote:
>
> > 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  > rmannibucau> |
> > LinkedIn  | JavaEE Factory
> > 
> >
> > 2017-09-28 10:14 GMT+02:00 Romain Manni-Bucau :
> >
> > > 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
> > >  | Github
> > >  | LinkedIn
> > >  | JavaEE Factory
> > > 
> > >
> > > 2017-09-27 23:06 GMT+02:00 Gary Gregory :
> > >
> > >> 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 <
> > >> rmannibu...@gmail.com>
> > >> wrote:
> > >>
> > >> > 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
> > >> > > 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 -Duser.name=rmannibucau -Prelease release:perform
> > >> >   mvn -Duser.name=rmannibucau -Prelease clean site site:stage
> > >> > ?
> > >> >
> > >> > 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

[Gary Gregory]

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 if it is better this
> way please?
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github  rmannibucau> |
> LinkedIn  | JavaEE Factory
> 
>
> 2017-09-28 10:14 GMT+02:00 Romain Manni-Bucau :
>
> > 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
> >  | Github
> >  | LinkedIn
> >  | JavaEE Factory
> > 
> >
> > 2017-09-27 23:06 GMT+02:00 Gary Gregory :
> >
> >> 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 <
> >> rmannibu...@gmail.com>
> >> wrote:
> >>
> >> > 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
> >> > > 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 -Duser.name=rmannibucau -Prelease release:perform
> >> >   mvn -Duser.name=rmannibucau -Prelease clean site site:stage
> >> > ?
> >> >
> >> > 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

[Romain Manni-Bucau]

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  |
LinkedIn  | JavaEE Factory


2017-09-28 10:14 GMT+02:00 Romain Manni-Bucau :

> 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
>  | Github
>  | LinkedIn
>  | JavaEE Factory
> 
>
> 2017-09-27 23:06 GMT+02:00 Gary Gregory :
>
>> 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 <
>> rmannibu...@gmail.com>
>> wrote:
>>
>> > 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
>> > > 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 -Duser.name=rmannibucau -Prelease release:perform
>> >   mvn -Duser.name=rmannibucau -Prelease clean site site:stage
>> > ?
>> >
>> > 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

[Romain Manni-Bucau]

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
 | Github  |
LinkedIn  | JavaEE Factory


2017-09-27 23:06 GMT+02:00 Gary Gregory :

> 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
> > 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
> > > 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 -Duser.name=rmannibucau -Prelease release:perform
> >   mvn -Duser.name=rmannibucau -Prelease clean site site:stage
> > ?
> >
> > 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

[Gary Gregory]

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
> 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
> > 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 -Duser.name=rmannibucau -Prelease release:perform
>   mvn -Duser.name=rmannibucau -Prelease clean site site:stage
> ?
>
> 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

[Thomas Vandahl]

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

[Romain Manni-Bucau]

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
> 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 -Duser.name=rmannibucau -Prelease release:perform
  mvn -Duser.name=rmannibucau -Prelease clean site site:stage
?

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

[Thomas Vandahl]

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 -Duser.name=rmannibucau -Prelease release:perform
  mvn -Duser.name=rmannibucau -Prelease clean site site:stage
?

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

[Romain Manni-Bucau]

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  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | JavaEE Factory


2017-09-25 17:47 GMT+02:00 Gary Gregory :

> -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 [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:
> > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> commons-jcs-2.2.1/
> >
> >  The release notes are available at:
> > http://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> > commons-jcs-2.2.1/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  > rmannibucau> |
> > LinkedIn  | JavaEE Factory
> > 
> >
>

Re: [VOTE] Release Apache Commons JCS 2.2.1

[Gary Gregory]

-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 [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:
> http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1/
>
>  The release notes are available at:
> http://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> commons-jcs-2.2.1/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  rmannibucau> |
> LinkedIn  | JavaEE Factory
> 
>

[VOTE] Release Apache Commons JCS 2.2.1

[Romain Manni-Bucau]

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:
http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1/

 The release notes are available at:
http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1/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  | JavaEE Factory