launchpad help|
Size: 1647
Comment:
|
← Revision 12 as of 2018-05-10 22:29:23 ⇥
Size: 4149
Comment: GitHub status syncing works
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| '''DRAFT: this page is a work in progress. Please [:Feedback:seek further help] or check the [:TitleIndex:wiki index] for a complete page on this topic.''' | ## page was renamed from Bugs/Multi ## page was renamed from Bugs/MultiProject/Draft |
| Line 3: | Line 4: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">[[TableOfContents]]|| | ~-[[FrontPage|Launchpad Help]] > [[Bugs]] > Multi-project bugs -~ ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
| Line 7: | Line 10: |
| Launchpad is unique in that it can track how the same bug affects different communities, such as free software projects or Linux distributions. | As we saw in the [[Bugs/YourProject|introduction]] to the bugs section of this user guide, Launchpad's bug tracker is special. |
| Line 9: | Line 12: |
| Each community shares the same: | Launchpad can track how the same bug affects different communities, such as free software projects or Linux distributions. |
| Line 11: | Line 14: |
| * bug number * bug report * comment history. |
Each community shares the same bug number, report and comment history. However, they can keep track of how the bug affects them and how they plan to deal with it by setting their own [[Bugs/Statuses|status]], importance and assignee for each bug. |
| Line 15: | Line 16: |
| However, each community can keep track of how the bug affects them and how they plan to deal with it by setting their own: * [:Bugs/Statuses:status] * importance * assignee. This is ideal for free software projects who rely on code maintained by other communities. For example: an Ubuntu user may report a bug in the Exaile media player. Both the Ubuntu packager of Exaile and the upstream Exaile project have an interest in fixing the bug and working together. Launchpad helps them to share their progress through the comment history and email notifications. |
In effect, those communities come together and form an ad-hoc community around the bug report. This is ideal for free software projects who rely on code maintained by other communities. |
| Line 27: | Line 20: |
| There's a table at the top of each bug report in Launchpad that tells you which communities are tracking that bug. | Bugs affecting more than one community is a natural part of life in the free software world. That's why Launchpad makes handling multi-project bugs natural and effortless. |
| Line 29: | Line 22: |
| If you discover that a bug reported in Launchpad also affects your project, you can tell Launchpad using the link directly below the table. | At the top of each bug report in Launchpad is a table that shows you which communities are tracking that bug. |
| Line 31: | Line 24: |
| ||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">attachment:bug-table.png|| ||<style="text-align: center;">'''A bug that affects many projects'''|| |
||<tablestyle="font-size: 0.8em; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">{{attachment:bug-table.png}}|| To tell Launchpad that the bug also affects your project, use the link directly below the table. It's a simple as that. As soon as Launchpad knows that you also want to track that bug, the report shows up just like any other bug reported against your project. The difference is that the bug has become much shallower than if your bug tracker treated your project like an island. Now it's not just people interested in your project who are looking for a fix: it's people from every project that's tracking the bug in Launchpad! = Bugs in external trackers = Of course, not every project that you work with uses Launchpad's bug tracker. Just as you can share a bug report with other projects inside Launchpad, you can also monitor how other projects are tracking that same bug outside of Launchpad. Let's take a look at [[https://bugs.launchpad.net/ubuntu/+source/mozilla-thunderbird/+bug/24220|an example]]. ||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">{{attachment:external-bug.png}}|| ||<style="text-align: center;">'''Bugs in Ubuntu, Debian and upstream'''|| Here, the bug is tracked directly in Launchpad by the maintainers of the Ubuntu Mozilla Thunderbird package. However, Launchpad is also importing status information about the bug from two external bug trackers: Debian BTS, for the Debian Thunderbird package, and Bugzilla for the upstream Thunderbird project. Watching externally tracked bugs is just as easy as marking a bug as affecting multiple projects within Launchpad. Follow the link below the table and choose the relevant project. {i} '''Note:''' even though the project uses an external bug tracker, the project must be [[Projects/Registering|registered]] in Launchpad. == External trackers that Launchpad supports == Launchpad can link to and, in most cases, import the status of bugs reported in the following external trackers. || '''Bug tracker''' || '''Import status?''' || || Bugzilla || Yes || || Debian BTS || Yes || || Trac || Yes || || Sourceforge || Yes || || Mantis || Yes || || RT || Yes || || Savane || Coming soon || || Gforge || Coming soon || || Git``Hub || Yes || To ensure ease of use and consistency, Launchpad translates the statuses used by external trackers. = Next step = There's a table of the translations that Launchpad makes, along with an explanation of Launchpad's approach to bug statuses, [[Bugs/Statuses|next]]. ||<tablestyle="width: 100%;"> ~-[[Bugs/YourProject|< Using Launchpad to track your project's bugs]] -~ ||<style="text-align: right;"> ~- [[Bugs/Statuses|Bugs statuses >]] -~ || |
Launchpad Help > Bugs > Multi-project bugs
Overview
As we saw in the introduction to the bugs section of this user guide, Launchpad's bug tracker is special.
Launchpad can track how the same bug affects different communities, such as free software projects or Linux distributions.
Each community shares the same bug number, report and comment history. However, they can keep track of how the bug affects them and how they plan to deal with it by setting their own status, importance and assignee for each bug.
In effect, those communities come together and form an ad-hoc community around the bug report. This is ideal for free software projects who rely on code maintained by other communities.
Working with multi-project bugs
Bugs affecting more than one community is a natural part of life in the free software world. That's why Launchpad makes handling multi-project bugs natural and effortless.
At the top of each bug report in Launchpad is a table that shows you which communities are tracking that bug.
|
To tell Launchpad that the bug also affects your project, use the link directly below the table. It's a simple as that.
As soon as Launchpad knows that you also want to track that bug, the report shows up just like any other bug reported against your project. The difference is that the bug has become much shallower than if your bug tracker treated your project like an island.
Now it's not just people interested in your project who are looking for a fix: it's people from every project that's tracking the bug in Launchpad!
Bugs in external trackers
Of course, not every project that you work with uses Launchpad's bug tracker.
Just as you can share a bug report with other projects inside Launchpad, you can also monitor how other projects are tracking that same bug outside of Launchpad.
Let's take a look at an example.
|
Bugs in Ubuntu, Debian and upstream |
Here, the bug is tracked directly in Launchpad by the maintainers of the Ubuntu Mozilla Thunderbird package. However, Launchpad is also importing status information about the bug from two external bug trackers: Debian BTS, for the Debian Thunderbird package, and Bugzilla for the upstream Thunderbird project.
Watching externally tracked bugs is just as easy as marking a bug as affecting multiple projects within Launchpad. Follow the link below the table and choose the relevant project.
Note: even though the project uses an external bug tracker, the project must be registered in Launchpad.
External trackers that Launchpad supports
Launchpad can link to and, in most cases, import the status of bugs reported in the following external trackers.
Bug tracker |
Import status? |
Bugzilla |
Yes |
Debian BTS |
Yes |
Trac |
Yes |
Sourceforge |
Yes |
Mantis |
Yes |
RT |
Yes |
Savane |
Coming soon |
Gforge |
Coming soon |
GitHub |
Yes |
To ensure ease of use and consistency, Launchpad translates the statuses used by external trackers.
Next step
There's a table of the translations that Launchpad makes, along with an explanation of Launchpad's approach to bug statuses, next.
