urosm
/
ikiwiki
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add thoughts on bug numbers

master
http://www.cse.unsw.edu.au/~willu/ 2008-08-09 07:27:48 -04:00 committed by Joey Hess
parent 907f717bce
commit 146c3b98cd
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/todo/Better_bug_tracking_support.mdwn
View File

@ -20,7 +20,17 @@ be embedded to the source code repository commit messages.
> I sorta take your point about bug numbers. It can be a pain to refer to > 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 > 'using_a_wiki_for_issue_tracking' as a bug name in a place like a
> changelog. > changelog.
>
>> Would a modified [[plugins/inline]] plugin that allowed new pages, but without a title field, be ok?
>> When you hit the edit button it just chooses a new number and makes a page with that
>> name.
>> The only issue I can see with this is if you're using a distributed wiki for
>> distributed bug tracking. In that case you're going to have to make sure that you
>> don't get conflicting bug ids.
>> Maybe there should be two options - consecutive numbering, and uuid numbering
>> which uses a random (128 bit, base64 encoded = 22 chars) name. -- [[Will]]
> OTOH, I don't see a need for specially formatted commit messages to be > 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 > 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 > an RCS along with your project, you can do like I do here, and just edit a