OT: Distributed bug tracking?

[Micah Elliott]

On 2008-01-04 Dmitriy Morozov wrote:

> I think the case where Mercurial is used by a single (or maybe
> a couple of) developers for a project for which they need to
> somehow keep track of (read: organize nicely) the issues
> involved, and perhaps save an occasional bug report from an
> occasional user, is common enough to where it explains the
> interest that this thread has raised.

I've enjoyed following this thread and all the great ideas that
have been brought up.  I too really like the notion of a bug
tracker integrated into the code base.  I tried to get something
related to this working in the form of Codetags
(http://www.python.org/dev/peps/pep-0350/), but my implementation
never got further than personal use.  I suppose the idea of
separate dirs per bug is cleaner than the codetag approach, but
just thought I'd add another perspective.

-- 
                          _ _     ___
                          |V|icah |- lliott
                          " "     """
mde at MicahElliott.com            <><             http://MicahElliott.com
PGP: 0x7C07CBF0          ICQ: 369060435      Linux/Ubuntu: 417195/12440
HackerKey: v4sw6YUPCJhw5ln5pr7OPck2ma9u8Lw3m5l6Ui2e7t3b8LDMOen6a3XsMRr5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://selenic.com/pipermail/mercurial/attachments/20080104/075c0dc9/attachment.pgp