You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2020/05/15 14:50:21 UTC

[VOTE] Apache Jena 3.15.0 RC 1

Hi,

Here is a vote on the release of Apache Jena 3.15.0
This is the first proposed release candidate.

The deadline is Tuesday, 19th May 2020 at 06:00 UTC

==== Dependency changes:

JENA-1829: Apache Parent POM to v23.
JENA-1812: Update Commons Codec 1.13 -> 1.14
JENA-1883: Commons Lang3 : 3.9 -> 3.10
JENA-1839: Update Commons CSV 1.7 -> 1.8

JENA-1005
Update slf4j 1.7.26 -> 1.7.30
   new : org.apache.logging.log4j2 version 2.13.1
   Remove log4j1

JENA-1850: Commons compress 1.19 -> 1.20

JENA-1836: Shiro: 1.2.6 -> 1.5.1   (CVE-2019-12422)
JENA-1850: Jetty: 9.4.12.v20180830 -> 9.4.26.v20200117
JENA-1851: Lucene: 7.4.0 -> 7.7.2 (Not -> 8.4.1)
            ElasticSearch 6.4.2 -> ES 6.8.6 for Lucene 7.7.x
            (Not -> ES 7.6.0 for Lucene 8.4.x)

==== Changes for 3.15.0:

https://s.apache.org/jena-3.15.0-jira

==== Release Vote

Everyone, not just committers, is invited to test and vote.
Please download and test the proposed release.

Staging repository:
   https://repository.apache.org/content/repositories/orgapachejena-1037

Proposed dist/ area:
   https://dist.apache.org/repos/dist/dev/jena/

Keys:
   https://svn.apache.org/repos/asf/jena/dist/KEYS

Git commit (browser URL):
   https://github.com/apache/jena/commit/a59b6b103c

Git Commit Hash:@@
   a59b6b103c8b109fbbdc15f9269fab6eebfc132c

Git Commit Tag:
   jena-3.15.0

Please vote to approve this release:

         [ ] +1 Approve the release
         [ ]  0 Don't care
         [ ] -1 Don't release, because ...

This vote will be open until at least

     Tuesday, 19th May 2020 at 06:00 UTC

If you expect to check the release but the time limit does not work
for you, please email within the schedule above with an expected time
and we can extend the vote period.

Thanks,

       Andy

Checking needed:

+ are the GPG signatures fine?
+ are the checksums correct?
+ is there a source archive?

+ can the source archive really be built?
           (NB This requires a "mvn install" first time)
+ is there a correct LICENSE and NOTICE file in each artifact
           (both source and binary artifacts)?
+ does the NOTICE file contain all necessary attributions?
+ have any licenses of dependencies changed due to upgrades?
            if so have LICENSE and NOTICE been upgraded appropriately?
+ does the tag/commit in the SCM contain reproducible sources?

[RESULT] [VOTE] Apache Jena 3.15.0 RC 1

Posted by Andy Seaborne <an...@apache.org>.
(Resend with the correct subject line.)

The vote passes with +1's from

Aaron, Bruno, Chris and Andy

and a welcome community +1 from Marco.

Onto phase 2 - sync, announce and the new shiny website production.

      Andy

