[x] +1 Approve the release mvn verify install - completed successfully on MacOS 10.14.6 with Java 1.8.0_162-b12.
Simple testing of fuseki-server ran without issue. Regards, Chris > On Oct 10, 2019, at 4:01 PM, Andy Seaborne <[email protected]> wrote: > > Could we get a third vote for this release, please? > > Adam? > > Andy > > On 06/10/2019 22:46, Andy Seaborne wrote: >> Hi, >> Here is a vote on the release of Apache Jena 3.13.1. >> This is the first proposed release candidate. >> ==== Changes: >> https://s.apache.org/jena-3.13.1-jira >> which is these 4 tickets: >> JENA-1767 >> Enable clear out of all TDB1 location-related state. >> JENA-1766 >> Fuseki Web interface endpoint mechanism not working >> JENA-1764 >> Fix missing and duplicate Automatic-Module-Name metadata >> JENA-1749 >> Support lucene field names in jena-text queries >> ==== 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-1034 >> 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/987b59e240 >> Git Commit Hash: >> 987b59e2405f2e5853f5550219b932a5fb7bb86c >> Git Commit Tag: >> jena-3.13.1 >> 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 >> Thursday, 10th October 2019 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?
