Tasklist for release 0.2 of dbccp4i, database and visualiser
Release 0.2 of dbccp4i, database and visualiser
Description
Make a public version 0.2 release of dbccp4i which consists
of the handler, the various database schemas, and the visualiser.
Date due
?/?/2007
Depends on
Assigned to
Estimated time
List of tasks
Consolidation of the client APIs:
Review and update the names of the commands to make them
more consistent, specifically: references to "records" should
be standardised to "jobs", references to "databases" should
be standardised to "projects".
Bug #2347: Update DbRegister to remove the pid argument and
instead request the application name ("user-agent").
Provide API single commands for starting the handler,
connecting and registering (currently it's a two step
process)
Increase the default timeouts in the client APIs.
Bug #2122: Fix problem with default "empty" project
Review the documentation
Check installation documentation
Generation of client API documentation automatically from
docstrings and doc comments: finish off the script for
generating Tcl documentation, and generate the Python
documentation using "pydoc -w"
Bug #2389: Sort out issues with checking and installing the
dependencies
Potential risks and mitigation strategies
We must be very careful that the underlying code does not in any
way corrupt someone's existing database.
Put tests in place to verify correct behaviour
Include PJB's db_recover.tcl script (or equivalent) in dbccp4i
(now flagged for 0.2 release, see below)
Completed tasks
Testing under Windows (will be required for CCP4i integration)
Add a "changes" file (should record significant changes from previous
version that impact on users or developers, e.g. changes to the Python
client API which break older code that uses it, new features in the
viewer etc).
Review and standardise the return values from the commands (done
for Python client API).
Bug #2138: Implement new commands in the handler for handling files
associated with jobs