+1 Building OK for me from tag on
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0) Maven home: /opt/apache-maven-3.8.5 Java version: 17.0.7, vendor: Private Build, runtime: /usr/lib/jvm/java-17-openjdk-amd64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.15.0-76-generic", arch: "amd64", family: "unix" On Tue, 4 Jul 2023 at 21:24, Andy Seaborne <a...@apache.org> wrote: > Hi, > > Here is a vote on the release of Apache Jena 4.9.0. > This is the first release candidate. > > The deadline is > > Saturday, 8th July 2023 at 05:00 UTC > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > ==== Items in this release > > Arne Berdhardt > https://github.com/apache/jena/issues/1912 > New implementations of in-memory graphs with better storage and > performance. > > See the issue for performance details. > > See GraphMemFactory for access to these new graph implementations. > > Arne has also provided a performance analysis and improvements for the > existing default in-memory graphs together with a benchmarking framework > https://github.com/apache/jena/pull/1279 > > -- > > Switch from TriplyDB/(yasr,yasqe) to zazuko/(yasr,yasqe) > to pick up fixes. > Thank you Zazuko! > > -- > > SERVICE on/off control > https://github.com/apache/jena/pull/1906 > > Provide the ability to switch off all SERVICE processing completely. > Use > Code: arq:httpServiceAllowed > or http://jena.apache.org/ARQ#httpServiceAllowed=false > to disable. > > e.g. > fuseki-server --set arq:httpServiceAllowed=false .... > > -- > > Additional restrictions and control for SPARQL script functions > https://github.com/apache/jena/pull/1908 > > There is a new Jena context setting > http://jena.apache.org/ARQ#scriptAllowList > which is on the command line: > arq:scriptAllowList > and java constant > ARQ.symCustomFunctionScriptAllowList > > Its value is a comma separated list of function names. > "function1,function2" > Only the functions in this can be called from SPARQL. > > As in Jena 4.8.0, the Java system property "jena:scripting" must also be > set to "true" to enable script functions. > Website (when published): > https://jena.apache.org/documentation/query/javascript-functions > > -- > > Prepare for Jena5: > Deprecate JSON-LD 1.0 constants > Deprecate API calls that may be removed. > > -- > > Specific SPARQL 1.2 parser, tracking the RDF-star working group. > All features are also available in the default SPARQL parser. > > -- > Ryan Shaw(@rybesh) > new Turtle RDFFormat > https://github.com/apache/jena/issues/1924 > -- > Simon Bin (@SimonBin) > A fix for incorrect integer cast in scripting.NV > https://github.com/apache/jena/pull/1851 > -- > Alexander Ilin-Tomich (@ailintom) > Fix for SPARQL_Update verification and /HTTP PATCH > -- > Ryan Shaw (@rybesh) > Script fix for additional classpath elements > https://github.com/apache/jena/pull/1877 > -- > FusekiModules: > Issue: https://github.com/apache/jena/issues/1897 > > There is a change in that the interface for automatically loading > modules from the classpath has changed to FusekiAutoModule, The > interface FusekiModule is now the configuration lifecycle only. This is > to allow for programmatically set up a Fuskei server with Fuseki > modules, including custom one from the calling application. > > =================== > ==== 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-1059 > > 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/84aa91e095 > > Git Commit Hash: > 84aa91e095e20e0e3c7a55c9780f285ef8fb54bb > > Git Commit Tag: > jena-4.9.0 > > This vote will be open until at least > > Saturday, 8th July 2023 at 05:00 UTC > > If you expect to check the release but the time limit does not work > for you, please email within the schedule above. > > Thanks, > Andy > > 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? >
