I'd like to go ahead with the current release candidate now that a
likely cause has been found.
It is not an application runtime issue.
We know how to workaround it if anyone else encounters it. It's been in
the code base for several releases with no reports.
If that's OK - could I get another PMC vote please?
Issue to fix and also harden the code:
https://github.com/apache/jena/issues/3150
Andy
On 14/04/2025 16:49, Andy Seaborne wrote:
Hi,
Here is a vote on the first release candidate for
Apache Jena version 5.4.0.
==== Release Vote
This vote will be open until at least
Thursday 18th April 2025 at 23:59 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-1068
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/1af1a75db6
Git Commit Hash:
1af1a75db645cf745ee418225b99651a60b2434a
Git Commit Tag:
jena-5.4.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.4.0-issues
== RDF 1.2
Jena 5.4.0 introduces a preview of RDF 1.2 support. This work is
*experimental* and subject to change. It will track the work of the
RDF-Star Working Group.
Users of the work of the RDF-star Community Group will be impacted.
This is an opportunity to provide feedback on the work of the W3C
working group.
For more information, see
https://lists.apache.org/thread/5k8cr91h1okhh75g0gx71dyhwt0fobfc
== New artifact
Jena 5.4.0 introduces a new module jena-langtag for language tag parsing
in compliance with RFC 5646. Language tag validation is strengthened.
When parsing, language tag violations are still treated as warnings.
==== 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 contributed improvement to the jena-text build for
java21 and also in fixing the unstable build on github actions.
@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
-------------------
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?
