How does bug tracker/version control integration work with typical git workflows?

Question

Here\'s are examples of git workflows:

• https://github.com/bard/sameplace/wiki/typical-git-workflow
• http://www.nabble.com/Git-workflow-overview-td163

Answer 1

Take a look to how Launchpad does this: tracking the state of the bug in different places.

Below I'll quote to Mark Shuttleworth:

Truly distributed bug tracking (where the bug list follows the code everywhere) is very exciting, and may be the long term solution. In the interim, you can address it with just tracking the state of the bug in a few different places. Canonical has been funding work on Bugzilla, Trac and other bug trackers to make it easier to talk to them programatically, so that we can keep Ubuntu developers up to date automatically.

We have a "centralised view of distributed bug status" in Launchpad, which helps us keep track of the status of an issue upstream, in Debian, or in other distros. For example, check out these bugs:

https://bugs.launchpad.net/moblin-applets/+bug/209870
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/214041
https://bugs.launchpad.net/ubuntu/+source/tuxmath/+bug/220319
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920
https://bugs.launchpad.net/ubuntu/+source/warsow/+bug/131582

In each case, you can see how the bug is linked to reports in other bug trackers, and then the status is updated automatically. As a small consequence, you can subscribe to any bug report on any bug tracker (of the supported types) via LP.

A centralised view isn't the ultimate solution, but it works for us right now and quite a few other projects - upstreams and distributions - are using it too.