[x] +1 Approve this release Tested building on OS X using Java 11 and Java 8 using this command: `$ mvn clean install -Pdev`
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T14:33:14-04:00) Maven home: /usr/local/Cellar/maven/3.5.4/libexec Java version: 11.0.2, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk-11.0.2.jdk/Contents/Home Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.14.4", arch: "x86_64", family: "mac" and Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T14:33:14-04:00) Maven home: /usr/local/Cellar/maven/3.5.4/libexec Java version: 1.8.0_201, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_201.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.14.4", arch: "x86_64", family: "mac" OSGi provisioning works with manual testing in Karaf 4.2.3 and via automated pax-exam-based tests in a downstream project. Checksums are good Signatures are good SCM tags are good. Thanks! Aaron On Mon, Apr 29, 2019 at 2:27 PM Andy Seaborne <[email protected]> wrote: > Could we get a PMC vote please? > > So far > > +1 2 PMC, 1 community > > Andy > > On 24/04/2019 11:53, Andy Seaborne wrote: > > Hi, > > > > Here is a vote on a release of Apache Jena 3.11.0. > > This is the second proposed release candidate. > > > > The deadline for the vote is Saturday, 27th April at 17:00 UTC > > > > ==== Differences to RC1: > > > > * Fix for timezone test failure > > * Fix JENA-1705 for ParameterizedSpqralString > > > > ==== Release changes: > > > > 38 JIRA: > > > > https://s.apache.org/jena-3.11.0-jira > > > > == Changes of note: > > > > JENA-1691 : Metric services for Fuseki > > Sean Ryan > > > > JENA-1664, JENA-1665, JENA-1673 > > SDB improvements including performance of OPTIONAL, MINUS > > Graham Triggs > > > > JENA-1686 > > Set Dyadic#getL() and Dyadic#getR() return type to Graph > > Jan Martin Keil > > > > JENA-1674 : Fix mishandling negative xsd:floats in TDB2 > > > > JENA-1644 : ParameterizedSparqlString Empty List fix > > Greg Albiston > > > > Improvements to TDB1 and TDB2 handling bad I/O > > during transaction commit. > > > > == Updates > > > > commons compress 1.17 -> 1.18 > > libthrift 0.10.0 -> 0.12.0 > > jsonld-java 0.12.1 -> 0.12.3 > > Additionally, control the version of Jackson: 2.9.8 due to CVE's > > fileupload 1.3.3 -> 1.4 > > slf4j -> 1.7.25 -> 1.7.26 (CVE upgrade) > > > > new: > > io.micrometer: 1.1.3 > > and recursive dependencies: > > org.hdrhistogram:HdrHistogram:jar:2.1.9 (BSD-2-Clause) > > org.latencyutils:LatencyUtils:jar:2.0.3 (BSD-2-Clause) > > > > ==== 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-1030 > > > > 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/a13228f7 > > > > Git Commit Hash: > > a13228f7812a0d24f4242bfcae82ff2232a1ea58 > > > > Git Commit Tag: > > jena-3.11.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 > > > > Saturday, 27th April at 17: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? >
