• 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

Daily Build Bugs

Requirements

As a person who's using a daily build package I want to file bugs against the package using ubuntu-bug and have them go to the right place so I can provide feedback on the package in the most useful place

As a maintainer of a daily build package I want bugs filed on my package to go to the bug tracker of my choice so that feedback from my users is captured in a useful way

Or in other words:

1. MUST be able to file bugs on a daily build package using apport / ubuntu-bug
2. Maintainer SHOULD be able to specify an external bug tracker as easily as a project / package on Launchpad
3. Maintainer MUST be able to specify that bugs go on an Ubuntu package's tracker.
4. Maintainer MUST be able to specify that bugs go on a Launchpad upstream project's tracker.
5. If the maintainer has not specified a bug tracker, then users SHOULD still be able to report bugs. These bugs MUST NOT be lost.

Open Questions

• What if the maintainer of the daily build recommends bugs go on tracker X, but the maintainers of tracker X don't like it?
• Why should the PPA maintainer choose? What is driving req 3?
  • james_w says, "So that they can get bug feedback. For say X, they read most of the bugs on the Ubuntu package anyway, and so pick up the daily bugs as part of that. They could set up a project to track the daily bugs, but then they are following yet another place for bugs."

• What should the default bug target be? (social, tool integration)

  • james_w says, "We would presumably still have apport block them. I'm not sure there's a better solution if PPAs are not a bug target."

What do we need

• UI design
• Database patch
• Code
  • the simple data entry bit
  • adhoc external bugtracker registration
    • for when PPA wants to file bugs against a tracker not already in Launchpad
  • changes to apport report to include an Origin that can be mapped back to the PPA.

Timing

• Feature could release first
• Small window to land bugs after that
• Work needs to be done by bugs team to scope, design, etc.

Thinking

From James Westby's email, "Bugs for daily build packages", 2009-11-26 Comments from jml & deryck inline

> 1. Allow a PPA to specify a bug target. Either an LP project or package,
>    or a URL of an external bug tracker.

• If specifying URL of external bug tracker, it should probably register that bug tracker as a proper LP bug tracker
• Another opportunity to create package-project links? (The relationship flattening could happen 3.1.12 cycle)
• This is creating a special relationship between Bugs and PPAs, not shared by other Launchpad apps -- is this problem?

> 2. Export this information in the Packages file using the existing Bugs
>    field.

• Soyuz needs to do this, jml thinks.

[the rest of the stuff in the list is not directly relevant to Launchpad - jml]

3. Extend apport to use this information when it detects the package is
   not from Ubuntu.
4. Where the target is on LP use much the same system as it currently
   does. Where the target is not on LP, but uses a bugtracker it understands,
   make use of that knowledge to file the bug. Otherwise dump the useful
   information to a text file, open the specified URL and tell the user
   to attach the file(s).
5. Possibly extend apport to retrace the reports locally, so that this
   does not have to be done after they are reported. (Duplicating the
   infrastructure we have in Ubuntu for everything would probably be a
   mistake.)