On 13/10/2024 10:15, Marco Neumann wrote:
+1 builds for me. not tested with products yet
Some observations: The build took ~ 4min for a fresh repo. skipped javadoc.
all fine with Maven 3.9.6. jdk 21 oracle on linux. very smooth.
Thanks!
The disk size of Jena continues to grow substantially. Just a
cursory reading for Jena 4.10 gives me 1.1 GB on disk after the build. Jena
5.1.0 already goes up to 1.4GB and Jena 5.2.0 now is at 1.6GB. This while
my application use of Jena hasn't changed much in the last 2 years.
(stable) system just scaled up data size (linear) in production.
This is for the checked-out github code after a build? (I get about 1.6G
for that) or something else?
The size of .git will always be increasing - there is a lot of history,
including back to SVN days. It's 410M currently.
(If you have not run "git gc", that makes a small difference.)
Another growth factor is dependencies - the binary downloads for Jena
and jars/war file for Fuseki include dependencies so for some, several
copies. Strangely, such dependency artifacts don't seem to get smaller
over time :-)
Andy
Best,
Marco
On Sat, Oct 12, 2024 at 9:12 AM Andy Seaborne <a...@apache.org> wrote:
Hi,
Here is a vote on the first release candidate for
Apache Jena version 5.2.0.
==== Release Vote
This vote will be open until at least
Tuesday 15th October, 2024 at 12: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-1066
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/58e6cf3cd0
Git Commit Hash:
58e6cf3cd020fc3d95b7f29197bf1a0410c220db
Git Commit Tag:
jena-5.2.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.2.0-issues
The main feature for Jena 5.2.0 is an implementation of CDT "Composite
Datatype Literals", contributed by Olaf Hartig and others from AWSlabs.
This is "experimental" meaning it is subject to change. There should be
no impact if the feature is not used.
The release also includes:
* hash join improvements
* performance improvements for RDF/XML parsing, and for command startup.
* refinement of jena-ontapi
==== Contributions
CDT: Composite Datatype Literals
Olaf Hartig (@Hartig) et al.
https://github.com/apache/jena/issues/2518
https://github.com/w3c/sparql-dev/tree/main/SEP/SEP-0009
https://github.com/awslabs/SPARQL-CDTs
Hash join improvements.
@Aklakan Claus Stadler
https://github.com/apache/jena/issues/2404
https://github.com/apache/jena/pull/2405
GH-2580: Added parseCheck flags to query and update exec builders
https://github.com/apache/jena/issues/2580
This helps when dealing with vendor extensions to SPARQL.
@Aklakan Claus Stadler
GH-2578: Fix Quad.isTriple() handling in JenaTitanium
https://github.com/apache/jena/issues/2578
@Ostrzyciel Piotr Sowiński
-------------------
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?
