We have a reasonable number of reports of SDB including used with MS SQL
Server, MySQL, PostgresQL and Oracle SQL 11g.
It tests with HSQLDB and I've now added Derby (latest version) to the
build setup and so that's in the standard build/test now.
There has been one issue reported - on windows, it's possible to get
parse warnings from the config file because the file base name isn't
converted to a safe form when there is a drive letter. It's a warning,
not an error. This will go away eventually.
Choices:
1/ release SDB 1.3.5 with a dependency on Jena 2.7.3
2/ release Jena 2.7.4, and update SDB 1.3.5 then release SDB 1.3.5
(there are internal changes that affect SDB 1.3.5 and make it
incompatible with Jena 2.7.4)
PMC review of SDB needs to cover the basics of legal and process
requirements. The community has done testing of codebase.
My concern with choice-2 is the amount of testing work it generates all
at the same time. I'm happy to be Release Manager for both.
Thoughts?
Andy
