Distributed Bugtrackers

The idea is basically that if you use DVCS, you keep your bug database in the repository, and move it around like the rest of your code. It means you don't need a separate store for your bugs, you can record a fix along with committing the fix, you can see the state of the bug database and corresponding codebase at any point in time, and the database can be used offline. It also means that QA will need commit access to the repository, checkouts of old revisions won't include any mention of bugs they contain which were only reported later, comments on bugs don't propagate any faster than code, and will be lost in closed branches, and there's no idea of a canonical single bug state (although if you have a golden master repository somewhere, there sort of is). Anyway, interesting idea.