+1 Build passing on:
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T05:41:47+13:00) Maven home: /opt/maven Java version: 1.8.0_111, vendor: Oracle Corporation Java home: /usr/lib/jvm/java-8-oracle/jre Default locale: en_NZ, platform encoding: UTF-8 OS name: "linux", version: "4.4.0-45-generic", arch: "amd64", family: "unix" >+ does everything work on Linux? OK >+ are the GPG signatures fine? >+ are the checksums correct? Key looks good, imported locally. Checked artefacts with gpg --verify, everything looks OK. >+ does the NOTICE file contain all necessary attributions? Looks OK to me. >+ does the tag/commit in the SCM contain reproducible sources? Yup, built from git commit Cheers Bruno >________________________________ > From: Andy Seaborne <[email protected]> >To: [email protected] >Sent: Saturday, 5 November 2016 11:43 AM >Subject: [VOTE] Release Apache jena 3.1.1 (2nd) > > > >Hi, > >Here is a vote on a release of Jena 3.1.1 >(with Fuseki 2.4.1 and Fuseki 1.4.1). > >This is the second proposed candidate for this release. > >** My signing key has changed - to verify, use the key in ** >** https://svn.apache.org/repos/asf/jena/dist/KEYS ** >** for [email protected]. ** > >* Dependency changes: > >New module: > jena-fuseki2/jena-fuseki-embedded > >Updates: > com.github.jsonld-java:jsonld-java 0.7.0 -> 0.8.3 > > org.apache.httpcomponents:httpClient 4.2.6 -> 4.5.2 > org.apache.httpcomponents:httpCache 4.2.6 -> 4.5.2 > org.apache.httpcomponents:httpCore 4.2.5 -> 4.4.4 > > com.jayway.awaitility:awaitility 1.6.4 -> 1.7.0 > com.spatial4j:spatial4j 0.4.1 -> 0.5 > org.slf4j:* 1.7.20 -> 1.7.21 > commons-codec:commons-codec 1.9 -> 1.10 > org.apache.commons:commons-collections4 4.0 -> 4.1 > org.apache.commons:commons-csv 1.0 -> 1.3 > org.apache.commons:commons-lang3 3.3.2 -> 3.4 > org.apache.thrift:libthrift 0.9.2 -> 0.9.3 > org.apache.mrunit:mrunit 1.0.0 -> 1.1.0 > com.github.rvesse:airline 2.1.0 -> 2.1.1 > > >Key features of the release: > >* Improve JSON-LD output > JENA-1208 - François-Paul Servant >http://jena.staging.apache.org/documentation/io/rdf-output.html#json-ld > >* Completed F&O XPath3 functions > JENA-508 - Alessandro Seganti > >* ComplexPhraseQueryParser > JENA-1180 - Andrew Dolby > >* Additional vocabularies (DCAT, VoID, ROV, ORG) > JENA-1206 - Bart Hanssens > >* Improvement to the Fuseki service script for RHEL/Centos 6. > JENA-1219 - Dan Pritts > >* ORDER BY now cancelable. > >* Txn : a highlevel API for working with transactions >http://jena.staging.apache.org/documentation/txn/txn.html > >* Embedded Fuseki >http://jena.staging.apache.org/documentation/fuseki2/fuseki-embedded.html > >* Property path speed ups (JENA-1195) > >* Upgrade to Apache HttpClient v4.3 API > => auth changes cause API changes. > > >Everyone, not just committers, is invited to test and vote. > >Staging repository: >https://repository.apache.org/content/repositories/orgapachejena-1015/ > >Proposed dist/ area: > https://dist.apache.org/repos/dist/dev/jena/ > >Keys: > https://svn.apache.org/repos/asf/jena/dist/KEYS > ** NB signing key has changed. > > >Git commit (browser URL): > https://git-wip-us.apache.org/repos/asf/jena/commit/f7b3c416 > >Git Commit Hash: > f7b3c416328bba4b8044e4ea8ad80e09ac51d720 > >Git Commit Tag: > jena-3.1.1-rc2 > >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 > > Monday, 7 Nov 2016, 23:59 UTC > >If you expect to check the release but the 72 hour 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? >+ 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? > > >
