[X] +1 Approve the release Built from git tag on OS X with Java version 1.8.0_231 Deploys into Karaf 4.2.8 (OSGi) Works with Java Platform Module System (Java 11) Hashes and Signatures are all good LICENSE and NOTICE files are present
Thanks for preparing this release. Cheers, Aaron On Thu, 9 Jul 2020 at 14:49, Andy Seaborne <[email protected]> wrote: > Hi, > > Here is a vote on the release of Apache Jena 3.16.0 > This is the first proposed release candidate. > > The deadline is Monday, 13th July 2020 at 12:00 UTC > > ==== Dependency changes: > > JENA-1896 : Update shaded Google Guava to 29.0-jre > > ==== Changes for 3.16.0: > > https://s.apache.org/jena-3.16.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-1039 > > 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/c78176284b > > Git Commit Hash: > c78176284b89c00fff929cd18e15e2b704991887 > > Git Commit Tag: > jena-3.16.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 > > Monday, 13th July 2020 at 12: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? >
