Difference between revisions of "CoCoALib:TaskTable"
(→Dortmund: add "update the documentation") |
(→Dortmund: add matlab toolbox & python bindings) |
||
Line 32: | Line 32: | ||
===Dortmund=== | ===Dortmund=== | ||
− | + | * MatLabToolBox | |
+ | ** who: [http://cocoa.mathematik.uni-dortmund.de/wiki/User:Mabshoff Abshoff] | ||
+ | ** status: 2b | ||
+ | ** progress: active | ||
+ | * Python bindings | ||
+ | ** who: [http://cocoa.mathematik.uni-dortmund.de/wiki/User:Mabshoff Abshoff] | ||
+ | ** status: 1 | ||
+ | ** progress: active | ||
=Development stages= | =Development stages= |
Revision as of 20:41, 19 December 2006
CoCoAList Task Table
This page summarises the work going on in CoCoALib. The tasks for Genova are still hosted at dima, it is currently uncertains if and when those tasks will be transfered to the wiki. The sections Development and Status have been ripped shamelessly from the task table in Genova.
Always
Genova
See Task Page in Genova.
Dortmund
- Valgrinding, purifying & benchmarking
- Improve the documentation
Release 1.0
Genova
See Task Page in Genova.
Dortmund
FIXME
Release 0.98
Genova
See Task Page in Genova.
Dortmund
- MatLabToolBox
- who: Abshoff
- status: 2b
- progress: active
- Python bindings
- who: Abshoff
- status: 1
- progress: active
Development stages
To describe the progress of each subtask (contributing C++ code to the library), I suggest using the following scheme for identifying what has been done, and what is still to be done. The intention is that normally all lower numbered stages be completed before progressing to the higher numbered stages. For other types of task, the task description should give an indication of progress.
- (1) subproject start (incl specification of subproject)
- (2a) abstract algm design, choice of data-structures, etc.
- (2b) initial test set
- (2c) early prototype, mostly works, maybe some bugs
- (3a) late prototype, fully working, almost no bugs
- (3b) comprehensive test cases
- (4a) final C++ version (incl. relevant build commands)
- (4b) maybe extra tests
- (4c) portability and quality control issues
- (4d) documentation
- (5a)-(5d) independent verification of stages (4a)-(4d)
Status
For each task, the table indicates the current "status". Here are the main choices for the status:
- active being worked on currently
- inactive not being worked on currently (but work should begin fairly soon)
- waiting progress suspended until some other task has progressed enough
- resting temporarily suspended (e.g. holiday)
- other explanation of actual status is with task description