Reflect code progress in TODO file, add plans

1 files changed, 24 insertions, 19 deletions

diff --git a/TODO b/TODO
index dd544bc..e4cdb68 100644
--- a/TODO
+++ b/TODO
@@ -2,56 +2,60 @@
 Release Plans:
 ========================================================================
 
-nbb-0.1
+
+nbb-0.1 (done)
  * Start new git repo (get rid of ndim-git-utils history).
  * Clean up git tags.
 
-nbb-0.5
- * Write docs: man page equivalent, README, NEWS, HACKING.
 
-nbb-1.0
- * Make public release.
+nbb-0.2
+ * Make sure the "if cmp ... mv .. rm" in make rules are correct and useful,
+   and the cmp is silent.
+ * Useful logging infrastructure, and --debug etc user interface.
+ * Store config in ${srcdir}/.nbb.conf instead of 'git config'.
+   More portable. bzr does not have a config interface, for example.
 
-========================================================================
-TODO (some time):
-========================================================================
 
- * Separate generic plugin/command/etc. stuff and nbb specific
-   code into separate modules.
+nbb-0.9 or earlier
  * Switch plugins.Foo.validate() functions to different protocol:
    Either return or raise an exception.
  * Use different exceptions for plugins signalling detection failure
    to detect() and detect() to signal "no matching plugin detected"
    to detect()'s caller.
- * BS support: cmake, scons, ...
+ * BS support: cmake, scons, python setuptools ...
  * VCS support: SVN, darcs, hg, ...
  * Out-of-source builds for systems which require in-source-tree builds:
    "cp -rl foo.src foo.build"?
  * General removal of redundancy in Python code.
- * Useful logging infrastructure, and --debug etc user interface.
- * Make sure the "if cmp ... mv .. rm" in make rules are correct and useful.
  * More declarative syntax elements in the Python code.
  * Use declarations for command line parsing, and help text generation.
    Use optparse stuff for both global params and extra optparse stuff
    for each command?
  * Add global --nick or similar option to determine the branch
    name to use for composing the pathes.
- * Store config in ${srcdir}/.nbb.conf instead of 'git config'?
-   More portable. bzr does not have a config interface, for example.
  * Model different "stages" of e.g. automake builds as distinct objects,
    including proper dependency detectors, and stuff? OK, we're not going
    to duplicate scons here.
- * Bash syntax completion
- * Man page or something similar. Generate from help texts?
+ * Bash syntax completion, ideally autogenerated
+ * Docs:
+    * Write docs: README, NEWS, HACKING.
+    * Man page or something similar. Generate from help texts?
  * Command aliases:
      make -> build    (for automake, or similar mapping)
- * Make automake's make depend on configure etc.
+ * Make automake's "nbb make" depend on configure etc.
  * Test sh command like run command.
 
+
+nbb-1.0
+ * Make public release.
+
+
 ========================================================================
-DONE:
+DONE (some time in the past)
 ========================================================================
 
+ * Separate generic plugin/command/etc. stuff and nbb specific
+   code into separate modules.
  * Implement sh and run commands.
  * supports execution of user commands in source, build, install dirs
  * Do not move command objects to plugin detection framework (bad idea!)
@@ -80,6 +84,7 @@ DONE:
    gained with git-amb, especially the command interdependencies.
    (Nothing to do! :)
 
+
 ========================================================================
 End of TODO file.
 ========================================================================