The vote passes with 3 +1 votes from Bruno, Aaron and Andy, together
with a community vote from Marco.
I'll start pushing the release out.
Note - this is without the OSGi binary artifacts due to problems with
the new dependencies for JSON-LD 1.1 support discovered during the
release process.
Andy
On 12/09/2021 13:24, Andy Seaborne wrote:
Hi,
Here is a vote on the release of Apache Jena 4.2.0.
This is the first proposed release candidate.
The deadline is Wednesday, 15 September June 2021 at 15:00 UTC.
Please vote to approve this release:
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
==== Major items in this release
JENA-2112: ShEx engine
https://jena.apache.org/documentation/shex/
JENA-1948: JSON-LD 1.1 Reader
JSON-LD 1.1 uses the Titanium system.
https://github.com/filip26/titanium-json-ld
jsonld-java is still there for JSON-LD 1.0.
In this release, JSON-LD 1.0 is the default for reading JSON-LD.
This adds new jars into the convenience binaries which
are Eclipse Public License 2.0.
JENA-2114: SHACL: Provide SPARQL targets
JENA-2123: Upgrade to Jetty10
Contributions:
Claus Sadler:
JENA-2132 : RDF-star fix
JENA-2154 : Custom SERVICE executors
Experimental: Using SERVICE for extension functionality.
Erich Bremer:
JENA-2159: schema.org vocabulary
JENA-2155: Add Web Access Control vocabulary
Jan Martin Keil:
JENA-2142: Extend DatatypeFormatException
==== Changes for 4.2.0
See for JIRA tickets:
https://s.apache.org/jena-4.2.0-jira
==== Release Vote
Everyone, not just committers, is invited to test and vote.
Please download and test the proposed release.
Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-1044
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/d346b35f49 @@
Git Commit Hash:
d346b35f49e60220f89b3a11c8ed36be778d37a5
Git Commit Tag:
jena-4.2.0
This vote will be open until at least
Wednesday, 15 September June 2021 at 15:00 UTC
If you expect to check the release but the time limit does not work
for you, please email within the schedule above with an expected time
and we can extend the vote period.
Thanks,
Andy
Checking needed:
+ 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?
