• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

Fixing bugs in dedicated branches

When bugs are being fixed in bazaar branches, and those branches are registered in launchpad, the bugs and branches can be linked.

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.

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.

• http://code.beta.launchpad.net/beagle

attachment:beaglebranchlisting.png

The bug listing shows the branch badges. Branch badges are small bazaar icons, and these are also hyperlinked to the branch page.

• https://bugs.beta.launchpad.net/beagle/+bugs

attachment:beaglebuglisting.png

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.

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].