launchpad help|
Size: 656
Comment: first cut - needs thumper's attention
|
← Revision 7 as of 2008-06-17 14:21:18 ⇥
Size: 1421
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| XXX Tim, please could you fill this in? Should include: | = Fixing bugs in dedicated branches = |
| Line 4: | Line 4: |
| * screenshot of branch listing with bug badges (please only show one badge per branch ;-)) * sample URL or two which show a bug with branches, and a branch with bugs, and cutouts of the relevant parts of those pages |
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 7: | Line 6: |
| Preserve this bit, which is the lead into the next section: | 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 9: | Line 8: |
| 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 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. http://code.beta.launchpad.net/beagle {{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. https://bugs.beta.launchpad.net/beagle/+bugs {{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 [[FeatureHighlights/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.
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.
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 show you next.
