How are things looking for a 3.4.0 release?
I can be the release manager (on company time).
== Unification of version numbers:
Is it useful to have separate version numbers for Fuseki2 which is
2.6.0? Or should we jump Fuseki modules to 3.4.0?
This will become significant if/when any other component gets superseded
by a new component that evolves along side it (e.g. TDB2).
We might want to make a separate release of a component but we don't.
We can cope with occasional part-releases by simply moving the version
along - the overall combined release would just jump.
If we want to change, do it now or after the 3.4.0 release?
Andy
==== Jena 3.4.0:
** Features of note:
JENA-1326: Generic Lucene Analyzers (Code Ferret) Chris Tomlinson
http://jena.apache.org/documentation/query/text-query.html
JENA-1313: compare using a Collator when both literals are tagged with
same language
Basic Fuseki
JENA-1350: Use Fuseki embedded server for testing
JENA-1366: Fuseki server basic
Greg Albiston / JENA-1339
"Property Function signature for List subjects and List objects."
JENA-1340 - riot ignored "--base", now it doesn't
JENA-1074: Union graph.
JENA-1346: HttpOp: switch to a pooling HttpClient as the default
JENA-1360: Support the "q" (quote) flag on regex.
** dependency changes
No license changes.
commonscsv 1.3 -> 1.4
dexxcollection 0.6 -> 0.7
httpclient 4.5.2 -> 4.5.3
commons-cli 1.3->1.4
slf4j 1.7.21 -> 1.7.25
JENA-1341:
Upgrade Jetty to 9.4.5.v20170502 (Fuseki2)
Upgrade Jetty to 8.1.22.v20160922 (Fuseki1)
