Diff for "Code/BugAndBlueprintLinks"

Not logged in - Log In / Register

Differences between revisions 1 and 2
Revision 1 as of 2008-09-12 22:32:02
Size: 1917
Editor: 92-237-59-186
Comment: wip
Revision 2 as of 2008-09-15 14:55:26
Size: 1872
Editor: 92-237-59-186
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
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. 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. This helps those people who are interested in the bug to follow the progress of the work to address it.
Line 9: Line 9:
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. In branch listings, and on the branch overview page itself, Launchpad uses an icon to indicate a link between a bug report and a branch of code. Similarly, there's a yellow Bazaar icon in bug listings to show which reports are linked to a branch of code.
Line 11: Line 11:
For example, take the [[https://code.edge.launchpad.net/drizzle|branch listing for the Drizzle]] 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. Let's take a look at an example: take the [[https://code.edge.launchpad.net/drizzle|branch listing for the Drizzle]] project. As you can see, some branches have grey bug icons beside their name. Click on one of those the bug icons and Launchpad will take you to the bug report page.
Line 16: Line 16:
Similarly, on Drizzle's 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. From the other side of this relationship - i.e. Drizzle's bug listing pages - you'll see the yellow Bazaar logo next to bug reports that are linked to a branch. Clicking on the Bazaar icon takes you to the relevant branch.
Line 22: Line 22:
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. 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 24: Line 24:
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]].
= Next step =

DRAFT: this page is a work in progress. Please seek further help or check the wiki index for a complete page on this topic.

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. This helps those people who are interested in the bug to follow the progress of the work to address it.

In branch listings, and on the branch overview page itself, Launchpad uses an icon to indicate a link between a bug report and a branch of code. Similarly, there's a yellow Bazaar icon in bug listings to show which reports are linked to a branch of code.

Let's take a look at an example: take the branch listing for the Drizzle project. As you can see, some branches have grey bug icons beside their name. Click on one of those the bug icons and Launchpad will take you to the bug report page.

drizzle-branches.png

Drizzle branches

From the other side of this relationship - i.e. Drizzle's bug listing pages - you'll see the yellow Bazaar logo next to bug reports 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.

Next step

Code/BugAndBlueprintLinks (last edited 2009-08-03 12:42:02 by stc92-2-82-228-137-96)