> 
> 
> On 15/05/2020 15:50, Andy Seaborne wrote:
>> Hi,
>>
>> Here is a vote on the release of Apache Jena 3.15.0
>> This is the first proposed release candidate.
>>
>> The deadline is Tuesday, 19th May 2020 at 06:00 UTC
>>
>> ==== Dependency changes:
>>
>> JENA-1829: Apache Parent POM to v23.
>> JENA-1812: Update Commons Codec 1.13 -> 1.14
>> JENA-1883: Commons Lang3 : 3.9 -> 3.10
>> JENA-1839: Update Commons CSV 1.7 -> 1.8
>>
>> JENA-1005
>> Update slf4j 1.7.26 -> 1.7.30
>>    new : org.apache.logging.log4j2 version 2.13.1
>>    Remove log4j1
>>
>> JENA-1850: Commons compress 1.19 -> 1.20
>>
>> JENA-1836: Shiro: 1.2.6 -> 1.5.1   (CVE-2019-12422)
>> JENA-1850: Jetty: 9.4.12.v20180830 -> 9.4.26.v20200117
>> JENA-1851: Lucene: 7.4.0 -> 7.7.2 (Not -> 8.4.1)
>>             ElasticSearch 6.4.2 -> ES 6.8.6 for Lucene 7.7.x
>>             (Not -> ES 7.6.0 for Lucene 8.4.x)
>>
>> ==== Changes for 3.15.0:
>>
>> https://s.apache.org/jena-3.15.0-jira
>>
>> ==== Release Vote
>>
>> Everyone, not just committers, is invited to test and vote.
>> Please download and test the proposed release.
>>
>> Staging repository:
>>    https://repository.apache.org/content/repositories/orgapachejena-1037
>>
>> Proposed dist/ area:
>>    https://dist.apache.org/repos/dist/dev/jena/
>>
>> Keys:
>>    https://svn.apache.org/repos/asf/jena/dist/KEYS
>>
>> Git commit (browser URL):
>>    https://github.com/apache/jena/commit/a59b6b103c
>>
>> Git Commit Hash:@@
>>    a59b6b103c8b109fbbdc15f9269fab6eebfc132c
>>
>> Git Commit Tag:
>>    jena-3.15.0
>>
>> Please vote to approve this release:
>>
>>          [ ] +1 Approve the release
>>          [ ]  0 Don't care
>>          [ ] -1 Don't release, because ...
>>
>> This vote will be open until at least
>>
>>      Tuesday, 19th May 2020 at 06:00 UTC
>>
>> If you expect to check the release but the time limit does not work
>> for you, please email within the schedule above with an expected time
>> and we can extend the vote period.
>>
>> Thanks,
>>
>>        Andy
>>
>> Checking needed:
>>
>> + are the GPG signatures fine?
>> + are the checksums correct?
>> + is there a source archive?
>>
>> + can the source archive really be built?
>>            (NB This requires a "mvn install" first time)
>> + is there a correct LICENSE and NOTICE file in each artifact
>>            (both source and binary artifacts)?
>> + does the NOTICE file contain all necessary attributions?
>> + have any licenses of dependencies changed due to upgrades?
>>             if so have LICENSE and NOTICE been upgraded appropriately?
>> + does the tag/commit in the SCM contain reproducible sources?

Re: [VOTE] Apache Jena 3.15.0 RC 1

Posted by Andy Seaborne <an...@apache.org>.
The vote passes with +1's from

Aaron, Bruno, Chris and Andy

and a welcome community +1 from Marco.

On to phase 2 - sync, announce and the new shiny website production.

     Andy


On 15/05/2020 15:50, Andy Seaborne wrote:
> Hi,
> 
> Here is a vote on the release of Apache Jena 3.15.0
> This is the first proposed release candidate.
> 
> The deadline is Tuesday, 19th May 2020 at 06:00 UTC
> 
> ==== Dependency changes:
> 
> JENA-1829: Apache Parent POM to v23.
> JENA-1812: Update Commons Codec 1.13 -> 1.14
> JENA-1883: Commons Lang3 : 3.9 -> 3.10
> JENA-1839: Update Commons CSV 1.7 -> 1.8
> 
> JENA-1005
> Update slf4j 1.7.26 -> 1.7.30
>    new : org.apache.logging.log4j2 version 2.13.1
>    Remove log4j1
> 
> JENA-1850: Commons compress 1.19 -> 1.20
> 
> JENA-1836: Shiro: 1.2.6 -> 1.5.1   (CVE-2019-12422)
> JENA-1850: Jetty: 9.4.12.v20180830 -> 9.4.26.v20200117
> JENA-1851: Lucene: 7.4.0 -> 7.7.2 (Not -> 8.4.1)
>             ElasticSearch 6.4.2 -> ES 6.8.6 for Lucene 7.7.x
>             (Not -> ES 7.6.0 for Lucene 8.4.x)
> 
> ==== Changes for 3.15.0:
> 
> https://s.apache.org/jena-3.15.0-jira
> 
> ==== Release Vote
> 
> Everyone, not just committers, is invited to test and vote.
> Please download and test the proposed release.
> 
> Staging repository:
>    https://repository.apache.org/content/repositories/orgapachejena-1037
> 
> Proposed dist/ area:
>    https://dist.apache.org/repos/dist/dev/jena/
> 
> Keys:
>    https://svn.apache.org/repos/asf/jena/dist/KEYS
> 
> Git commit (browser URL):
>    https://github.com/apache/jena/commit/a59b6b103c
> 
> Git Commit Hash:@@
>    a59b6b103c8b109fbbdc15f9269fab6eebfc132c
> 
> Git Commit Tag:
>    jena-3.15.0
> 
> Please vote to approve this release:
> 
>          [ ] +1 Approve the release
>          [ ]  0 Don't care
>          [ ] -1 Don't release, because ...
> 
> This vote will be open until at least
> 
>      Tuesday, 19th May 2020 at 06:00 UTC
> 
> If you expect to check the release but the time limit does not work
> for you, please email within the schedule above with an expected time
> and we can extend the vote period.
> 
> Thanks,
> 
>        Andy
> 
> Checking needed:
> 
> + are the GPG signatures fine?
> + are the checksums correct?
> + is there a source archive?
> 
> + can the source archive really be built?
>            (NB This requires a "mvn install" first time)
> + is there a correct LICENSE and NOTICE file in each artifact
>            (both source and binary artifacts)?
> + does the NOTICE file contain all necessary attributions?
> + have any licenses of dependencies changed due to upgrades?
>             if so have LICENSE and NOTICE been upgraded appropriately?
> + does the tag/commit in the SCM contain reproducible sources?

