Diff for "FeatureHighlights/MultiProjectBugs"

Not logged in - Log In / Register

Differences between revisions 4 and 5
Revision 4 as of 2007-03-24 19:59:25
Size: 2491
Editor: 81
Comment: link to next page
Revision 5 as of 2007-03-24 20:00:03
Size: 2506
Editor: 81
Comment:
Deletions are marked like this. Additions are marked like this.
Line 31: Line 31:
Now, look again at the table for [:https://launchpad.net/bugs/86103:Bug #86103]. Notice the assignee in the last column for the upstream Sun Java row, and the Debian row, look unusual? That takes us to the next step in our tour - [:BugWatches:watching bugs in other bug trackers]. Now, look again at the table for [:https://launchpad.net/bugs/86103:Bug #86103]. Notice the assignee in the last column for the upstream Sun Java row, and the Debian row, look unusual? That takes us to the next step in our tour - [:ReviewersGuide/BugWatches:watching bugs in other bug trackers].

Launchpad's bug tracker is unique in that it allows you to track the status of the same bug as it affects multiple different communities. This gives you a one-page overview of the work that is ongoing in all of those communities to engineer a fix to the problem.

Here's an example:

attachment:multiprojectbugs.png

Looking at this bug report, you can see that it is currently affecting at least 3 communities:

  • Java upstream
  • Debian
  • Ubuntu

In the case of Ubuntu, the bug has been recorded in two places - the sun-java5 and sun-java6 packages.

Each row in this table corresponds to a "place" where the bug has been detected, and so will need to be assessed and possibly fixed. At the highest level, a "place" is a community, like an upstream project or a distribution. But there are also some more specialised kinds of "places", each of which can have a row to itself, such as specific packages within a distribution, or specific major versions of an application, which can give you a fine level of granularity in tracking where this bug needs to be addressed.

It's quite possible to have a bug which needs fixing in many different places in the same project, for example this bug which affects 15 different packages in Ubuntu:

You can see that the issue has now been addressed in all packages. As the team is working on a bug like that, different packages will get fixed at different times, so the page provides a useful overview of the real work still required to consider the bug fixed. For example,

Sometimes, a bug is severe enough that you will want to go back and look at previous versions of the software to evaluate whether or not it should be fixed there, perhaps as a security fix or update to the stable and supported releases. Here's an example of a bug that was deemed important enough to go back and fix in Dapper and Edgy (two previous releases of Ubuntu):

Note that this bug needed fixing in two packages, in the current development release and two stable releases of the distribution, so there are a total of 6 rows in the table.

Now, look again at the table for [:https://launchpad.net/bugs/86103:Bug #86103]. Notice the assignee in the last column for the upstream Sun Java row, and the Debian row, look unusual? That takes us to the next step in our tour - [:ReviewersGuide/BugWatches:watching bugs in other bug trackers].

FeatureHighlights/MultiProjectBugs (last edited 2008-06-17 14:21:16 by localhost)