[x ] +1 Approve the release

build worked, but had to shutdown a live local fuseki server at 3030 to
pass the tests.

have not tested the new build with my apps yet.

Thank You,
Marco



On Tue, Jan 27, 2026 at 4:18 PM Andy Seaborne <[email protected]> wrote:

> Hi,
>
> Here is a vote on the first release candidate for
> Apache Jena version 6.0.0
>
> ==== Release Vote
>
> This vote will be open until at least
>
>      Saturday, 31st January 2026 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-1071
>
> 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/1b767c8830
>
> Git Commit Hash:
>    1b767c8830220f55dcd760e94c0dadf597b6eea4
>
> Git Commit Tag:
>    jena-6.0.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.
>
> ==== Contributors
>
> @jduchateau
> @Aklakan
> @SimonBin
> @imsdu:
> @MathiasVDA
> @AtesComp
>
> ==== In this release
>
> Issues in this release:
>
>    https://s.apache.org/jena-6.0.0-issues
>
> ==== 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?
>
> ==== Current draft [ANN]
>
> The Apache Jena development community is pleased to
> announce the release of Apache Jena 6.0.0
>
> All issues for this release:
>    https://s.apache.org/jena-6.6.0-issues
>
> == Jena 6.0.0
>
> * Minimum Java version: Java 21
> * Reloading data into TDB2 is recommended
> * Reloading geospatial for the move to Kyro5
> * Lucene update to 10.* (this requires Java21+)
>
> * Retire jena-permissions
> * Retire the Fuseki WAR file, jena-fuseki-webapp, jena-fuseki-war
>
> * Code deprecation removal
> * Deprecation of TDB1 (but not removed)
>
> * Remove ARQ initial bindings
>
> * Switch to jena-iri3986 as the IRI parser; retire jena-iri
>
> == Contributions to Jena 6.0.0:
>
> Contributors:
>
> @jduchateau
> Updates to schemagen for keyword handling and
> Allow versionInfo to be a URI
>
> Aklakan
>    Improve query cancellation
>    Fix for AbstractIterhasJoin
>    RDFS improvements
>    GeoSpatql - upgrade to kryo5
>
> SimonBin:
> Ability to render GeoSPARQL results on a map in Fuseki-UI
> https://github.com/apache/jena/pull/3587
>
> @imsdu:
> Conversions to/from JSON object for Titanium JSON-LD
> https://github.com/apache/jena/pull/3702
>
> @MathiasVDA
> Correction for GEoSPARQL #3577
>
> @AtesComp
> Update Fuseki Edit view CodeMirror usage
>
> == Impact:
>
> The minimum version of Java is now Java21.
>
> = TDB2
>
> There is a fix for handling xsd:decimals.
> It is advisable to reload data if xsd:decimals have been used.
>
> = geosparql
>
> jena-geosparql: Jena 6 requires re-creation of spatial index files that
> were generated with earlier versions. The reason is a bump to the latest
> major version of the kryo serialization framework dependency.
>
> In general, it is recommended to back up existing databases including
> the spatial indexes prior to engaging in the migration process.
>
> The GeoSPARQL Assembler will automatically re-create all referenced
> absent spatial index files. Hence, moving or deleting existing spatial
> indexes is usually sufficient. The Fuseki SPARQL server runs spatial
> index creation of GeoSPARQL assemblers during server start. This process
> may take a while depending on the sizes of the involved datasets.
>
> == Lucene 10
>
> == modules removed:
> jena-iri, jena-fuseki-webapp, jena-fuseki-war, jena-permissions
>
> == Package org.apache.jena.tdb removed.
> Migrate to TDB2 or use package org.apache.jena.tdb1 (for now).
>
> == Obtaining Apache Jena 6.0.0
>
> * Via repo1.maven.org
>
> The main jars and their dependencies can used with:
>
>        <dependency>
>          <groupId>org.apache.jena</groupId>
>          <artifactId>apache-jena-libs</artifactId>
>          <type>pom</type>
>          <version>6.0.0</version>
>        </dependency>
>
> Full details of all maven artifacts are described at:
>
>      http://jena.apache.org/download/maven.html
>
> * As binary downloads
>
> Apache Jena libraries are available as a binary distribution of
> libraries. For details of a global mirror copy of Jena binaries please see:
>
>      https://jena.apache.org/download/
>
> * Source code for the release
>
> The signed source code of this release is available at:
>
>      https://downloads.apache.org/jena/source/
>
> and the signed source code for all Apache Jena releases is
> available at: https://archive.apache.org/dist/jena/
>
> == Contributing
>
> If you would like to help out, a good place to look is the list of
> unresolved github issues:
>
>      https://github.com/apache/jena/issues
>
> or review pull requests at
>
>      https://github.com/apache/jena/pulls
>
> or drop into the dev@ list.
>
> We use github pull requests and other ways for accepting code:
>
>       https://github.com/apache/jena/blob/master/CONTRIBUTING.md
>
>

-- 


---
Marco Neumann

Reply via email to