I see your point about new classes added to the public API needing
javadoc, that seems reasonable.
By release, do you mean a Derby release or an ICLA? Assuming the
latter, I thought the ICLA issue had been cleared up. The ICLA has been
on file for some time, search for Stephen Fitch in
http://people.apache.org/~jim/committers.html.
David
Daniel John Debrunner (JIRA) wrote:
[ http://issues.apache.org/jira/browse/DERBY-646?page=comments#action_12426372 ]
Daniel John Debrunner commented on DERBY-646:
---------------------------------------------
Probably no new tests are required but some changes to ensure the feature is
tested, such as the ability to run tests with this configuration and suites
that use the configuration.
As in my earlier comments, I don't think this patch is ready to be committed,
my concern is the new classes added to the publi api, with no coments or
documentation as to what they are for.
Why would a release not be needed?
In-memory backend storage support
---------------------------------
Key: DERBY-646
URL: http://issues.apache.org/jira/browse/DERBY-646
Project: Derby
Issue Type: New Feature
Components: Store
Environment: All
Reporter: Stephen Fitch
Assigned To: Stephen Fitch
Attachments: svn.diff
To allow creation and modification of databases in-memory without requiring
disk access or space to store the database.
