Diff for "FeatureHighlights/MultiProjectBugs"

Not logged in - Log In / Register

Differences between revisions 8 and 9
Revision 8 as of 2007-03-26 16:17:36
Size: 2537
Editor: 62-30-68-94
Comment: Removed an orphaned "For example,"
Revision 9 as of 2007-03-26 17:06:39
Size: 2503
Editor: 62-30-68-94
Comment: Various changes to discuss with sabdfl
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:

=== Bugs that affect multiple communities ===
Line 11: Line 13:
Looking at this bug report, you can see that it is currently affecting at least 3 communities: The screen-shot shows that this bug currently affects at least three communities:
Line 15: Line 17:
 * Ubuntu  * Ubuntu.
Line 17: Line 19:
In the case of Ubuntu, the bug has been recorded in two places - the sun-java5 and sun-java6 packages. In Ubuntu's case, the bug has been recorded in two places: the sun-java5 and sun-java6 packages.
Line 19: Line 21:
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. Each row in this table corresponds to a "place" where the bug has been detected, and so needs to be assessed and possibly fixed.
Line 21: Line 23:
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: At the highest level, a "place" is a community, such as an upstream project or a distribution. There are also specialised types of place, which offer a finer level of granularity: for example, a major version of an application or a specific package within a distribution.

=== Several occurrences of the same bug in one project ===

It's possible for a bug to appear in many places in the same project. For example, this bug affects fifteen different packages in Ubuntu:
Line 25: Line 31:
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. You can see that the issue has now been addressed in all packages. As a team works on a bug like that, they will fix different packages at different times. The bug page provides a useful overview of the real work still required before the bug can be considered to be fixed.
Line 27: Line 33:
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): === Fixing bugs in previous versions of software ===

Sometimes, a bug is severe enough that you need to fix it in previous versions of the software, perhaps as a security fix or an 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):
Line 31: Line 41:
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. Note that this bug needed to be fixed in two packages: in the current development release and two stable releases of the distribution. This gives us a total of six rows in the table.
Line 33: Line 43:
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]. === Bugs in external trackers ===

Now, look again at the table for [https://launchpad.net/bugs/86103 bug #86103].

You
may notice that the icon in the assignee row looks unusual. That takes us to the next step in our tour - [:ReviewersGuide/BugWatches:watching bugs in other bug trackers].

Tracking bugs across multiple projects

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.

Bugs that affect multiple communities

Here's an example:

attachment:multiprojectbugs.png

The screen-shot shows that this bug currently affects at least three communities:

  • Java upstream
  • Debian
  • Ubuntu.

In Ubuntu's case, 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 needs to be assessed and possibly fixed.

At the highest level, a "place" is a community, such as an upstream project or a distribution. There are also specialised types of place, which offer a finer level of granularity: for example, a major version of an application or a specific package within a distribution.

Several occurrences of the same bug in one project

It's possible for a bug to appear in many places in the same project. For example, this bug affects fifteen different packages in Ubuntu:

You can see that the issue has now been addressed in all packages. As a team works on a bug like that, they will fix different packages at different times. The bug page provides a useful overview of the real work still required before the bug can be considered to be fixed.

Fixing bugs in previous versions of software

Sometimes, a bug is severe enough that you need to fix it in previous versions of the software, perhaps as a security fix or an 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 to be fixed in two packages: in the current development release and two stable releases of the distribution. This gives us a total of six rows in the table.

Bugs in external trackers

Now, look again at the table for [https://launchpad.net/bugs/86103 bug #86103].

You may notice that the icon in the assignee row looks 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)