Re: Maintenance release for JCS 2.2

[Romain Manni-Bucau]

Hi JL,

I'm planning to work on it this week-end or next week (depending how long
it will be to setup my new computer).

Will probably be a 2.2.1 from a branch from the previous discussions we had
so we will need to backport the changes but nothing blocking.


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


2017-09-18 18:29 GMT+02:00 Gary Gregory :

> Hi,
>
> JCS 2.2 is out already: https://commons.apache.org/proper/commons-jcs/
>
> Do you mean the _next_ release?
>
> Gary
>
> On Mon, Sep 18, 2017 at 9:28 AM, Jean-Louis MONTEIRO 
> wrote:
>
> > Hi,
> >
> > I am currently facing performance issues with the CDI integration because
> > of the reflection.
> > I have successfully tested the patch from Romain and would like to know
> if
> > there is a maintenance release planned soon?
> >
> > Thanks
> > Jean-Louis
> >
>

RDF Commons release?

[Aaron Coburn]

Hi!

The last release of commons-rdf was from last November, and there are some nice 
features in the master branch that I would really like to use -- especially the 
improved OSGi support. It seems that there are a few unresolved jira issues, 
such that this wouldn't be a 1.0 release, but even a 0.4.0 release would be 
great.

As a little background, over the last several months I've built a server 
implementation of the W3C Linked Data Platform in which commons-rdf provides 
all of the core RDF abstractions.

Would it be possible to move forward with a release? I would be more than happy 
to help out.

Thanks,
Aaron 

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

Re: Ready for JDK 9 ?

[Stephen Colebourne]

I didn't get the chance to reply when this thread happened, but really
a project should only be viewed as JDK 9 ready when it has had a
release with the Automatic-Module-Name entry in the manifest file.
AFAIK, only common-lang has this (Although commons-csv, email and jcs
were released recently I don't believe they have the entry).

Stephen



On 8 August 2017 at 21:48, Pascal Schumacher  wrote:
> Hello everybody,
>
> commons-lang and commons-text are build and tested with JDK 9 on traivs-ci,
> e.g.:
>
> https://travis-ci.org/apache/commons-text/jobs/259838032
> https://travis-ci.org/apache/commons-lang/jobs/258653445
>
> so I guess these components are ready for JDK 9.
>
> Cheers,
> Pascal
>
> Am 08.08.2017 um 12:09 schrieb Rory O'Donnell:
>>
>>
>> Hi Benedikt,
>>
>> Thank you very much for all your testing of JDK 9 during its development!
>> Such contributions have significantly helped shape and improve JDK 9.
>>
>> Now that we have reached the JDK 9 Final Release Candidate phase [1] , I
>> would like to ask if your project can be considered to be 'ready for JDK 9',
>> or if there are any remaining show stopper issues which you've encountered
>> when testing with the JDK 9 release candidate.
>>
>> JDK 9  b181 is available at http://jdk.java.net/9/
>>
>> If you have a public web page, mailing list post, or even a tweet
>> announcing you project's readiness for JDK 9, I'd love to add the URL to the
>> upcoming JDK 9 readiness page on the Quality Outreach wiki.
>>
>>
>> Looking forward to hearing from you,
>> Rory
>>
>> [1] http://openjdk.java.net/projects/jdk9/
>>
>
>
> -
> 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: Maintenance release for JCS 2.2

[Gary Gregory]

Hi,

JCS 2.2 is out already: https://commons.apache.org/proper/commons-jcs/

Do you mean the _next_ release?

Gary

On Mon, Sep 18, 2017 at 9:28 AM, Jean-Louis MONTEIRO 
wrote:

> Hi,
>
> I am currently facing performance issues with the CDI integration because
> of the reflection.
> I have successfully tested the patch from Romain and would like to know if
> there is a maintenance release planned soon?
>
> Thanks
> Jean-Louis
>

Fwd: Maintenance release for JCS 2.2

[Jean-Louis MONTEIRO]

Hi,

I am currently facing performance issues with the CDI integration because
of the reflection.
I have successfully tested the patch from Romain and would like to know if
there is a maintenance release planned soon?

Thanks
Jean-Louis

Re: [RESULT][VOTE] Release Apache Commons BCEL 6.1 based on RC1

[Gary Gregory]

Yep, the email client on my phone must be funky. Thank you for the link! :-)