Re: [] Apache Jena 3.15.0 RC 1

Posted by Andy Seaborne <an...@apache.org>.
Thanks

There is nothing unexpected here:

> but get the following information during build for "maven clean install":
> 
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release
> Warning: Nashorn engine is planned to be removed from a future JDK release

This is a post-Java8 warning. So you are using a later Java which works, 
but warns.

ARQ supports writing extension functions in JS.

> OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated
> in version 9.0 and will likely be removed in a future release.
> Wait: 0
> Wait: 0

These two have been removed - I saw them recently.

> May 17, 2020 1:21:14 PM
> org.apache.sis.referencing.operation.transform.DefaultMathTransformFactory
> createParameterizedTransform
> WARNING: The “SIS_DATA” environment variable is not set.
> May 17, 2020 1:21:14 PM
> org.apache.sis.referencing.operation.CoordinateOperationFinder
> createOperation
> WARNING: Can not parse “OSTN15_NTv2_OSGBtoETRS.gsb” as a file in the NTv2
> format.
> May 17, 2020 1:21:14 PM
> org.apache.sis.referencing.operation.CoordinateOperationFinder
> createOperation
> WARNING: Can not parse “OSTN02_NTv2.gsb” as a file in the NTv2 format.

Expected.

----

Also the shading warnings from Shiro are expected - they are fixing the 
problem in 1.5.0 but we need 1.5.0 to get a CVE fix so we have to have 
the slightly messy message for now.

     Andy

Re: [VOTE] Apache Jena 3.15.0 RC 1

Posted by Marco Neumann <ma...@gmail.com>.
+1

[INFO] BUILD SUCCESS
[INFO] Total time:  06:05 min

openjdk version "13.0.2" 2020-01-14
Ubuntu 20.04 LTS


but get the following information during build for "maven clean install":

Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
Warning: Nashorn engine is planned to be removed from a future JDK release
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated
in version 9.0 and will likely be removed in a future release.
Wait: 0
Wait: 0
May 17, 2020 1:21:14 PM
org.apache.sis.referencing.operation.transform.DefaultMathTransformFactory
createParameterizedTransform
WARNING: The “SIS_DATA” environment variable is not set.
May 17, 2020 1:21:14 PM
org.apache.sis.referencing.operation.CoordinateOperationFinder
createOperation
WARNING: Can not parse “OSTN15_NTv2_OSGBtoETRS.gsb” as a file in the NTv2
format.
May 17, 2020 1:21:14 PM
org.apache.sis.referencing.operation.CoordinateOperationFinder
createOperation
WARNING: Can not parse “OSTN02_NTv2.gsb” as a file in the NTv2 format.



On Sat, May 16, 2020 at 7:30 PM Chris Tomlinson <ch...@gmail.com>
wrote:

