| |||||||||||||
|
| |||||||||||||
Similar approach using ikiwikiSimilar approach using ikiwikiPosted Apr 26, 2007 20:31 UTC (Thu) by dmarti (subscriber, #11625)Parent article: DisTract - the Distributed Bug Tracker You can also keep track of bugs within your project RCS using Ikiwiki issue tracking. This approach looks especially good when you can set things up so that one commit can do three things: fixes the code, edits the documentation, and changes the status of a bug. Revert the code change and the docs and BTS change too.
(Log in to post comments)
Similar approach using ikiwiki Posted Apr 26, 2007 22:45 UTC (Thu) by pimlott (guest, #1535) [Link] I've given considerable thought to this model (versioning bugs along with the code) and rejected it. At least, I don't think it works well when
Bug reports are really "outside of time" with respect to code revisions: When looking at a version of the code repository (eg, the latest release), you really want to see all future information about bugs in that version.
On the other hand, it has the merit of simple implementation, so if people want to try it out and see how it works in practice, go for it!
Similar approach using ikiwiki Posted Apr 26, 2007 22:47 UTC (Thu) by pimlott (guest, #1535) [Link] Bah, that was an accidental post. I had meant not to post at all, because 1) what I had to say is complicated and would take a while to write and 2) I'm not as sure about it as I was when I thought about it before. :-)
|
|
||||||||||||