It may be useful to check what needs to be done to get Jena 2.10.0 out
with some time allocated to user-driven testing before release. i
though doing that for SDB was quite successful.
2.10 contains many small changes which are either internal or of minimal
external affect. The largest external effect is probably rectification
changes. But there are a lot of changes and not all applications stick
to external APIs. There is a chance some that something inconvenient
has changed which can be smoothed over to help users.
So I suggest a "release candidate" cycle like we did for SDB - not a
formally release (with all it's vote and maven distribution upload) but
a statement that the SNAPSHOT build is ready for pre-release testing.
Any unnecessary friction points just get fixed in the dev build cycle;
anything significant comes to dev@ for discussion.
Things to do for 2.10.0:
1/ It would be good to include the reorganised and refactored tests
(JENA-370)
Claude - I tried to apply the patch but either I didn't understand the
intent or it is missing some classes (moved? and only the old version
removed, without a new version in the patch?)
2/ Events
Currently, the model-level events are old-style, events for each of the
ways to add/delete statements (list, iterator, model, single ...).
This is factored into a single global GraphUtil.OldStyle. But many
tests are likely to change so I was leaving this until after JENA-370 as
the codebase and the patch are already from different generations already.
3/ Steaming support (partial)
Stephen - is there anything we should be aiming for in this release to
move things along?
4/ Anything else anyone wants to get in?
Andy