> [x] +1 Approve the release
>
> Ran “mvn clean install" from release tag on GH w/ Mac OS/X 10.14.6, Java
> 1.8.0_162. No rat complaints.
> Packaged apache-jena-fuseki-3.15.0.tar.gz; ran fuseki-server w/o issue.
>
> Chris
>
>
> > On May 15, 2020, at 9:50 AM, Andy Seaborne <an...@apache.org> wrote:
> >
> > Hi,
> >
> > Here is a vote on the release of Apache Jena 3.15.0
> > This is the first proposed release candidate.
> >
> > The deadline is Tuesday, 19th May 2020 at 06:00 UTC
> >
> > ==== Dependency changes:
> >
> > JENA-1829: Apache Parent POM to v23.
> > JENA-1812: Update Commons Codec 1.13 -> 1.14
> > JENA-1883: Commons Lang3 : 3.9 -> 3.10
> > JENA-1839: Update Commons CSV 1.7 -> 1.8
> >
> > JENA-1005
> > Update slf4j 1.7.26 -> 1.7.30
> >  new : org.apache.logging.log4j2 version 2.13.1
> >  Remove log4j1
> >
> > JENA-1850: Commons compress 1.19 -> 1.20
> >
> > JENA-1836: Shiro: 1.2.6 -> 1.5.1   (CVE-2019-12422)
> > JENA-1850: Jetty: 9.4.12.v20180830 -> 9.4.26.v20200117
> > JENA-1851: Lucene: 7.4.0 -> 7.7.2 (Not -> 8.4.1)
> >           ElasticSearch 6.4.2 -> ES 6.8.6 for Lucene 7.7.x
> >           (Not -> ES 7.6.0 for Lucene 8.4.x)
> >
> > ==== Changes for 3.15.0:
> >
> > https://s.apache.org/jena-3.15.0-jira
> >
> > ==== Release Vote
> >
> > Everyone, not just committers, is invited to test and vote.
> > Please download and test the proposed release.
> >
> > Staging repository:
> >  https://repository.apache.org/content/repositories/orgapachejena-1037
> >
> > Proposed dist/ area:
> >  https://dist.apache.org/repos/dist/dev/jena/
> >
> > Keys:
> >  https://svn.apache.org/repos/asf/jena/dist/KEYS
> >
> > Git commit (browser URL):
> >  https://github.com/apache/jena/commit/a59b6b103c
> >
> > Git Commit Hash:@@
> >  a59b6b103c8b109fbbdc15f9269fab6eebfc132c
> >
> > Git Commit Tag:
> >  jena-3.15.0
> >
> > Please vote to approve this release:
> >
> >        [ ] +1 Approve the release
> >        [ ]  0 Don't care
> >        [ ] -1 Don't release, because ...
> >
> > This vote will be open until at least
> >
> >    Tuesday, 19th May 2020 at 06:00 UTC
> >
> > If you expect to check the release but the time limit does not work
> > for you, please email within the schedule above with an expected time
> > and we can extend the vote period.
> >
> > Thanks,
> >
> >      Andy
> >
> > Checking needed:
> >
> > + are the GPG signatures fine?
> > + are the checksums correct?
> > + is there a source archive?
> >
> > + can the source archive really be built?
> >          (NB This requires a "mvn install" first time)
> > + is there a correct LICENSE and NOTICE file in each artifact
> >          (both source and binary artifacts)?
> > + does the NOTICE file contain all necessary attributions?
> > + have any licenses of dependencies changed due to upgrades?
> >           if so have LICENSE and NOTICE been upgraded appropriately?
> > + does the tag/commit in the SCM contain reproducible sources?
>
>

-- 


---
Marco Neumann
KONA

Re: [VOTE] Apache Jena 3.15.0 RC 1

Posted by Chris Tomlinson <ch...@gmail.com>.
[x] +1 Approve the release

Ran “mvn clean install" from release tag on GH w/ Mac OS/X 10.14.6, Java 1.8.0_162. No rat complaints.
Packaged apache-jena-fuseki-3.15.0.tar.gz; ran fuseki-server w/o issue.

Chris