Gary

On Mon, Sep 18, 2017 at 7:05 AM, Benedikt Ritter  wrote:

>
> > Am 18.09.2017 um 14:52 schrieb Gary Gregory :
> >
> > Hi Bendikt,
> >
> > Can you please add "[RESULT]" to the email subject?
>
> Hi Gary,
>
> I did, see [1]. Maybe your mail client is showing this wrong?
>
> Regards,
> Benedikt
>
> [1] http://markmail.org/message/75hwfovacb2f4t4w
>
> >
> > Gary
> >
> > On Sep 18, 2017 01:02, "Benedikt Ritter"  wrote:
> >
> >
> >> Am 14.09.2017 um 22:29 schrieb Benedikt Ritter :
> >>
> >> Hi,
> >>
> >> we’ve fixed some bugs and added some new feature since Commons BCEL 6.0
> > was released, so I’d like to call a vote to release Commons BCEL 6.1
> based
> > on RC1.
> >>
> >> BCEL 6.1 RC1 is available for review her:
> >> https://dist.apache.org/repos/dist/dev/commons/bcel (rev 21612)
> >>
> >> The tag is here:
> >> https://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_1_RC1
> > (rev 1808392)
> >>
> >> Maven artifacts are here:
> >>   https://repository.apache.org/content/repositories/
> > orgapachecommons-1263/org/apache/bcel/bcel/6.1/
> >>
> >> These are the Maven artifacts and their hashes
> >>
> >> bcel-6.1.jar.asc
> >> (SHA1: a190964c22cb11132f3e14b71adc50b72db8d629)
> >> bcel-6.1-sources.jar.asc
> >> (SHA1: 5c740afacb9267135e39b3746243b22623e81d03)
> >> bcel-6.1-test-sources.jar.asc
> >> (SHA1: e5dcb0adad0f9c812b6da180800948e6e07652b2)
> >> bcel-6.1-tests.jar.asc
> >> (SHA1: 760cb782785426f647771fab73ab58a1cb34a433)
> >> bcel-6.1-javadoc.jar
> >> (SHA1: 64db6246e0b1fc9b4e1ba3c31c7e8251e0fe5acd)
> >> bcel-6.1.pom.asc
> >> (SHA1: ee13e95b11ab53ac1352404423ef365993869c83)
> >> bcel-6.1.pom
> >> (SHA1: b4cff8fd449d6a4ed2252182de949511034ac7b3)
> >> bcel-6.1-sources.jar
> >> (SHA1: fcd80e33305bbc1fdbd9456fb4f5afb454171f09)
> >> bcel-6.1.jar
> >> (SHA1: 6f0534a03433c804c6ad774c9c98fb7637e6fb57)
> >> bcel-6.1-javadoc.jar.asc
> >> (SHA1: 07bbf6ca6519a06a57a5841c768b01ac5a8302a0)
> >> bcel-6.1-test-sources.jar
> >> (SHA1: a73cc36bd1ed46a858316894ec0792de07b5e34a)
> >> bcel-6.1-tests.jar
> >> (SHA1: 71d1a2afe871aa3ece39c4b858445f764c08092d)
> >>
> >> I have tested this with JDK 7 using Maven 3.5.0. I’ve also tested with
> > Java 9 EA b181. The build fails. See BCEL-275.
> >>
> >> Details of changes since 6.1 are in the release notes:
> >>   https://dist.apache.org/repos/dist/dev/commons/bcel/RELEASE-NOTES.txt
> >>   http://home.apache.org/~britter/commons/bcel/6.1-RC1/
> > changes-report.html
> >>
> >> Site:
> >>   http://home.apache.org/~britter/commons/bcel/6.1-RC1
> >> (note some *relative* links are broken and the 6.1 directories are
> >> not yet created - these will be OK once the site is deployed)
> >>
> >> Clirr Report (compared to 6.1):
> >>   http://home.apache.org/~britter/commons/bcel/6.1-RC1/
> clirr-report.html
> >>
> >> Note that Clirr reports several errors.
> >> These are considered OK for the reasons stated below.
> >> These exceptions are also noted in the Changes and Release Notes.
> >>
> >> Errors reported:
> >> - methods added to interface: OK because that does not affect binary
> > compatibility. The Visitor interface is not meant to be implemented
> > directly by clients. This change has also be discussed on the dev ML:
> > http://markmail.org/message/n445xf3f5ghkrkwe
> >>
> >> RAT Report:
> >>   http://home.apache.org/~britter/commons/bcel/6.1-RC1/rat-report.html
> >>
> >> KEYS:
> >> https://www.apache.org/dist/commons/KEYS
> >>
> >> Please review the release candidate and vote.
> >> This vote will close no sooner that 72 hours from now,
> >> i.e. sometime after 22:30 CEST (UTC+2) 17-September 2017
> >>
> >> [ ] +1 Release these artifacts
> >> [ ] +0 OK, but...
> >> [ ] -0 OK, but really should fix...
> >> [ ] -1 I oppose this release because...
> >>
> >> Thanks!
> >
> > Hi,
> >
> > this vote passes with the following result:
> >
> > Bruno P. Kinoshita: +1 (binding)
> > Oliver Heger: +1 (binding)
> > Gary Gregory: +1 (binding)
> > Mark Roberts: +1 (non-binding)
> > Benedikt Ritter: +1 (binding)
> >
> > Thank you!
> > Benedikt
> >
> >>
> >> Benedikt
> >>
> >>
> >>
> >> -
> >> 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: [RESULT][VOTE] Release Apache Commons BCEL 6.1 based on RC1

