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 2018/10/04 12:16:10 UTC
Re: [] Apache Jena 3.9.0 RC1
Hi,
Could I get a 3rd PMC vote for this release, please?
(a indicative, not binding, indication of timescale is helpful).
Andy
On 29/09/18 10:22, Andy Seaborne wrote:
> Hi,
>
> Here is a vote on a release of Jena 3.9.0.
> This is the first proposed candidate.
>
> The deadline is Wednesday, 2018-10-03, 08:00 UTC.
>
>
> ==== Process Change
>
> The jena-VER-source-release.zip that goes into /source now has a
> ".sha512" as per the ASF new recommendations and this is now generated
> by the build itself. There is no SHA1 in /source and MD5 was already not
> recommended. The copy that goes to maven central still has .md5 and sha1
> (these are de facto hard coded into the way maven works).
>
> ==== Release changes:
>
> 37 JIRA:
> https://s.apache.org/jena-3.9.0-jira
>
> == Upgrades to libraries (runtime dependencies):
>
> No license changes.
>
> Apache parent v20 -> v21
> JSON-LD 0.12.0 -> 0.12.1
> Jetty 9.4.7.v20170914 -> 9.4.12.v20180830
>
> == Changes of note:
>
> JENA-1598
> Upgrade Jetty to 9.4.12.v20180830
> (this fixes several CVEs)
>
> JENA-1593
> Update Apache parent POM to v21
>
> JENA-1599
> Upgrade to jsonld-java version 0.12.1
>
> JENA-1594
> Provide per-graph access control in Fuseki
> New maven module for Fuseki2.
>
> JENA-1585
> Reorganize the Fuseki codebase to split the server engine classes from
> the webapp classes
>
> JENA-1573
> Remove the jena-fuseki1 distribution
> The jar is still available.
>
> JENA-1571
> Remove the jena-sdb distribution.
> The jar is still available.
>
> JENA-1481
> Deleting a dataset in Fuseki now deletes it permanently
>
> JENA-868
> Fuseki2: docker: When redirecting ports, UI URLs should now work.
>
> ==== 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-1025
>
> 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/30f2f1e9031d
>
> Git Commit Hash:
> 30f2f1e9031d17b5c70cb6432233c8c8d95d6a2e
>
> Git Commit Tag:
> jena-3.9.0-rc1
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
>
> This vote will be open to at least
>
> Wednesday, 2018-10-03, 08: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:
>
> + does everything work on Linux?
> + does everything work on MS Windows?
> + does everything work on OS X?
> + 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.9.0 RC1
Posted by Andy Seaborne <an...@apache.org>.
Bruno - thank you for the testing.
Looks like the dreaded windows-can't-delete-mmap-files issue in test for
JENA-1481 (delete a managed database via the UI).
I'll try a fix out on ASF Jenkins.
I hope it will be OK with everyone to fix in the development codebase
and release this Jena 3.9.0 RC as-is.
Andy
On 04/10/18 23:04, Bruno P. Kinoshita wrote:
> Build passing with `mvn clean install -Pdev` 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-36-generic", arch: "amd64", family: "unix"
>
>
> Checked binaries in dist area, and signatures look good.
>
> Also checked the sha512 signature for the source file and it looks good too.
>
> Had some extra time and decided to build on Windows too. Build failed with:
>
> """
>
> [ERROR] Failures:
> [ERROR] TestAdminAPI.add_delete_api_1:49->testAddDelete:84->Assert.assertFalse:74->Assert.assertFalse:64->Assert.assertTrue:41->Assert.fail:86
> [ERROR] TestAdminAPI.add_delete_api_2:53->testAddDelete:84->Assert.assertFalse:74->Assert.assertFalse:64->Assert.assertTrue:41->Assert.fail:86
> [ERROR] TestAdminAPI.add_delete_api_3:57->testAddDelete:84->Assert.assertFalse:74->Assert.assertFalse:64->Assert.assertTrue:41->Assert.fail:86
> [INFO]
> [ERROR] Tests run: 172, Failures: 3, Errors: 0, Skipped: 0
> """
>
>
> A more complete snippet of the error can be found here: https://gist.github.com/kinow/8f7fa57a8f189f89803e6de769deb2f2
>
> And Windows env is a Win10 pro:
>
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-04T07:39:06+12:00)
> Maven home: C:\Users\kinoshitabd\Development\java\apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_144\jre
> Default locale: en_NZ, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> Not sure if a blocker... if not, here's my vote
>
>
>> [ X ] +1 Approve the release
>
>
>
> Thanks!
> Bruno
>
>
>
> ________________________________
> From: Andy Seaborne <an...@apache.org>
> To: "dev@jena.apache.org" <de...@jena.apache.org>
> Sent: Friday, 5 October 2018 1:29 AM
> Subject: Re: [] Apache Jena 3.9.0 RC1
>
>
>
> Hi,
>
> Could I get a 3rd PMC vote for this release, please?
> (a indicative, not binding, indication of timescale is helpful).
>
> Andy
>
>
> On 29/09/18 10:22, Andy Seaborne wrote:
>> Hi,
>>
>> Here is a vote on a release of Jena 3.9.0.
>> This is the first proposed candidate.
>>
>> The deadline is Wednesday, 2018-10-03, 08:00 UTC.
>>
>>
>> ==== Process Change
>>
>> The jena-VER-source-release.zip that goes into /source now has a
>> ".sha512" as per the ASF new recommendations and this is now generated
>> by the build itself. There is no SHA1 in /source and MD5 was already not
>> recommended. The copy that goes to maven central still has .md5 and sha1
>> (these are de facto hard coded into the way maven works).
>>
>> ==== Release changes:
>>
>> 37 JIRA:
>> https://s.apache.org/jena-3.9.0-jira
>>
>> == Upgrades to libraries (runtime dependencies):
>>
>> No license changes.
>>
>> Apache parent v20 -> v21
>> JSON-LD 0.12.0 -> 0.12.1
>> Jetty 9.4.7.v20170914 -> 9.4.12.v20180830
>>
>> == Changes of note:
>>
>> JENA-1598
>> Upgrade Jetty to 9.4.12.v20180830
>> (this fixes several CVEs)
>>
>> JENA-1593
>> Update Apache parent POM to v21
>>
>> JENA-1599
>> Upgrade to jsonld-java version 0.12.1
>>
>> JENA-1594
>> Provide per-graph access control in Fuseki
>> New maven module for Fuseki2.
>>
>> JENA-1585
>> Reorganize the Fuseki codebase to split the server engine classes from
>> the webapp classes
>>
>> JENA-1573
>> Remove the jena-fuseki1 distribution
>> The jar is still available.
>>
>> JENA-1571
>> Remove the jena-sdb distribution.
>> The jar is still available.
>>
>> JENA-1481
>> Deleting a dataset in Fuseki now deletes it permanently
>>
>> JENA-868
>> Fuseki2: docker: When redirecting ports, UI URLs should now work.
>>
>> ==== 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-1025
>>
>> 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/30f2f1e9031d
>>
>> Git Commit Hash:
>> 30f2f1e9031d17b5c70cb6432233c8c8d95d6a2e
>>
>> Git Commit Tag:
>> jena-3.9.0-rc1
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] 0 Don't care
>> [ ] -1 Don't release, because ...
>>
>> This vote will be open to at least
>>
>> Wednesday, 2018-10-03, 08: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:
>>
>> + does everything work on Linux?
>> + does everything work on MS Windows?
>> + does everything work on OS X?
>> + 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.9.0 RC1
Posted by Andy Seaborne <an...@apache.org>.
These are new test for deleting TDB databases from a running Fuseki
server but they assume the database is deleted immediately whereas on MS
Windows, the files will not go away until the JVM exits because of the
mmap files.
The only fix is to ignore these tests on Windows.
There is a bug in add_delete_api_1 which is a test for memory databases
- but the code ignores the db request type and defaults to TDB.
I have run the tests on ASF Jenkins Windows and it fails, then applied
the fix to skip the tests for TDB/TDB2 on Windows, and the build than
passes. add_delete_api_1 (mem) does pass, _2 (tdb) and _3 (tdb2) are
skipped.
JIRA:
https://issues.apache.org/jira/browse/JENA-1611
Commit:
https://git-wip-us.apache.org/repos/asf?p=jena.git;h=ecb01ec
Bruno - is this good enough to continue this release?
Andy
On 04/10/18 23:04, Bruno P. Kinoshita wrote:
> Build passing with `mvn clean install -Pdev` 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-36-generic", arch: "amd64", family: "unix"
>
>
> Checked binaries in dist area, and signatures look good.
>
> Also checked the sha512 signature for the source file and it looks good too.
>
> Had some extra time and decided to build on Windows too. Build failed with:
>
> """
>
> [ERROR] Failures:
> [ERROR] TestAdminAPI.add_delete_api_1:49->testAddDelete:84->Assert.assertFalse:74->Assert.assertFalse:64->Assert.assertTrue:41->Assert.fail:86
> [ERROR] TestAdminAPI.add_delete_api_2:53->testAddDelete:84->Assert.assertFalse:74->Assert.assertFalse:64->Assert.assertTrue:41->Assert.fail:86
> [ERROR] TestAdminAPI.add_delete_api_3:57->testAddDelete:84->Assert.assertFalse:74->Assert.assertFalse:64->Assert.assertTrue:41->Assert.fail:86
> [INFO]
> [ERROR] Tests run: 172, Failures: 3, Errors: 0, Skipped: 0
> """
>
>
> A more complete snippet of the error can be found here: https://gist.github.com/kinow/8f7fa57a8f189f89803e6de769deb2f2
>
> And Windows env is a Win10 pro:
>
> Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-04T07:39:06+12:00)
> Maven home: C:\Users\kinoshitabd\Development\java\apache-maven-3.5.0
> Java version: 1.8.0_144, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_144\jre
> Default locale: en_NZ, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> Not sure if a blocker... if not, here's my vote
>
>
>> [ X ] +1 Approve the release
>
>
>
> Thanks!
> Bruno
>
>
>
> ________________________________
> From: Andy Seaborne <an...@apache.org>
> To: "dev@jena.apache.org" <de...@jena.apache.org>
> Sent: Friday, 5 October 2018 1:29 AM
> Subject: Re: [] Apache Jena 3.9.0 RC1
>
>
>
> Hi,
>
> Could I get a 3rd PMC vote for this release, please?
> (a indicative, not binding, indication of timescale is helpful).
>
> Andy
>
>
> On 29/09/18 10:22, Andy Seaborne wrote:
>> Hi,
>>
>> Here is a vote on a release of Jena 3.9.0.
>> This is the first proposed candidate.
>>
>> The deadline is Wednesday, 2018-10-03, 08:00 UTC.
>>
>>
>> ==== Process Change
>>
>> The jena-VER-source-release.zip that goes into /source now has a
>> ".sha512" as per the ASF new recommendations and this is now generated
>> by the build itself. There is no SHA1 in /source and MD5 was already not
>> recommended. The copy that goes to maven central still has .md5 and sha1
>> (these are de facto hard coded into the way maven works).
>>
>> ==== Release changes:
>>
>> 37 JIRA:
>> https://s.apache.org/jena-3.9.0-jira
>>
>> == Upgrades to libraries (runtime dependencies):
>>
>> No license changes.
>>
>> Apache parent v20 -> v21
>> JSON-LD 0.12.0 -> 0.12.1
>> Jetty 9.4.7.v20170914 -> 9.4.12.v20180830
>>
>> == Changes of note:
>>
>> JENA-1598
>> Upgrade Jetty to 9.4.12.v20180830
>> (this fixes several CVEs)
>>
>> JENA-1593
>> Update Apache parent POM to v21
>>
>> JENA-1599
>> Upgrade to jsonld-java version 0.12.1
>>
>> JENA-1594
>> Provide per-graph access control in Fuseki
>> New maven module for Fuseki2.
>>
>> JENA-1585
>> Reorganize the Fuseki codebase to split the server engine classes from
>> the webapp classes
>>
>> JENA-1573
>> Remove the jena-fuseki1 distribution
>> The jar is still available.
>>
>> JENA-1571
>> Remove the jena-sdb distribution.
>> The jar is still available.
>>
>> JENA-1481
>> Deleting a dataset in Fuseki now deletes it permanently
>>
>> JENA-868
>> Fuseki2: docker: When redirecting ports, UI URLs should now work.
>>
>> ==== 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-1025
>>
>> 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/30f2f1e9031d
>>
>> Git Commit Hash:
>> 30f2f1e9031d17b5c70cb6432233c8c8d95d6a2e
>>
>> Git Commit Tag:
>> jena-3.9.0-rc1
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] 0 Don't care
>> [ ] -1 Don't release, because ...
>>
>> This vote will be open to at least
>>
>> Wednesday, 2018-10-03, 08: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:
>>
>> + does everything work on Linux?
>> + does everything work on MS Windows?
>> + does everything work on OS X?
>> + 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.9.0 RC1
Posted by "Bruno P. Kinoshita" <ki...@apache.org>.
Build passing with `mvn clean install -Pdev` 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-36-generic", arch: "amd64", family: "unix"
Checked binaries in dist area, and signatures look good.
Also checked the sha512 signature for the source file and it looks good too.
Had some extra time and decided to build on Windows too. Build failed with:
"""
[ERROR] Failures:
[ERROR] TestAdminAPI.add_delete_api_1:49->testAddDelete:84->Assert.assertFalse:74->Assert.assertFalse:64->Assert.assertTrue:41->Assert.fail:86
[ERROR] TestAdminAPI.add_delete_api_2:53->testAddDelete:84->Assert.assertFalse:74->Assert.assertFalse:64->Assert.assertTrue:41->Assert.fail:86
[ERROR] TestAdminAPI.add_delete_api_3:57->testAddDelete:84->Assert.assertFalse:74->Assert.assertFalse:64->Assert.assertTrue:41->Assert.fail:86
[INFO]
[ERROR] Tests run: 172, Failures: 3, Errors: 0, Skipped: 0
"""
A more complete snippet of the error can be found here: https://gist.github.com/kinow/8f7fa57a8f189f89803e6de769deb2f2
And Windows env is a Win10 pro:
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-04T07:39:06+12:00)
Maven home: C:\Users\kinoshitabd\Development\java\apache-maven-3.5.0
Java version: 1.8.0_144, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_144\jre
Default locale: en_NZ, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Not sure if a blocker... if not, here's my vote
> [ X ] +1 Approve the release
Thanks!
Bruno
________________________________
From: Andy Seaborne <an...@apache.org>
To: "dev@jena.apache.org" <de...@jena.apache.org>
Sent: Friday, 5 October 2018 1:29 AM
Subject: Re: [] Apache Jena 3.9.0 RC1
Hi,
Could I get a 3rd PMC vote for this release, please?
(a indicative, not binding, indication of timescale is helpful).
Andy
On 29/09/18 10:22, Andy Seaborne wrote:
> Hi,
>
> Here is a vote on a release of Jena 3.9.0.
> This is the first proposed candidate.
>
> The deadline is Wednesday, 2018-10-03, 08:00 UTC.
>
>
> ==== Process Change
>
> The jena-VER-source-release.zip that goes into /source now has a
> ".sha512" as per the ASF new recommendations and this is now generated
> by the build itself. There is no SHA1 in /source and MD5 was already not
> recommended. The copy that goes to maven central still has .md5 and sha1
> (these are de facto hard coded into the way maven works).
>
> ==== Release changes:
>
> 37 JIRA:
> https://s.apache.org/jena-3.9.0-jira
>
> == Upgrades to libraries (runtime dependencies):
>
> No license changes.
>
> Apache parent v20 -> v21
> JSON-LD 0.12.0 -> 0.12.1
> Jetty 9.4.7.v20170914 -> 9.4.12.v20180830
>
> == Changes of note:
>
> JENA-1598
> Upgrade Jetty to 9.4.12.v20180830
> (this fixes several CVEs)
>
> JENA-1593
> Update Apache parent POM to v21
>
> JENA-1599
> Upgrade to jsonld-java version 0.12.1
>
> JENA-1594
> Provide per-graph access control in Fuseki
> New maven module for Fuseki2.
>
> JENA-1585
> Reorganize the Fuseki codebase to split the server engine classes from
> the webapp classes
>
> JENA-1573
> Remove the jena-fuseki1 distribution
> The jar is still available.
>
> JENA-1571
> Remove the jena-sdb distribution.
> The jar is still available.
>
> JENA-1481
> Deleting a dataset in Fuseki now deletes it permanently
>
> JENA-868
> Fuseki2: docker: When redirecting ports, UI URLs should now work.
>
> ==== 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-1025
>
> 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/30f2f1e9031d
>
> Git Commit Hash:
> 30f2f1e9031d17b5c70cb6432233c8c8d95d6a2e
>
> Git Commit Tag:
> jena-3.9.0-rc1
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
>
> This vote will be open to at least
>
> Wednesday, 2018-10-03, 08: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:
>
> + does everything work on Linux?
> + does everything work on MS Windows?
> + does everything work on OS X?
> + 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.9.0 RC1
Posted by "Bruno P. Kinoshita" <ki...@apache.org>.
I can review it in about 9 hours, just turned workstation off.
Tis OK if another PMC beats me to it :)
Bruno
Sent from Yahoo Mail on Android
On Fri, 5 Oct 2018 at 1:29, Andy Seaborne<an...@apache.org> wrote: Hi,
Could I get a 3rd PMC vote for this release, please?
(a indicative, not binding, indication of timescale is helpful).
Andy
On 29/09/18 10:22, Andy Seaborne wrote:
> Hi,
>
> Here is a vote on a release of Jena 3.9.0.
> This is the first proposed candidate.
>
> The deadline is Wednesday, 2018-10-03, 08:00 UTC.
>
>
> ==== Process Change
>
> The jena-VER-source-release.zip that goes into /source now has a
> ".sha512" as per the ASF new recommendations and this is now generated
> by the build itself. There is no SHA1 in /source and MD5 was already not
> recommended. The copy that goes to maven central still has .md5 and sha1
> (these are de facto hard coded into the way maven works).
>
> ==== Release changes:
>
> 37 JIRA:
> https://s.apache.org/jena-3.9.0-jira
>
> == Upgrades to libraries (runtime dependencies):
>
> No license changes.
>
> Apache parent v20 -> v21
> JSON-LD 0.12.0 -> 0.12.1
> Jetty 9.4.7.v20170914 -> 9.4.12.v20180830
>
> == Changes of note:
>
> JENA-1598
> Upgrade Jetty to 9.4.12.v20180830
> (this fixes several CVEs)
>
> JENA-1593
> Update Apache parent POM to v21
>
> JENA-1599
> Upgrade to jsonld-java version 0.12.1
>
> JENA-1594
> Provide per-graph access control in Fuseki
> New maven module for Fuseki2.
>
> JENA-1585
> Reorganize the Fuseki codebase to split the server engine classes from
> the webapp classes
>
> JENA-1573
> Remove the jena-fuseki1 distribution
> The jar is still available.
>
> JENA-1571
> Remove the jena-sdb distribution.
> The jar is still available.
>
> JENA-1481
> Deleting a dataset in Fuseki now deletes it permanently
>
> JENA-868
> Fuseki2: docker: When redirecting ports, UI URLs should now work.
>
> ==== 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-1025
>
> 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/30f2f1e9031d
>
> Git Commit Hash:
> 30f2f1e9031d17b5c70cb6432233c8c8d95d6a2e
>
> Git Commit Tag:
> jena-3.9.0-rc1
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
>
> This vote will be open to at least
>
> Wednesday, 2018-10-03, 08: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:
>
> + does everything work on Linux?
> + does everything work on MS Windows?
> + does everything work on OS X?
> + 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?