+1 (Binding)

Inspected and verified on OS X

Rob

From: Andy Seaborne <a...@apache.org>
Date: Thursday, 16 January 2025 at 11:26
To: dev@jena.apache.org <dev@jena.apache.org>
Subject: [VOTE] Apache Jena 5.3.0
Hi,

Here is a vote on the first release candidate for
Apache Jena version 5.3.0.

==== Release Vote

This vote will be open until at least

     Tuesday 21th January 2025 at 08:00 UTC

Please vote to approve this release:

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

Everyone, not just committers, is invited to test and vote.
Please download and test the proposed release. See the checklist below.

Staging repository:
   https://repository.apache.org/content/repositories/orgapachejena-1067

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/2303067d36

Git Commit Hash:
   2303067d362d6d69e52da0111ec6f1f23a252c8e

Git Commit Tag:
   jena-5.3.0

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

==== In this release

Issues in this release:

   https://s.apache.org/jena-5.3.0-issues

Jena 5.3.0 has changes in the structure of the Fuseki server, a new IRI
provider, together with a lot of clearup and simplification of Jena's
use of Apache Xerces.

==== Contributions

@Ostrzyciel has contributed several test cases for initialization
and also cleaning up of Jena's use of Apache Xerces-derived code for RDF
datatypes:

@OyvindLGjesdal has contrinbuted imporvement to the jena-text build for
java21->

@Aklakan has contributed support for timeouts in SPARQL Updates,
provided fixes for closing execution iterators, OpAsQuery, and for
NodeFmtLib.

Committers with PRs: rvesse, sszuev, kinow, arne-bdt, afs
and not forgetting @dependabot

==== Fuseki

The artifact jena-fuseki-main, which was the UI-less embedded simple
server, now has equivalent functionality, including UI, to the
Fuseki/webapp packaging.

The artifact jena-fuseki-server packages jena-fuseki-main with
dependencies and UI files into a single jar.

It should be a drop-in replacement. There is no functionality added or
removed; it is a better base for future development.

Fuseki/webapp packaging for the WAR file which will continue to be
produced but may not get all future Fuseki development features.

-------------------

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?

Reply via email to