[Benedikt Ritter]

> Am 18.09.2017 um 14:52 schrieb Gary Gregory :
> 
> Hi Bendikt,
> 
> Can you please add "[RESULT]" to the email subject?

Hi Gary,

I did, see [1]. Maybe your mail client is showing this wrong?

Regards,
Benedikt

[1] http://markmail.org/message/75hwfovacb2f4t4w

> 
> Gary
> 
> On Sep 18, 2017 01:02, "Benedikt Ritter"  wrote:
> 
> 
>> Am 14.09.2017 um 22:29 schrieb Benedikt Ritter :
>> 
>> Hi,
>> 
>> we’ve fixed some bugs and added some new feature since Commons BCEL 6.0
> was released, so I’d like to call a vote to release Commons BCEL 6.1 based
> on RC1.
>> 
>> BCEL 6.1 RC1 is available for review her:
>> https://dist.apache.org/repos/dist/dev/commons/bcel (rev 21612)
>> 
>> The tag is here:
>> https://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_1_RC1
> (rev 1808392)
>> 
>> Maven artifacts are here:
>>   https://repository.apache.org/content/repositories/
> orgapachecommons-1263/org/apache/bcel/bcel/6.1/
>> 
>> These are the Maven artifacts and their hashes
>> 
>> bcel-6.1.jar.asc
>> (SHA1: a190964c22cb11132f3e14b71adc50b72db8d629)
>> bcel-6.1-sources.jar.asc
>> (SHA1: 5c740afacb9267135e39b3746243b22623e81d03)
>> bcel-6.1-test-sources.jar.asc
>> (SHA1: e5dcb0adad0f9c812b6da180800948e6e07652b2)
>> bcel-6.1-tests.jar.asc
>> (SHA1: 760cb782785426f647771fab73ab58a1cb34a433)
>> bcel-6.1-javadoc.jar
>> (SHA1: 64db6246e0b1fc9b4e1ba3c31c7e8251e0fe5acd)
>> bcel-6.1.pom.asc
>> (SHA1: ee13e95b11ab53ac1352404423ef365993869c83)
>> bcel-6.1.pom
>> (SHA1: b4cff8fd449d6a4ed2252182de949511034ac7b3)
>> bcel-6.1-sources.jar
>> (SHA1: fcd80e33305bbc1fdbd9456fb4f5afb454171f09)
>> bcel-6.1.jar
>> (SHA1: 6f0534a03433c804c6ad774c9c98fb7637e6fb57)
>> bcel-6.1-javadoc.jar.asc
>> (SHA1: 07bbf6ca6519a06a57a5841c768b01ac5a8302a0)
>> bcel-6.1-test-sources.jar
>> (SHA1: a73cc36bd1ed46a858316894ec0792de07b5e34a)
>> bcel-6.1-tests.jar
>> (SHA1: 71d1a2afe871aa3ece39c4b858445f764c08092d)
>> 
>> I have tested this with JDK 7 using Maven 3.5.0. I’ve also tested with
> Java 9 EA b181. The build fails. See BCEL-275.
>> 
>> Details of changes since 6.1 are in the release notes:
>>   https://dist.apache.org/repos/dist/dev/commons/bcel/RELEASE-NOTES.txt
>>   http://home.apache.org/~britter/commons/bcel/6.1-RC1/
> changes-report.html
>> 
>> Site:
>>   http://home.apache.org/~britter/commons/bcel/6.1-RC1
>> (note some *relative* links are broken and the 6.1 directories are
>> not yet created - these will be OK once the site is deployed)
>> 
>> Clirr Report (compared to 6.1):
>>   http://home.apache.org/~britter/commons/bcel/6.1-RC1/clirr-report.html
>> 
>> Note that Clirr reports several errors.
>> These are considered OK for the reasons stated below.
>> These exceptions are also noted in the Changes and Release Notes.
>> 
>> Errors reported:
>> - methods added to interface: OK because that does not affect binary
> compatibility. The Visitor interface is not meant to be implemented
> directly by clients. This change has also be discussed on the dev ML:
> http://markmail.org/message/n445xf3f5ghkrkwe
>> 
>> RAT Report:
>>   http://home.apache.org/~britter/commons/bcel/6.1-RC1/rat-report.html
>> 
>> KEYS:
>> https://www.apache.org/dist/commons/KEYS
>> 
>> Please review the release candidate and vote.
>> This vote will close no sooner that 72 hours from now,
>> i.e. sometime after 22:30 CEST (UTC+2) 17-September 2017
>> 
>> [ ] +1 Release these artifacts
>> [ ] +0 OK, but...
>> [ ] -0 OK, but really should fix...
>> [ ] -1 I oppose this release because...
>> 
>> Thanks!
> 
> Hi,
> 
> this vote passes with the following result:
> 
> Bruno P. Kinoshita: +1 (binding)
> Oliver Heger: +1 (binding)
> Gary Gregory: +1 (binding)
> Mark Roberts: +1 (non-binding)
> Benedikt Ritter: +1 (binding)
> 
> Thank you!
> Benedikt
> 
>> 
>> Benedikt
>> 
>> 
>> 
>> -
>> 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: [RESULT][VOTE] Release Apache Commons BCEL 6.1 based on RC1

