Distributed bug tracking [LWN.net]

Distributed bug tracking

Posted May 14, 2008 17:29 UTC (Wed) by joey (subscriber, #328)
Parent article: Distributed bug tracking

The article touches on bug tracking systems being used for communication with users. I have
not been trying to develop a distributed BTS, but in working on a wiki backed by distributed
version control (ikwiki), I have kind of came at the same problem from the other end, starting
with a centralised documentation and communication medium (the wiki and blog), making it
decentralised, and then also using the wiki for (rather basic) bug tracking.

If that sounds interesting, here are a few links.

http://ikiwiki.info/tips/distributed_wikis/
http://ikiwiki.info/tips/integrated_issue_tracking_with_i...

(Log in to post comments)

Distributed bug tracking

Posted May 14, 2008 18:01 UTC (Wed) by JoeBuck (subscriber, #2330) [Link]

One possibility for maintaining a centralized point for public reports, while still distributing the bug database for day-to-day work, is just to treat the public repository as one of a number of peers. You can still update in both directions. Users wouldn't need their own git tree; they could use a bugzilla-style web interface to interact with one particular tree.

But developers wouldn't use the same approach. If Alice has fixed a bug in her own tree, she would want to update her local bug database as well (ideally by the same checkin, so that the mod to the bug's state is an atomic transaction that goes with the mod to the code). But since the bug still exists in developer Bob's tree, the bug database is naturally in a different state. Once developer trees are merged with the public tree, the database users see would be updated.