Distributed bug tracking

I think that nobody's worked out the "what this is all really about" model for bug tracking.
It seems to me that there should only be one set of bugs, rather than one per branch, because
the same bug can affect multiple branches, and be fixed by corresponding patches to those
branches. And it doesn't matter just whether a bug has been fixed; it matters what commit(s)
fix it, and whether the version you're looking at contains any of those commits. It's only a
relatively specialized case in which you want to know the bugs that nobody has found a fix
for.

I suspect that the website for access to the bug tracker should be relatively easy in the
distributed system; it's just another client in a system with a lot of clients. (For that
matter, I still want to see a website that lets you edit documentation in a project
wiki-style, generating a branch that you can look at before and after making commits and the
maintainer can pull to accept your changes.) On the other hand, it could be nice for users to
be able to report bugs when they don't have network access, either, especially for bugs that
cause or require a lack of connectivity, so an optional offline client is an advantage there,
too. And it would be really nice to be able to do one thing and see the status of all of the
bugs you care about, across different projects from different organizations.