A bit bumpy!

The current state is that the codebase is now ready

There are three issues to do with the UI part of the build:

1. "Cypress failed to start"

"This may be due to a missing library or dependency."

It only happens on Jenkins and the build is OK on github actions and my local machine. I'm guessing it is a version dependency issue.

Starts at PR #2410

https://github.com/apache/jena/pull/2410/files


2. Sass deprecation warnings - these will need addressing but are not a problem. Starts at PR #2573 (dependabot)


3. In the unmerged PR 2574 / local build only
test:unit failure.
This is a blocker. The upgrade is of vite-test from 1.6.0 to 2.0.1 (OK - so major version jump)

https://github.com/apache/jena/pull/2574 from dependabot.
(this has been marked "draft")


Given all this, I think we should release without point 3 (PR 2574) which is only about the build and test.

    Andy

On 17/06/2024 14:54, Andy Seaborne wrote:
Jena 5.0.0 was released March 16th.
It's about time for Jena 5.1.0.

The main feature for 5.1.0 is the new ontapi module which includes a Java API for working with OWL2.

Issues: https://github.com/apache/jena/issues/2160
Code:   https://github.com/apache/jena/tree/main/jena-ontapi

Draft documentation:

https://github.com/apache/jena-site/blob/jena-next/source/documentation/ontology/__index.md

Issues closed in Jena 5.1.0 so far
   https://s.apache.org/jena-5.1.0-issues
45 issues

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

Beyond Jena 5.1.0:

There are several PRs in the backlog. A major one is the SPARQL extensions for lists and maps as literals. CDT = "Composite Datatype Literals". It is not quite ready to merge.

The website:
   https://github.com/awslabs/SPARQL-CDTs

Issue: https://github.com/apache/jena/issues/2518
PR:    https://github.com/apache/jena/pull/2501

which is a contribution from AWSlabs for an implementation of this.
This would be "experimental" meaning it is subject to change.  There should be no impact if the feature isn't used.

SPARQL and RDF features do need a way to get from solid ideaS to practical experience from real verification.

It has also been submitted as SPARQL change (SEP-0009) and there is also an implementation in Attean (Perl based)

   https://github.com/kasei/attean

I think it is better to not have two major items in a release so the suggestion is release Jena 5.1.0 and have a shorter (1-2 month) cycle for Jena 5.2.0 (if that works out).

== Current state

The Jenkins and github actions are all passing.

There is a backlog of PRs.

Reply via email to