Comment 4 for bug 553947

Actually the scenario that I was thinking on is different: I worked on a
branch, I proposed it for merging, the merge was approved and now I'm
merging it in trunk with `bzr merge` and `bzr commit --fixes`.

In this situation there are two branches involved: lp:project (the
trunk) and lp:~me/project/fix-1234 (the branch where I worked on the
fix). lp:~me/project/fix-1234 is linked to the relevant merge proposal
and contains all the "intermediate" revisions that were needed in oreder
to fix the bug. lp:project instead is linked to a large number of merge
proposals and contains only the toplevel revisions.

Looking at the bug report, the most relevant branch is, in my opinion,
lp:~me/project/fix-1234. Currently lp:project does not offer any
information about the bug that may be useful to a developer nor to a
user, except when the fix is in one of the most recent revisions. The
only additional and useful information that lp:project contains, but
that isn't currently displayed, is the revision where the fix landed.

On Tue, 2010-04-13 at 06:11 +0000, Martin Pool wrote:
> I think there are two different scenarios here:
>
> 1- I am marking this _branch_, at a particular revision, related to
> this bug. I want to see the branch from the bug page, I want to see
> the bug in the context of the merge proposal, etc.
>
> 2- I'm just marking a revision, perhaps in trunk, as fixing the bug,
> and I don't particularly care about kicking off that merge-related
> workflow. I'm interested in navigating from the bug to the revision,
> and from that revision to that bug, but not between the bug and
> branch.

Thanks,
Andrea