> On May 15, 2020, at 9:50 AM, Andy Seaborne <an...@apache.org> wrote:
> 
> Hi,
> 
> Here is a vote on the release of Apache Jena 3.15.0
> This is the first proposed release candidate.
> 
> The deadline is Tuesday, 19th May 2020 at 06:00 UTC
> 
> ==== Dependency changes:
> 
> JENA-1829: Apache Parent POM to v23.
> JENA-1812: Update Commons Codec 1.13 -> 1.14
> JENA-1883: Commons Lang3 : 3.9 -> 3.10
> JENA-1839: Update Commons CSV 1.7 -> 1.8
> 
> JENA-1005
> Update slf4j 1.7.26 -> 1.7.30
>  new : org.apache.logging.log4j2 version 2.13.1
>  Remove log4j1
> 
> JENA-1850: Commons compress 1.19 -> 1.20
> 
> JENA-1836: Shiro: 1.2.6 -> 1.5.1   (CVE-2019-12422)
> JENA-1850: Jetty: 9.4.12.v20180830 -> 9.4.26.v20200117
> JENA-1851: Lucene: 7.4.0 -> 7.7.2 (Not -> 8.4.1)
>           ElasticSearch 6.4.2 -> ES 6.8.6 for Lucene 7.7.x
>           (Not -> ES 7.6.0 for Lucene 8.4.x)
> 
> ==== Changes for 3.15.0:
> 
> https://s.apache.org/jena-3.15.0-jira
> 
> ==== Release Vote
> 
> Everyone, not just committers, is invited to test and vote.
> Please download and test the proposed release.
> 
> Staging repository:
>  https://repository.apache.org/content/repositories/orgapachejena-1037
> 
> Proposed dist/ area:
>  https://dist.apache.org/repos/dist/dev/jena/
> 
> Keys:
>  https://svn.apache.org/repos/asf/jena/dist/KEYS
> 
> Git commit (browser URL):
>  https://github.com/apache/jena/commit/a59b6b103c
> 
> Git Commit Hash:@@
>  a59b6b103c8b109fbbdc15f9269fab6eebfc132c
> 
> Git Commit Tag:
>  jena-3.15.0
> 
> Please vote to approve this release:
> 
>        [ ] +1 Approve the release
>        [ ]  0 Don't care
>        [ ] -1 Don't release, because ...
> 
> This vote will be open until at least
> 
>    Tuesday, 19th May 2020 at 06:00 UTC
> 
> If you expect to check the release but the time limit does not work
> for you, please email within the schedule above with an expected time
> and we can extend the vote period.
> 
> Thanks,
> 
>      Andy
> 
> Checking needed:
> 
> + are the GPG signatures fine?
> + are the checksums correct?
> + is there a source archive?
> 
> + can the source archive really be built?
>          (NB This requires a "mvn install" first time)
> + is there a correct LICENSE and NOTICE file in each artifact
>          (both source and binary artifacts)?
> + does the NOTICE file contain all necessary attributions?
> + have any licenses of dependencies changed due to upgrades?
>           if so have LICENSE and NOTICE been upgraded appropriately?
> + does the tag/commit in the SCM contain reproducible sources?


Re: [VOTE] Apache Jena 3.15.0 RC 1

Posted by "Bruno P. Kinoshita" <ki...@apache.org>.
  [x] +1 Approve the release

Building fine from tag on Ubuntu LTS with Java 8.

Bruno

    On Saturday, 16 May 2020, 2:50:36 am NZST, Andy Seaborne <an...@apache.org> wrote:  
 
 Hi,

Here is a vote on the release of Apache Jena 3.15.0
This is the first proposed release candidate.

The deadline is Tuesday, 19th May 2020 at 06:00 UTC

==== Dependency changes:

JENA-1829: Apache Parent POM to v23.
JENA-1812: Update Commons Codec 1.13 -> 1.14
JENA-1883: Commons Lang3 : 3.9 -> 3.10
JENA-1839: Update Commons CSV 1.7 -> 1.8

JENA-1005
Update slf4j 1.7.26 -> 1.7.30
  new : org.apache.logging.log4j2 version 2.13.1
  Remove log4j1

JENA-1850: Commons compress 1.19 -> 1.20

JENA-1836: Shiro: 1.2.6 -> 1.5.1  (CVE-2019-12422)
JENA-1850: Jetty: 9.4.12.v20180830 -> 9.4.26.v20200117
JENA-1851: Lucene: 7.4.0 -> 7.7.2 (Not -> 8.4.1)
            ElasticSearch 6.4.2 -> ES 6.8.6 for Lucene 7.7.x
            (Not -> ES 7.6.0 for Lucene 8.4.x)