[Gary Gregory]

Hi Bendikt,

Can you please add "[RESULT]" to the email subject?

Gary

On Sep 18, 2017 01:02, "Benedikt Ritter"  wrote:


> Am 14.09.2017 um 22:29 schrieb Benedikt Ritter :
>
> Hi,
>
> we’ve fixed some bugs and added some new feature since Commons BCEL 6.0
was released, so I’d like to call a vote to release Commons BCEL 6.1 based
on RC1.
>
> BCEL 6.1 RC1 is available for review her:
>  https://dist.apache.org/repos/dist/dev/commons/bcel (rev 21612)
>
> The tag is here:
>  https://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_1_RC1
(rev 1808392)
>
> Maven artifacts are here:
>https://repository.apache.org/content/repositories/
orgapachecommons-1263/org/apache/bcel/bcel/6.1/
>
> These are the Maven artifacts and their hashes
>
> bcel-6.1.jar.asc
> (SHA1: a190964c22cb11132f3e14b71adc50b72db8d629)
> bcel-6.1-sources.jar.asc
> (SHA1: 5c740afacb9267135e39b3746243b22623e81d03)
> bcel-6.1-test-sources.jar.asc
> (SHA1: e5dcb0adad0f9c812b6da180800948e6e07652b2)
> bcel-6.1-tests.jar.asc
> (SHA1: 760cb782785426f647771fab73ab58a1cb34a433)
> bcel-6.1-javadoc.jar
> (SHA1: 64db6246e0b1fc9b4e1ba3c31c7e8251e0fe5acd)
> bcel-6.1.pom.asc
> (SHA1: ee13e95b11ab53ac1352404423ef365993869c83)
> bcel-6.1.pom
> (SHA1: b4cff8fd449d6a4ed2252182de949511034ac7b3)
> bcel-6.1-sources.jar
> (SHA1: fcd80e33305bbc1fdbd9456fb4f5afb454171f09)
> bcel-6.1.jar
> (SHA1: 6f0534a03433c804c6ad774c9c98fb7637e6fb57)
> bcel-6.1-javadoc.jar.asc
> (SHA1: 07bbf6ca6519a06a57a5841c768b01ac5a8302a0)
> bcel-6.1-test-sources.jar
> (SHA1: a73cc36bd1ed46a858316894ec0792de07b5e34a)
> bcel-6.1-tests.jar
> (SHA1: 71d1a2afe871aa3ece39c4b858445f764c08092d)
>
> I have tested this with JDK 7 using Maven 3.5.0. I’ve also tested with
Java 9 EA b181. The build fails. See BCEL-275.
>
> Details of changes since 6.1 are in the release notes:
>https://dist.apache.org/repos/dist/dev/commons/bcel/RELEASE-NOTES.txt
>http://home.apache.org/~britter/commons/bcel/6.1-RC1/
changes-report.html
>
> Site:
>http://home.apache.org/~britter/commons/bcel/6.1-RC1
>  (note some *relative* links are broken and the 6.1 directories are
>  not yet created - these will be OK once the site is deployed)
>
> Clirr Report (compared to 6.1):
>http://home.apache.org/~britter/commons/bcel/6.1-RC1/clirr-report.html
>
> Note that Clirr reports several errors.
> These are considered OK for the reasons stated below.
> These exceptions are also noted in the Changes and Release Notes.
>
> Errors reported:
> - methods added to interface: OK because that does not affect binary
compatibility. The Visitor interface is not meant to be implemented
directly by clients. This change has also be discussed on the dev ML:
http://markmail.org/message/n445xf3f5ghkrkwe
>
> RAT Report:
>http://home.apache.org/~britter/commons/bcel/6.1-RC1/rat-report.html
>
> KEYS:
>  https://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 22:30 CEST (UTC+2) 17-September 2017
>
>  [ ] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
>
> Thanks!

