Sorting out upstream and project bugtrackers

James Henstridge james at jamesh.id.au
Wed Aug 23 15:54:38 BST 2006


On 23/08/06, Matthew Paul Thomas <mpt at canonical.com> wrote:
> 1.  Fix the bug that currently requires the Sourceforge bug tracker to
>      be registered eleven times (!) in Launchpad. (We don't need
>      bugzilla.mozilla.org to be registered separately for each of
>      Firefox, Thunderbird, Seamonkey, etc, so we shouldn't need
>      sourceforge.net/tracker to be registered separately for each
>      Sourceforge project.)

If we want to have a single bug tracker entry for SF, then we'll need
to make the "remote bug number" consist of three numbers:
 * the bug ID
 * the tracker ID (e.g. Python bugs, Python patches)
 * the project ID (e.g. Python)

This could be handled as three comma separated numbers (since the
field is a string column).  When constructing the URL, the IDs could
be split appart again.

While the bug ID is unique accross SF, we can't construct a URL for it
without the other two numbers, so they need to be stored somewhere.
Yes this sucks.  No we can't do anything about it.

The current system has multiple tracker entries for SourceForge
because we currently only store the bug ID as the remote bug number.
The tracker ID and project ID are part of the bug tracker
registration.

James.



More information about the launchpad-users mailing list