launchpad help|
Size: 1388
Comment:
|
Size: 1407
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| When bugs are being fixed in bazaar branches, and those branches are registered in launchpad, the bugs and branches can be linked. |
If you create a Bazaar branch to fix a specific bug, and that branch is registered in Launchpad, you can link the bug report and the branch. |
| Line 6: | Line 5: |
| This link is indicated in the branch and bug listings as badges. The badges give a quick indication that someone has code that intends to fix a particular bug, and that this information is easily shown in the general bug and branch listings. |
Launchpad uses an icon to indicate the link in the branch and bug listings. The icons are a quick way for anyone to see that you have code that is intended to fix a particular bug. |
| Line 11: | Line 7: |
| The branch listing for the beagle project is a good example. The badge is a grey bug. This badge is hyperlinked to the actual bug page. |
For example, take the branch listing for the Beagle project. You can see grey bug icons beside the name of some branches. Clicking on the bug icon takes you to the relevant page in the bug tracker. |
| Line 16: | Line 11: |
| Line 19: | Line 13: |
| The bug listing shows the branch badges. Branch badges are small bazaar icons, and these are also hyperlinked to the branch page. |
Similarly, on the bug listing pages, a yellow Bazaar logo appears next to bugs that are linked to a branch. Clicking on the Bazaar icon takes you to the relevant branch. |
| Line 26: | Line 19: |
| The bug branch links have a status, and a whiteboard. The status indicates the progress of the fix, and the whiteboard can contain any plain text that may be used to convey more specific information. |
Each link between a bug and branch has its own status and whiteboard. The status indicates the progress of the fix, and you can use the whiteboard for more detailed information. |
| Line 30: | Line 21: |
| Any Launchpad user can have multiple branches of code for a project, and teams can have multiple branches too. How do you know which branch to use when starting new work? | |
| Line 31: | Line 23: |
| Any person can have multiple branches of code for a project, and teams can have multiple branches too. How does one know which branch to use when starting new work? For this, we have major branches in the project, which we call "Series", and that's what we will [:ReviewersGuide/ProductSeries:show you next]. | For this, we have major branches in the project, which we call "Series", and that's what we will [:ReviewersGuide/ProductSeries:show you next]. |
Fixing bugs in dedicated branches
If you create a Bazaar branch to fix a specific bug, and that branch is registered in Launchpad, you can link the bug report and the branch.
Launchpad uses an icon to indicate the link in the branch and bug listings. The icons are a quick way for anyone to see that you have code that is intended to fix a particular bug.
For example, take the branch listing for the Beagle project. You can see grey bug icons beside the name of some branches. Clicking on the bug icon takes you to the relevant page in the bug tracker.
attachment:beaglebranchlisting.png
Similarly, on the bug listing pages, a yellow Bazaar logo appears next to bugs that are linked to a branch. Clicking on the Bazaar icon takes you to the relevant branch.
attachment:beaglebuglisting.png
Each link between a bug and branch has its own status and whiteboard. The status indicates the progress of the fix, and you can use the whiteboard for more detailed information.
Any Launchpad user can have multiple branches of code for a project, and teams can have multiple branches too. How do you know which branch to use when starting new work?
For this, we have major branches in the project, which we call "Series", and that's what we will [:ReviewersGuide/ProductSeries:show you next].
