Sorry for the delay. I will checkout, build and then vote within the next hour.
Arne Andy Seaborne <a...@apache.org> schrieb am Mi., 17. Juli 2024, 13:15: > Could we have another PMC vote please? > > Andy > > On 12/07/2024 11:53, Andy Seaborne wrote: > > Hi, > > > > Here is a vote on the first release candidate for Apache Jena version > > 5.1.0. > > > > ==== Release Vote > > > > This vote will be open until at least > > > > Tuesday 16th July, 2024 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-1065 > > > > 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/8cf1104383 > > > > Git Commit Hash: > > 8cf11043838e312ab6ee82737de664e62d155cd1 > > > > Git Commit Tag: > > jena-5.1.0 > > > > If you expect to check the release but the time limit does not work > > for you, please email within the schedule above. > > > > ==== In this release > > > > Issues in this release: > > > > https://s.apache.org/jena-5.1.0-issues > > > > The major item for this release is the a new artifact jena-ontapi > > > > It has API support for working with OWL2 as well as other ontologies. It > > is the long-term replacement for org.apache.jena.ontology. > > > > https://github.com/apache/jena/issues/2160 > > > > This is a contribution from @sszuev > > > > == Also > > > > @karolina-telicent > > Prefixes Service > > New endpoint for Fuseki to give read and read-write access to the > > prefixes of a dataset enabling lookup and modification over HTTP. > > https://github.com/apache/jena/issues/2543 > > > > Micrometer - Prometheus upgrade > > See https://github.com/micrometer-metrics/micrometer/wiki/1.13- > > Migration-Guide > > https://github.com/apache/jena/pull/2480 > > > > Value space of rdf:XMLLiteral changed to be RDF 1.1/1.2 value semantics. > > Issue https://github.com/apache/jena/issues/2430 > > The value space in RDF 1.0 was different. > > > > @TelicentPaul - Paul Gallagher > > Migrating Base 64 operations from Apache Commons Codec to Util package. > > https://github.com/apache/jena/pull/2409 > > > > Balduin Landolt @BalduinLandolt > > javadoc fix for Literal.getString. > > https://github.com/apache/jena/pull/2251 > > > > ØyvindG @OyvindLGjesdal - > > https://github.com/apache/jena/pull/2121 > > text index fix for > > https://github.com/apache/jena/issues/2094 > > > > @wang3820 Tong Wang > > Fix tests due to assumptions on hashmap order > > https://github.com/apache/jena/pull/2098 > > > > @thomasjtaylor Thomas J. Taylor > > Fix for NodeValueFloat > > https://github.com/apache/jena/pull/2374 > > > > @Aklakan Claus Stadler > > "Incorrect JoinClassifier results with unbound values." > > https://github.com/apache/jena/issues/2412 > > > > @Aklakan Claus Stadler > > "QueryExec: abort before exec is ignored." > > https://github.com/apache/jena/issues/2394 > > > > @osi peter royal > > Track rule engine instances > > https://github.com/apache/jena/issues/2382 > > https://github.com/apache/jena/pull/2432 > > > > Normalization/Canonicalization of values > > Including RDFParserBuilder.canonicalValues > > This has been reworked to provide a consistent framework > > and also guarantee the same behavior between parsing > > and TDB2 handling of values. > > https://github.com/apache/jena/issues/2557 > > > > ------------------- > > > > 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? > >
