Launchpad itself

Easily link to codebrowse interface from bug reports

Bug #131279 reported by Paul Carduner
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

There is no way to easily link to the codebrowse interface from bug reports or anywhere for that matter. By easily I mean not using a big long url like http://codebrowse.launchpad.......

Let's say I have just committed a fix for bug #12345 and I committed it to a bzr branch called foo and the revision number was 78. It would be exceedingly useful if when I marked that bug as "fix committed," I could put in the comment message something like "fix committed in rev:foo/78", and the rev:foo/78 part would automagically turn into a link to the diff for that revision in the codebrowse interface for the foo branch. It would also be nice if I could use this type of syntax anywhere in launchpad: blueprints, answers, etc.

Matthew Paul Thomas (mpt)
Changed in launchpad:
importance: Undecided → Medium
Revision history for this message
Tim Penhey (thumper) wrote :

I think this is a really good idea.

Changed in launchpad-bazaar:
importance: Medium → Wishlist
status: New → Confirmed
Revision history for this message
Tim Penhey (thumper) wrote :

The harder bit however is deciding how to uniquely identify the revision.

Branches are identified using ~user/project/name so we'd want at least that to identify a branch. From that we'd have to somehow specify that we are interested in a specific revision of that branch.

Paul, do you have any suggestions?

Revision history for this message
Paul Carduner (pcardune) wrote :

I guess I still have the same suggestions I specified in the original bug report. Just append the revision number in question to the end of the branch path with a / or : or ; or some other separator between the path and revision number.

Revision history for this message
Jonathan Lange (jml) wrote :

Note that the mapping from (branch, revno) to a revision is not fixed over time. Revisions can be uncommitted, branches can be replaced etc.

Perhaps it would be best to take the entered branch and revision number and then internally map it to a revision ID?

Revision history for this message
Paul Carduner (pcardune) wrote : Re: [Bug 131279] Re: Easily link to codebrowse interface from bug reports

Ah yes, I forgot about those things (still used to using subversion).
I like your suggestion though of internally mapping it to a revision
ID.

Revision history for this message
David Allouche (ddaa) wrote :

I am not convinced the added complexity of internally recording revisions ids for revno-based, plain-text branch references is worth the trouble.

If people refer to a revision by anything than revid, then use uncommit or pull/push --overwrite to change the meaning of what they referred to, things will be confusing anyway. So the simplest, and the closest to what the user did, is the better.

Things are different for bug references found in revision data, or other forms of linking when the revision id is known. This comment only applies to linking to revision by revno from plain text references such as bug comments.

Revision history for this message
Martin Albisetti (beuno) wrote :

Apart from the tricky part where revnos can change, this sounds like an interesting idea for jml!

Changed in launchpad-bazaar:
status: Confirmed → Triaged
Revision history for this message
Adam Candy (asc) wrote :

+1, this would be helpful in the case of developing large projects where there are many project branches, associated merge requests, bugs and fixes - it would be useful to cross-reference these.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.