Hi,

this vote passes with the following result:

Bruno P. Kinoshita: +1 (binding)
Oliver Heger: +1 (binding)
Gary Gregory: +1 (binding)
Mark Roberts: +1 (non-binding)
Benedikt Ritter: +1 (binding)

Thank you!
Benedikt

>
> Benedikt
>
>
>
> -
> 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: [ALL] Javadoc.io - a new GitHub badge for our projects?

[Amey Jadiye]

+1, LGTM.

Regards,
Amey

On Mon, Sep 18, 2017, 3:24 PM Benedikt Ritter  wrote:

> Hi,
>
> I just became aware of https://javadoc.io/  a
> website which provides hosting for all javadocs on Maven Central. They also
> provide badges for GitHub. Do we want to add this to our README.md files?
>
> Cheers,
> Benedikt
>
>

[ALL] Javadoc.io - a new GitHub badge for our projects?

[Benedikt Ritter]

Hi,

I just became aware of https://javadoc.io/  a website 
which provides hosting for all javadocs on Maven Central. They also provide 
badges for GitHub. Do we want to add this to our README.md files?

Cheers,
Benedikt

[RESULT][VOTE] Release Apache Commons BCEL 6.1 based on RC1

[Benedikt Ritter]

> Am 14.09.2017 um 22:29 schrieb Benedikt Ritter :
> 
> Hi,
> 
> we’ve fixed some bugs and added some new feature since Commons BCEL 6.0 was 
> released, so I’d like to call a vote to release Commons BCEL 6.1 based on RC1.
> 
> BCEL 6.1 RC1 is available for review her:
>  https://dist.apache.org/repos/dist/dev/commons/bcel (rev 21612)
> 
> The tag is here:
>  https://svn.apache.org/repos/asf/commons/proper/bcel/tags/BCEL_6_1_RC1 (rev 
> 1808392)
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1263/org/apache/bcel/bcel/6.1/
> 
> These are the Maven artifacts and their hashes
> 
> bcel-6.1.jar.asc
> (SHA1: a190964c22cb11132f3e14b71adc50b72db8d629)
> bcel-6.1-sources.jar.asc
> (SHA1: 5c740afacb9267135e39b3746243b22623e81d03)
> bcel-6.1-test-sources.jar.asc
> (SHA1: e5dcb0adad0f9c812b6da180800948e6e07652b2)
> bcel-6.1-tests.jar.asc
> (SHA1: 760cb782785426f647771fab73ab58a1cb34a433)
> bcel-6.1-javadoc.jar
> (SHA1: 64db6246e0b1fc9b4e1ba3c31c7e8251e0fe5acd)
> bcel-6.1.pom.asc
> (SHA1: ee13e95b11ab53ac1352404423ef365993869c83)
> bcel-6.1.pom
> (SHA1: b4cff8fd449d6a4ed2252182de949511034ac7b3)
> bcel-6.1-sources.jar
> (SHA1: fcd80e33305bbc1fdbd9456fb4f5afb454171f09)
> bcel-6.1.jar
> (SHA1: 6f0534a03433c804c6ad774c9c98fb7637e6fb57)
> bcel-6.1-javadoc.jar.asc
> (SHA1: 07bbf6ca6519a06a57a5841c768b01ac5a8302a0)
> bcel-6.1-test-sources.jar
> (SHA1: a73cc36bd1ed46a858316894ec0792de07b5e34a)
> bcel-6.1-tests.jar
> (SHA1: 71d1a2afe871aa3ece39c4b858445f764c08092d)
> 
> I have tested this with JDK 7 using Maven 3.5.0. I’ve also tested with Java 9 
> EA b181. The build fails. See BCEL-275.
> 
> Details of changes since 6.1 are in the release notes:
>https://dist.apache.org/repos/dist/dev/commons/bcel/RELEASE-NOTES.txt
>http://home.apache.org/~britter/commons/bcel/6.1-RC1/changes-report.html
> 
> Site:
>http://home.apache.org/~britter/commons/bcel/6.1-RC1
>  (note some *relative* links are broken and the 6.1 directories are
>  not yet created - these will be OK once the site is deployed)
> 
> Clirr Report (compared to 6.1):
>http://home.apache.org/~britter/commons/bcel/6.1-RC1/clirr-report.html
> 
> Note that Clirr reports several errors.
> These are considered OK for the reasons stated below.
> These exceptions are also noted in the Changes and Release Notes.
> 
> Errors reported:
> - methods added to interface: OK because that does not affect binary 
> compatibility. The Visitor interface is not meant to be implemented directly 
> by clients. This change has also be discussed on the dev ML: 
> http://markmail.org/message/n445xf3f5ghkrkwe
> 
> RAT Report:
>http://home.apache.org/~britter/commons/bcel/6.1-RC1/rat-report.html
> 
> KEYS:
>  https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 22:30 CEST (UTC+2) 17-September 2017
> 
>  [ ] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
> 
> Thanks!

Hi,

this vote passes with the following result:

Bruno P. Kinoshita: +1 (binding)
Oliver Heger: +1 (binding)
Gary Gregory: +1 (binding)
Mark Roberts: +1 (non-binding)
Benedikt Ritter: +1 (binding)

Thank you!
Benedikt

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