+1 (binding)

Verified signatures and hashes
Verified source distro builds on OS X
Verified LICENSE and NOTICE files

Rob

On 01/12/2020, 08:46, "Andy Seaborne" <[email protected]> wrote:

    ping

    Could we have a 3rd vote for this please?

    Sorry about the release being over the (US-holiday) weekend - RC1 won't 
    have been so bad but it was not to be.

         Andy

    On 25/11/2020 22:12, Andy Seaborne wrote:
    > Hi,
    > 
    > Here is a vote on the release of Apache Jena 3.17.0
    > This is the second proposed release candidate.
    > 
    > 
    > ---- Changes from RC1:
    > https://issues.apache.org/jira/browse/JENA-2003
    > 
    > Fix for filenames on MS Windows.
    > ----
    > 
    > The deadline is Sunday, 29 November at 08:00 UTC.
    > 
    > Please vote to approve this release:
    > 
    >          [ ] +1 Approve the release
    >          [ ]  0 Don't care
    >          [ ] -1 Don't release, because ...
    > 
    > ==== Major items in this release
    > 
    > JENA-1949: Dockerfile
    > and build instructions
    > https://jena.apache.org/documentation/fuseki2/fuseki-docker.html
    > 
    > JENA-1937: SHACL Compact Syntax writer
    > 
    > JENA-1982: SPARQL \U escapes in String and IRIs.
    > This is a change to ARQ extended SPARQL syntax.
    > 
    > JENA-1950: Use GraalVM for javascript if available.
    > The license means we do not ship GraalVM itself (and it is quite big).
    > 
    > JENA-1968:
    > Support Turtle output with relative URIs but no BASE declaration.
    > 
    > JENA-1974: G library
    > A library for working with Graphs
    > More :
    > 
https://lists.apache.org/thread.html/r973fd076583327b75e15bda798dce66d47f4f7cd8dbaa14c280f1fe3%40%3Cdev.jena.apache.org%3E
 
    > 
    > 
    > ==== Dependency changes:
    > 
    > ## Updates:
    > 
    > JENA-1959, JENA-1967: JSON-LD 0.12.5 -> 0.13.2 (umbreak)
    > JENA-1972: Jetty 9.4.26 -> 9.4.31
    > JENA-1973: Micrometer: 1.2.1 -> 1.5.5
    > JENA-1992: Update Log4j2 to 2.14.0
    > JENA-1993: Update Eclipse Jetty to 9.4.34
    > 
    > HttpClient to 4.5.13
    > commons-lang3 from 3.10 to 3.11
    > guava 29-jre to 30-jre
    > spatial4j from 0.6 to 0.7
    > airline.version from 2.1.1 to 2.8.0 (#839)
    > jts-core from 1.16.1 to 1.17.1 (#844)
    > ver.shiro from 1.5.1 to 1.7.0 (#840)
    > jackson-core from 2.10.1 to 2.11.3 (#847)
    > commons-codec 1.14 to 1.15
    > commons-io from 2.6 to 2.8.0
    > micrometer from 1.5.5 to 1.6.1
    > lucene 7.7.2 to 7.7,3
    > ElasticSearch from 6.8.6 to 6.8.9
    > 
    > ==== Changes for 3.17.0:
    > 
    > https://s.apache.org/jena-3.17.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-1041
    > 
    > 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/b7771659
    > 
    > Git Commit Hash:
    >    b7771659567e75cb6fcbc8666bad5250a78ac22e
    > 
    > Git Commit Tag:
    >    jena-3.17.0
    > 
    > This vote will be open until at least
    > 
    >      Sunday, 29 November at 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:
    > 
    > + 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?




Reply via email to