Bug tracking in the source repository

time to read 1 min | 178 words

I've had a good experiance in putting all the bugs in a system in a TiddlyWiki and putting that in the source repository. It's a nice system, but I wonder how it would scale. Assume that there is more than one developer involved, you will start to get conflicts almost immediately, the wiki is a single file, and resolving those conflicts is going to be happening at each check in.

On solution is to use a common folder with a file for each issue, but I'm not sure that I like that approach. It's also fragile if two developers edit the same bug. One solution I can see if to handle this in the software itself. Have a single file and expect conflicts, and then solve them yourself.

Why not use an online bug tracking system? Simple, I'm often in disconnected mode, and it's incredibly useful to be able to still work on the bug tracking when I'm offline. A third option is to have a software that can work in disconnected mode, and then handle the possible conflicts when you merge back to the main database.