You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Rob Vesse <rv...@dotnetrdf.org> on 2022/02/01 16:12:12 UTC

Re: [VOTE] Apache Jena 4.4.0 RC2

+1 (binding)

Verified signatures, checksums and licenses plus verified building from source of OS X (M1 based)

LGTM,

Rob

On 30/01/2022, 16:33, "Andy Seaborne" <an...@apache.org> wrote:

    Hi,

    Here is a vote on the release of Apache Jena 4.4.0.
    This is the second proposed release candidate.

    == Changes RC1 -> RC2:

    JENA-2265 (Fuseki UI)
    Use window.location.pathname for the Fuseki URL, fix Vue publicPath

    JENA-2264 (jena-core)
    Improve Resource.getProperty(,lang). Include TestStandardModels.

    JENA-2262 (TestAdmin)
    Skip to the end of response streams

    ==

    The deadline is

          Wednesday, 2nd February 2022 at 19:00 UTC.

    Please vote to approve this release:

             [ ] +1 Approve the release
             [ ]  0 Don't care
             [ ] -1 Don't release, because ...


    ==== Items in this release

    ****

    The main item in this release is the updated Fuseki UI thanks to work by 
    Bruno.

    This can be tested by downloading 
    "org/apache/jena/apache-jena-fuseki/4.4.0/" zip or tar.gz from the 
    staging repository:
    https://repository.apache.org/content/repositories/orgapachejena-1050

    ****

    As general maintenance for the project:

    Apache log4j is at 2.17.1
    Apache Lucene: is updated to 8.10.1 -> 8.11.1
    Titanium JSON-LD updated 1.1.0 -> 1.2.0

    as well as all other dependences being checked for updates.

    To get valid javadoc, the build was done with Java17 cross-compiling to 
    <release>11</release>. A dry-run with java11 was done to check that no 
    Java17 library calls had crept in.

    The war file for Fuseki is no longer in the apache-jena-fuseki download. 
    Instead, it is available from the downloads page (links to be updated 
    when the release happens).

    Proposed:
    https://dist.apache.org/repos/dist/dev/jena/binaries/

    The Fuseki war file does not work in Tomcat10 due to the javax->jakarta 
    switchover. In theory, the Tomcat provided converter should work.
    https://tomcat.apache.org/download-migration.cgi


    This release includes the version of the TDB2 xloader used to load 16.6B 
    triples (WikiData all) into TDB2 and loading truthy (6B) on modest 
    hardware. Thanks to Marco, Lorenz and Øyvind for running Wikidata load 
    trails.

    Fuseki: serviceUpload is no longer added in a default configuration. 
    This is not SPARQL GSP. GSP (POST/PUT) does accept HTML file uploads as 
    well as POST/PUT by content-type.

    ==== 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-1050

    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/582e4082ef

    Git Commit Hash:
       582e4082ef53012527e686dd46cbeeb4b364f5fe

    Git Commit Tag:
       jena-4.4.0

    This vote will be open until at least

          Wednesday, 2nd February 2022 at 19:00 UTC.

    If you expect to check the release but the time limit does not work
    for you, please email within the schedule above.

    Thanks,

           Andy

    Checking:

    + are the GPG signatures fine?
    + are the checksums correct?
    + is there a source archive?
    + can the source archive 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?