diff options
author | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-03-21 17:54:46 +0000 |
---|---|---|
committer | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-03-21 17:54:46 +0000 |
commit | 829d097dc52b6a8f50297406affc67fbc08dccb7 (patch) | |
tree | 57c3f37ec17f630f5e65cb4c7a7f53dc0dd571bd | |
parent | 491338496eed1230b8ff5d853e2f7941a0c3706a (diff) |
web commit by http://getopenid.com/tpikonen
-rw-r--r-- | doc/todo/Better_bug_tracking_support.mdwn | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/todo/Better_bug_tracking_support.mdwn b/doc/todo/Better_bug_tracking_support.mdwn new file mode 100644 index 000000000..5bf8a95b2 --- /dev/null +++ b/doc/todo/Better_bug_tracking_support.mdwn @@ -0,0 +1,12 @@ +I see that ikiwiki has already some [[bugs]] stored on the wiki, but adding +better support for bug tracking would really make it a good project +management system for small projects. Storing the sourcecode, wiki, developer +blog and the issue tracker information under a same revision control +system really makes sense. At the moment the only part missing from ikiwiki +is the bug tracker plugin. + +The support would not need to be anything fancy, assignment of bug numbers +is perhaps the biggest thing missing when compared to a plain wiki page. +Integration with the revision control system a la [scmbug](http://www.mkgnu.net/?q=scmbug) +would really neat though, so that bug tracker commands like (closes: #nnn) could +be embedded to the source code repository commit messages.
\ No newline at end of file |