diff options
| author | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-03-22 15:47:59 +0000 |
|---|---|---|
| committer | joey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071> | 2007-03-22 15:47:59 +0000 |
| commit | e490e06841014073be068380df8169f3c02f3234 (patch) | |
| tree | 728d7c9b7ebd307eef2d955aaae7345e06027a56 | |
| parent | 5a6a93544f84305796fbc593226d3427e5abc90f (diff) | |
| download | ikiwiki-e490e06841014073be068380df8169f3c02f3234.tar ikiwiki-e490e06841014073be068380df8169f3c02f3234.tar.gz | |
web commit by http://getopenid.com/tpikonen
| -rw-r--r-- | doc/todo/Better_bug_tracking_support.mdwn | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/todo/Better_bug_tracking_support.mdwn b/doc/todo/Better_bug_tracking_support.mdwn index 577da2dc3..2b281d4b1 100644 --- a/doc/todo/Better_bug_tracking_support.mdwn +++ b/doc/todo/Better_bug_tracking_support.mdwn @@ -27,3 +27,22 @@ be embedded to the source code repository commit messages. > bug's page, tag it `done`, and commit that along with the bug fix. > > --[[Joey]] + +>> I think a little bit more structure than in a normal wiki would be +>> good to have for bug tracking. Bug numbers, automatic timestamps on comments +>> and maybe an email interface would be nice. The resulting page may not +>> look like a wikipage anymore, but rather something like the Debian +>> BTS web-interface, but it would still benefit from wikilinks to the +>> documentation in the wiki etc. +>> +>> About the commit message interface: I was thinking about a project +>> architecture where the code is kept in a separate revision control +>> system branch than the metadata (blog, wiki, BTS). This would IMHO +>> be a cleaner solution for distributing the source and making releases +>> etc. For this kind of setup, having the BTS scan the messages of the +>> source branch (by a commit-hook for example) would be useful. +>> +>> By Google BTS, do you mean the issue tracker in the Google code +>> project hosting? +>> +>> --Teemu
\ No newline at end of file |