blob: 577da2dc31e8a58d25c598271a08b46ad503bf91 (
plain)
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
would really neat though, so that bug tracker commands like (closes: #nnn) could
be embedded to the source code repository commit messages.
A while back I posted some thoughts in my blog about
using a wiki for issue tracking.
Google's BTS also has some interesting developments along the lines of
free-form search-based bug tracking, a style that seems a better fit to
wikis than the traditional rigid data of a BTS.
I sorta take your point about bug numbers. It can be a pain to refer to
'using_a_wiki_for_issue_tracking' as a bug name in a place like a
changelog.
OTOH, I don't see a need for specially formatted commit messages to be
used to close bugs. Instead, if your BTS is kept in an ikiwiki wiki in
an RCS along with your project, you can do like I do here, and just edit a
bug's page, tag it done , and commit that along with the bug fix.
--[[Joey]]
|