We have:
* in-memory transactional dataset from Adam is in the codebase
(details on progress below)
* configurable lucene analyzers
* general maintenance.
* Improved start-up and configuration to wire the jars together.
Shall we do a release? This fits our 3-6 months cycle.
As we know, getting people to try unreleased builds has limited effect
(generally for point-bug fixes, less so for new features) so my
suggestion is to release soon as v3.0.1 and describe the in-memory
transactional dataset as "RC". It's not fully integrated (test: Fuseki
is not using it yet) and getting that done and stable isn't an instant
task to do. At the same time, a release will let people try it.
So we expose the in-memory transactional dataset at the API level now,
introduce the deprecations so people can see what's coming, and
complete/stabilize the integration to make a v3.1.0 in a few months time.
Andy
Progress on the in-memory transactional dataset
https://pony-poc.apache.org/thread.html/Zj36f2pbaszgdnj
If you want to try it, then DatasetFactory.createTxnMem() is the entry
point.
--------------------------------------------------------
Outstanding tasks:
* Dependency version management in jena-parent.
Done
* more testing [done], and the organisation of the tests
Test done, organisation of tests is partially done. There is a wider
tasks to organise the dataset tests we have into some sort of order but
that's non-blocking.
* documentation
* code cleaning for deprecation of DatasetFactory.createMem
* Same migration for DatasetGraphFactory.createMem
* Fuseki integration
--------------------------------------------------------
