launchpad help|
Size: 619
Comment:
|
Size: 2503
Comment: Various changes to discuss with sabdfl
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| = Tracking bugs across multiple projects = | |
| Line 2: | Line 3: |
| 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 single picture overview of the work that is ongoing in all of those communities to engineer a fix to the problem. | 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 === |
| Line 10: | 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 14: | Line 17: |
| * Ubuntu | * Ubuntu. |
| Line 16: | 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. 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: https://launchpad.net/bugs/85124 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): https://launchpad.net/bugs/81782 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]. |
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].