==== Changes for 3.15.0:

https://s.apache.org/jena-3.15.0-jira

==== Release Vote

Everyone, not just committers, is invited to test and vote.
Please download and test the proposed release.

Staging repository:
  https://repository.apache.org/content/repositories/orgapachejena-1037

Proposed dist/ area:
  https://dist.apache.org/repos/dist/dev/jena/

Keys:
  https://svn.apache.org/repos/asf/jena/dist/KEYS

Git commit (browser URL):
  https://github.com/apache/jena/commit/a59b6b103c

Git Commit Hash:@@
  a59b6b103c8b109fbbdc15f9269fab6eebfc132c

Git Commit Tag:
  jena-3.15.0

Please vote to approve this release:

        [ ] +1 Approve the release
        [ ]  0 Don't care
        [ ] -1 Don't release, because ...

This vote will be open until at least

    Tuesday, 19th May 2020 at 06:00 UTC

If you expect to check the release but the time limit does not work
for you, please email within the schedule above with an expected time
and we can extend the vote period.

Thanks,

      Andy

Checking needed:

+ are the GPG signatures fine?
+ are the checksums correct?
+ is there a source archive?

+ can the source archive really be built?
          (NB This requires a "mvn install" first time)
+ is there a correct LICENSE and NOTICE file in each artifact
          (both source and binary artifacts)?
+ does the NOTICE file contain all necessary attributions?
+ have any licenses of dependencies changed due to upgrades?
            if so have LICENSE and NOTICE been upgraded appropriately?
+ does the tag/commit in the SCM contain reproducible sources?
  

Re: [VOTE] Apache Jena 3.15.0 RC 1

Posted by Aaron Coburn <ac...@apache.org>.
+1 (binding)

Hashes are good
Signatures are good
Built successfully from release tag on SCM (using JDK 8)
Built successfully from source artifact (using JDK 11)
Deployed successfully into Karaf 4.2.8
Verified that Jena 3.15 works in JPMS mode under Java 11
Successfully tested the new commons-rdf implementation
All the artifacts have NOTICE and LICENSE files

Aaron


On Fri, 15 May 2020 at 11:55, Andy Seaborne <an...@apache.org> wrote:

> +1
>
>      Andy
>
> On 15/05/2020 15:50, Andy Seaborne wrote:
> > Hi,
> >
> > Here is a vote on the release of Apache Jena 3.15.0
> > This is the first proposed release candidate.
> >
> > The deadline is Tuesday, 19th May 2020 at 06:00 UTC
> >
> > ==== Dependency changes:
> >
> > JENA-1829: Apache Parent POM to v23.
> > JENA-1812: Update Commons Codec 1.13 -> 1.14
> > JENA-1883: Commons Lang3 : 3.9 -> 3.10
> > JENA-1839: Update Commons CSV 1.7 -> 1.8
> >
> > JENA-1005
> > Update slf4j 1.7.26 -> 1.7.30
> >    new : org.apache.logging.log4j2 version 2.13.1
> >    Remove log4j1
> >
> > JENA-1850: Commons compress 1.19 -> 1.20
> >
> > JENA-1836: Shiro: 1.2.6 -> 1.5.1   (CVE-2019-12422)
> > JENA-1850: Jetty: 9.4.12.v20180830 -> 9.4.26.v20200117
> > JENA-1851: Lucene: 7.4.0 -> 7.7.2 (Not -> 8.4.1)
> >             ElasticSearch 6.4.2 -> ES 6.8.6 for Lucene 7.7.x
> >             (Not -> ES 7.6.0 for Lucene 8.4.x)
> >
> > ==== Changes for 3.15.0:
> >
> > https://s.apache.org/jena-3.15.0-jira
> >
> > ==== Release Vote
> >
> > Everyone, not just committers, is invited to test and vote.
> > Please download and test the proposed release.
> >
> > Staging repository:
> >    https://repository.apache.org/content/repositories/orgapachejena-1037
> >
> > Proposed dist/ area:
> >    https://dist.apache.org/repos/dist/dev/jena/
> >
> > Keys:
> >    https://svn.apache.org/repos/asf/jena/dist/KEYS
> >
> > Git commit (browser URL):
> >    https://github.com/apache/jena/commit/a59b6b103c
> >
> > Git Commit Hash:@@
> >    a59b6b103c8b109fbbdc15f9269fab6eebfc132c
> >
> > Git Commit Tag:
> >    jena-3.15.0
> >
> > Please vote to approve this release:
> >
> >          [ ] +1 Approve the release
> >          [ ]  0 Don't care
> >          [ ] -1 Don't release, because ...
> >
> > This vote will be open until at least
> >
> >      Tuesday, 19th May 2020 at 06:00 UTC
> >
> > If you expect to check the release but the time limit does not work
> > for you, please email within the schedule above with an expected time
> > and we can extend the vote period.
> >
> > Thanks,
> >
> >        Andy
> >
> > Checking needed:
> >
> > + are the GPG signatures fine?
> > + are the checksums correct?
> > + is there a source archive?
> >
> > + can the source archive really be built?
> >            (NB This requires a "mvn install" first time)
> > + is there a correct LICENSE and NOTICE file in each artifact
> >            (both source and binary artifacts)?
> > + does the NOTICE file contain all necessary attributions?
> > + have any licenses of dependencies changed due to upgrades?
> >             if so have LICENSE and NOTICE been upgraded appropriately?
> > + does the tag/commit in the SCM contain reproducible sources?
>

