The TDB included in 2.7.1 (0.9.1) has a bug that Fuseki triggers - the
Fuseki log ends up with a exception and stacktrace. It seems to be
harmless - the transaction does commit properly, and no threads in the
jetty server are lost. This is JENA-260.
It also messes up some reasonable uses of TDB begin-commit without the
recommended, but not compulsory, .end() call.
More importantly, it means users are still having to use snapshot builds
of Fuseki, which is far from ideal. I had hoped that users could pick
up versioned releases now; it helps in deployment environments and
reshipping.
A release of just TDB and Fuseki would be possible but it does not seem
to be less work and is more complicated to explain.
A fixed up version of Fuseki, with TDB 0.9.1 is also possible, but that
is a partial solution as some TDB usages need a workaround coding pattern.
I'm inclined to do another full release very soon, as time permits. I
realise this means a round of checking.
What do PMCers think? Do you have the energy to check another release?
(as it's a minimum of 3 +1's from the PMC that is needed for a release).
Andy
PS
I was going to suggest jumping all the version numbers to be the same
sometime - e.g. 2.10.0 as being higher than all the modules as less
confusing.
1/ Not sure we want to loose the ability to have single-module releases
just yet.
2/ This is a bug fix release - a jump in minor version number seems wrong.
