A few thing have arisen in the release checking.
Given that the new release will be better for existing users (it has
accumulated bug fixes; no regressions), I propose to fix the Fuseki
NOTICE issue and rebuild the release soon. I don't believe any users
will be have a less useful system and the bug fixes from the last,
incubator, release only improve the situation.
Andy
Details:
1/ Fuseki NOTICE is incomplete.
This needs to be fixed and means a new release cycle.
2/ TDB NodeTable transactional update isn't perfect.
NodeTableTrans needs rewriting - the design is flawed.
The problem is not new to this release.
Proposal: release as-is and try to get a new release
with a tested fix in quickly.
http://mail-archives.apache.org/mod_mbox/jena-dev/201206.mbox/%3C4FD4B8E4.8080709%40apache.org%3E
3/ ARQ tests under IBM JRE fail for duration
While it would be good to diagnose, it is not obviously
a jena bug.
http://mail-archives.apache.org/mod_mbox/jena-dev/201206.mbox/%3C4FD77FD0.1090508%40apache.org%3E
4/ Slow query
Fixed.
http://mail-archives.apache.org/mod_mbox/jena-dev/201206.mbox/%3COFEAC19AEA.103073B3-ON85257A17.007974BA-85257A17.007A4A57%40ca.ibm.com%3E
5/ TDB test in TS_Factory fails under windows
This is a bug in the test code only.
Fixed
6/ tdbloader3 reopens files.
In both mapped and direct modes, this causes a supposedly
fresh empty to contain junk.
Only know to affect tdblaoder3.
Proposal: release anyway
Needs a longer term investigation and fix.