Re: [VOTE] Apache Jena 3.15.0 RC 1

Posted by Andy Seaborne <an...@apache.org>.
+1

     Andy

On 15/05/2020 15:50, Andy Seaborne wrote:
> Hi,
> 
> Here is a vote on the release of Apache Jena 3.15.0
> This is the first proposed release candidate.
> 
> The deadline is Tuesday, 19th May 2020 at 06:00 UTC
> 
> ==== Dependency changes:
> 
> JENA-1829: Apache Parent POM to v23.
> JENA-1812: Update Commons Codec 1.13 -> 1.14
> JENA-1883: Commons Lang3 : 3.9 -> 3.10
> JENA-1839: Update Commons CSV 1.7 -> 1.8
> 
> JENA-1005
> Update slf4j 1.7.26 -> 1.7.30
>    new : org.apache.logging.log4j2 version 2.13.1
>    Remove log4j1
> 
> JENA-1850: Commons compress 1.19 -> 1.20
> 
> JENA-1836: Shiro: 1.2.6 -> 1.5.1   (CVE-2019-12422)
> JENA-1850: Jetty: 9.4.12.v20180830 -> 9.4.26.v20200117
> JENA-1851: Lucene: 7.4.0 -> 7.7.2 (Not -> 8.4.1)
>             ElasticSearch 6.4.2 -> ES 6.8.6 for Lucene 7.7.x
>             (Not -> ES 7.6.0 for Lucene 8.4.x)
> 
> ==== Changes for 3.15.0:
> 
> https://s.apache.org/jena-3.15.0-jira
> 
> ==== Release Vote
> 
> Everyone, not just committers, is invited to test and vote.
> Please download and test the proposed release.
> 
> Staging repository:
>    https://repository.apache.org/content/repositories/orgapachejena-1037
> 
> Proposed dist/ area:
>    https://dist.apache.org/repos/dist/dev/jena/
> 
> Keys:
>    https://svn.apache.org/repos/asf/jena/dist/KEYS
> 
> Git commit (browser URL):
>    https://github.com/apache/jena/commit/a59b6b103c
> 
> Git Commit Hash:@@
>    a59b6b103c8b109fbbdc15f9269fab6eebfc132c
> 
> Git Commit Tag:
>    jena-3.15.0
> 
> Please vote to approve this release:
> 
>          [ ] +1 Approve the release
>          [ ]  0 Don't care
>          [ ] -1 Don't release, because ...
> 
> This vote will be open until at least
> 
>      Tuesday, 19th May 2020 at 06:00 UTC
> 
> If you expect to check the release but the time limit does not work
> for you, please email within the schedule above with an expected time
> and we can extend the vote period.
> 
> Thanks,
> 
>        Andy
> 
> Checking needed:
> 
> + are the GPG signatures fine?
> + are the checksums correct?
> + is there a source archive?
> 
> + can the source archive really be built?
>            (NB This requires a "mvn install" first time)
> + is there a correct LICENSE and NOTICE file in each artifact
>            (both source and binary artifacts)?
> + does the NOTICE file contain all necessary attributions?
> + have any licenses of dependencies changed due to upgrades?
>             if so have LICENSE and NOTICE been upgraded appropriately?
> + does the tag/commit in the SCM contain reproducible sources?

Re: [] Apache Jena 3.15.0 RC 1

Posted by Andy Seaborne <an...@apache.org>.
JENA-1898 (version of commons-codec) is not a problem users will 
encounter. Depending on apache-jena-libs will bring the right version in.

I can only get it to happen by depending on test artifacts, which 
because they are not recursive, changes the depth and encounter order 
for maven dependencies - and then only sometimes.

JENA-1812 switched to using Murmur3 for some hashing and that's not in 
commons-codec 1.11

Why now? (and not during development) The project was using 
3.15.0-SNAPSHOT anyway. Why it flipped when set to use a 3.16.0-SNAPSHOT 
isn't clear - my guess is that a slight order change has happened (same 
depth, different order).

     Andy

https://issues.apache.org/jira/browse/JENA-1898

On 15/05/2020 15:50, Andy Seaborne wrote:
> Hi,
> 
> Here is a vote on the release of Apache Jena 3.15.0
> This is the first proposed release candidate.
> 
> The deadline is Tuesday, 19th May 2020 at 06:00 UTC
> 
> ==== Dependency changes:
> 
> JENA-1829: Apache Parent POM to v23.
> JENA-1812: Update Commons Codec 1.13 -> 1.14
> JENA-1883: Commons Lang3 : 3.9 -> 3.10
> JENA-1839: Update Commons CSV 1.7 -> 1.8
> 
> JENA-1005
> Update slf4j 1.7.26 -> 1.7.30
>    new : org.apache.logging.log4j2 version 2.13.1
>    Remove log4j1
> 
> JENA-1850: Commons compress 1.19 -> 1.20
> 
> JENA-1836: Shiro: 1.2.6 -> 1.5.1   (CVE-2019-12422)
> JENA-1850: Jetty: 9.4.12.v20180830 -> 9.4.26.v20200117
> JENA-1851: Lucene: 7.4.0 -> 7.7.2 (Not -> 8.4.1)
>             ElasticSearch 6.4.2 -> ES 6.8.6 for Lucene 7.7.x
>             (Not -> ES 7.6.0 for Lucene 8.4.x)
> 
> ==== Changes for 3.15.0:
> 
> https://s.apache.org/jena-3.15.0-jira
> 
> ==== Release Vote
> 
> Everyone, not just committers, is invited to test and vote.
> Please download and test the proposed release.
> 
> Staging repository:
>    https://repository.apache.org/content/repositories/orgapachejena-1037
> 
> Proposed dist/ area:
>    https://dist.apache.org/repos/dist/dev/jena/
> 
> Keys:
>    https://svn.apache.org/repos/asf/jena/dist/KEYS
> 
> Git commit (browser URL):
>    https://github.com/apache/jena/commit/a59b6b103c
> 
> Git Commit Hash:@@
>    a59b6b103c8b109fbbdc15f9269fab6eebfc132c
> 
> Git Commit Tag:
>    jena-3.15.0
> 
> Please vote to approve this release:
> 
>          [ ] +1 Approve the release
>          [ ]  0 Don't care
>          [ ] -1 Don't release, because ...
> 
> This vote will be open until at least
> 
>      Tuesday, 19th May 2020 at 06:00 UTC
> 
> If you expect to check the release but the time limit does not work
> for you, please email within the schedule above with an expected time
> and we can extend the vote period.
> 
> Thanks,
> 
>        Andy
> 
> Checking needed:
> 
> + are the GPG signatures fine?
> + are the checksums correct?
> + is there a source archive?
> 
> + can the source archive really be built?
>            (NB This requires a "mvn install" first time)
> + is there a correct LICENSE and NOTICE file in each artifact
>            (both source and binary artifacts)?
> + does the NOTICE file contain all necessary attributions?
> + have any licenses of dependencies changed due to upgrades?
>             if so have LICENSE and NOTICE been upgraded appropriately?
> + does the tag/commit in the SCM contain reproducible sources?