Diff for "Ubuntu/InfrastructureNeeds"

Not logged in - Log In / Register
Differences between revisions 6 and 19 (spanning 13 versions)
⇤ ← Revision 6 as of 2009-12-10 01:43:23 →
Size: 9188
Editor: jml
Comment:
← Revision 19 as of 2011-10-13 02:38:28 → ⇥
Size: 5816
Editor: bryce
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
|| '''Launchpad contact''' || [[https://launchpad.net/~jml|Jonathan Lange]] ||
|| '''Ubuntu contact''' || ??? ||		 || '''Launchpad contact''' || [[https://launchpad.net/~flacoste|Francis Lacoste]] ||
|| '''Ubuntu contact''' || [[https://launchpad.net/~bryce|Bryce Harrington]] ||

'''This is an old page that has not been updated recently; many of the items mentioned here are complete or obsolete, and the priorities need revisited on the remainder. -- bryce'''
Line 7: Line 9:

 1. Monitoring of Debian bugs
  * Tracked at: '''https://blueprints.edge.launchpad.net/malone/+spec/debian-bug-import-continuous-imports''' ???
  * Rationale: Nearly all Debian bugs also affect Ubuntu, and Debian's larger base of developers can find and fix a higher volume of bugs. We should be informed of these bugs so that we can make a decision about whether to act on them.
  * Status:
   * A script exists to import bugs from debbugs into Launchpad: '''https://blueprints.launchpad.net/malone/+spec/debian-bug-import'''
   * Launchpad can already import comments from debbugs, and send replies back to debbugs. A separate issue is whether or not we proactively import ALL Debian bugs into Launchpad, or whether we only import a subset of bugs (say, RC bugs), or whether we only import Debian bugs which have been manually correlated to Ubuntu bugs.
   * '''https://blueprints.launchpad.net/malone/+spec/upstream-bug-searching-and-filing'''. The expensive implementation depends on bugzilla-launchpad-identification.
    * Depends on BugTrackerImport.context
    * From also-affects-upstream:
     * Offer link to search first and say "(opens in new window)"
     * Group in sections:
      * "Didn't find your bug?": Offer a button that says "Report bug upstream (requires account in bugzilla.gnome.org) (opens in new window)"
      * Offer a box to enter the existing bug URL
    * Post to enter_bug.cgi form containing:
     * description (include URL to Launchpad bug) - summary
     * product (which comes from BugTrackerImport.context)
    * User is redirected to login, he uses his credentials and then bug is filed.
     * demo URL: http://people.ubuntu.com/~jamesh/file-bug-gnome.html
    * Less cheap would include a special plugin for GNOME bugzilla to provide a URL to redirect the end-user to a special URL. The "from-launchpad" keyword would be useful as well.
    * If we import bugs regularly, bug watches can be created at scan time.
  * Ideas:
   * Create non-Launchpad infrastructure to monitor bugs - Where to get notification addresses? Scrape launchpad?
   * MoM's bug notifications could be the basis of a partial solution
Line 37: Line 15:
   * The "no upstream bug tracker exists" use case, which is described in '''https://blueprints.launchpad.net/malone/+spec/forwarding-to-email-address'''
   * Simplified/automatic filing of bugs in an external bug tracker
   * Comment synching to enable inter-bug-tracker replies		    * The "no upstream bug tracker exists" use case, which is described in '''https://blueprints.launchpad.net/malone/+spec/forwarding-to-email-address''' (Done?)
   * Comment synching to enable inter-bug-tracker replies (Done?)
   * Map remote bugtracker product/component to source package (Nearly done)
   * Forwarding of selected attachments from LP bug to external
   * Automatic user registration in remote tracker
   * Automatic fill-in of upstream bug report fields (title, description, priority, cc, etc.)
Line 42: Line 23:

'''''NOTE: Some of this section may be already implemented. We're porting over notes from early 2009; it's now late 2009.'''''

 1. Rebuild testing in Launchpad
  * Tracked at: '''???'''
  * Rationale: Rebuild testing is currently performed using a dak instance. Failures must be processed manually by a buildd admin and the relevant developers notified. This requires maintaining redundant infrastructure and more manual work than should be necessary.
  * Status
   * As of 2009-05-15: Largely done; test currently in progress at https://launchpad.net/ubuntu/+archive/test-rebuild-20090513 (summary at http://people.ubuntuwire.com/~wgrant/rebuild-ftbfs-test/). Remaining omission is that the rebuild archive is not published and therefore is unable to use its own output (internal RT #34356).

 1. Web interface for syncing source packages in Soyuz, accessible to those with corresponding upload privileges
  * Tracked at: '''???'''
  * Rationale: "Syncing", i.e. copying source packages verbatim from one distribution to another, is a very common operation in Ubuntu, and is often requested by developers either after automatic syncs from Debian stop a couple of months into the release cycle, or when all changes have been incorporated into Debian and the Ubuntu changes may be discarded. At present, this operation is restricted to those with privileged shell access to the production archive. Conceptually, it should only require upload access to the corresponding component. Allowing uploaders to perform this task would save on the order of an hour a day of archive administrator time performing trivial requests. Syncing should also be possible from PPAs

  * Status:
   * Debian sources now available in Launchpad database, updated twice daily, making this more feasible
   * syncSource method available in API
   * Some problems with changelog presentation in web UI and in mails to -changes lists; '''https://bugs.launchpad.net/soyuz/+bug/55795''' documents part of this

== Low priority ==

 1. Opening a new distrorelease before releasing the previous one (shortcoming relative to former dak infrastructure)
  * Tracked at: '''https://bugs.launchpad.net/soyuz/+bug/87012'''
  * Rationale: When opening a new distrorelease, uploads must be temporarily blocked until the toolchain and other basic infrastructure are in place. Opening the new release early would allow this work to happen in parallel, so that the new release would be immediately open for development.

  * Status:
   * PPAs make it possible to do some of the preparatory work for a new distro series
   * Fully handling this was not targeted for Launchpad 4.0

 1. Improved activity logging
  * Tracked at: '''???'''
  * Rationale: The current activity log in the Launchpad bug tracking system does not capture milestone changes. This presents a problem for release managers, who have no way to tell whether the milestone on a bug was set by somebody they trust, or whom to contact about it if the person who milestoned the bug omitted to leave a comment.

  * Note that milestones are not designed to be tightly controlled, we have tight control of release-critical bugs targeted to the specific series, where only drivers can approve the bug as RC.

  * Status: Apparently needs a [[https://blueprints.launchpad.net/malone/+spec/bug-history|rewrite of the activity log]].
   * '''https://bugs.launchpad.net/malone/+bug/65660''' (Joey: Fix Released)
   * Not targeted in Launchpad 4.0
Line 95: Line 39:
 1. Prohibit filing bugs on obsolete packages (Bug:46385)

 1. [[https://dev.launchpad.net/Bugs/BugQ%26A|Bug Q&A]]

== Low priority ==

 1. Opening a new distrorelease before releasing the previous one (shortcoming relative to former dak infrastructure)
  * Tracked at: '''https://bugs.launchpad.net/soyuz/+bug/87012'''
  * Rationale: When opening a new distrorelease, uploads must be temporarily blocked until the toolchain and other basic infrastructure are in place. Opening the new release early would allow this work to happen in parallel, so that the new release would be immediately open for development.

  * Status:
   * PPAs make it possible to do some of the preparatory work for a new distro series
   * Fully handling this was not targeted for Launchpad 4.0
Line 104: Line 62:
   * What does this mean exactly?

 1. Subscribe someone (or a team) to a tag, e.g. 'regression'

 1. Ability to clone a bug

 1. Hiding comments or removing comments (Req'd by kernel team)

 1. Soyuz archive index (Req'd by Software Center)

 1. Search across attachments

 1. Tarball visibility / navigation

 1. Structured bug json data - aka "tags with values"

 1. git support

 1. search PPAs for version of app you want, for version of ubuntu you're on

 1. a new status for bugs between the in progress and fix committed, for when you fixed the bug and waiting for merge...

== Other stakeholder issues also relevant to Ubuntu: ==

 1. [[https://dev.launchpad.net/VersionFourDotO/OutOfScope/Blueprints|Wiki markup in blueprints]] (OEM)

 1. Task tracking in blueprints (aka [[https://dev.launchpad.net/VersionFourDotO/OutOfScope/Blueprints|Blueprint decomposition]]) (OEM)

 1. Add a "workaround" field to bug (Bug:54652). (Corp Services)

 1. Launchpad doesn't support multiple attachment (Bug:82652). (Corp Services)

This page discusses ways Launchpad could better serve the Ubuntu community. Please contact us with thoughts or questions.

Launchpad contact

Francis Lacoste

Ubuntu contact

Bryce Harrington

This is an old page that has not been updated recently; many of the items mentioned here are complete or obsolete, and the priorities need revisited on the remainder. -- bryce

High Priority

  1. Semi-automatic bug forwarding to upstream bug trackers

    • Tracked at: ???

    • Rationale: Ubuntu receives a very high volume of bug reports which should be forwarded upstream. Making this process more efficient would improve both the quality of Ubuntu and its relationships with upstream projects.
    • Status: Some of the steps for this to happen are implemented. Additional work includes:

      • The "no upstream bug tracker exists" use case, which is described in https://blueprints.launchpad.net/malone/+spec/forwarding-to-email-address (Done?)

      • Comment synching to enable inter-bug-tracker replies (Done?)
      • Map remote bugtracker product/component to source package (Nearly done)
      • Forwarding of selected attachments from LP bug to external
      • Automatic user registration in remote tracker
      • Automatic fill-in of upstream bug report fields (title, description, priority, cc, etc.)

Medium Priority

  1. Temporarily adding the uploader as a bug contact for the package being uploaded
    • Rationale: Our development model is such that packages are often uploaded by a developer who has no ongoing relationship with the package. Because they do not receive bug reports for the package, it is easy for them to be unaware of having introduced a regression.
    • Status:
  2. Visual distinction between bug comments from authoritative Ubuntu people and bug comments from random Launchpad users

    • Tracked at: ???

    • Rationale: Users who view and file bugs in Launchpad are not always familiar with the way bug tracking works in a large community project like Ubuntu. When they receive a comment which is inappropriate, erroneous or poorly presented, they assume that it came from someone representing the project, when in fact anyone with an email address can post a response. Users who find these bugs via web searches have difficulty telling the difference between comments from users and authoritative information from developers and QA. We want to avoid this confusion and misrepresentation, while still allowing everyone to participate, by visually showing the user whether the commenter is a member of an official team (such as Ubuntu QA), perhaps by showing the team badge next to their name.
    • Status:

  3. Prohibit filing bugs on obsolete packages (46385)

  4. Bug Q&A

Low priority

  1. Opening a new distrorelease before releasing the previous one (shortcoming relative to former dak infrastructure)

    • Tracked at: https://bugs.launchpad.net/soyuz/+bug/87012

    • Rationale: When opening a new distrorelease, uploads must be temporarily blocked until the toolchain and other basic infrastructure are in place. Opening the new release early would allow this work to happen in parallel, so that the new release would be immediately open for development.
    • Status:
      • PPAs make it possible to do some of the preparatory work for a new distro series
      • Fully handling this was not targeted for Launchpad 4.0
  2. Notifying the release team of new milestone targets

    • Tracked at: ???

    • Rationale: The release team tracks outstanding targets for milestones and their resolution. However, they currently must poll in order to obtain this information. Asynchronous notification would be more efficient.
    • Status:
      • Structural subscriptions were targeted for Launchpad 2.0 (2009-08-03: update, anyone? Do we push notification now?)
  3. Package version tracking for bugs (shortcoming of Launchpad relative to debbugs)
    • Not targeted in Launchpad 2.0
    • What does this mean exactly?
  4. Subscribe someone (or a team) to a tag, e.g. 'regression'
  5. Ability to clone a bug
  6. Hiding comments or removing comments (Req'd by kernel team)
  7. Soyuz archive index (Req'd by Software Center)
  8. Search across attachments
  9. Tarball visibility / navigation
  10. Structured bug json data - aka "tags with values"
  11. git support
  12. search PPAs for version of app you want, for version of ubuntu you're on
  13. a new status for bugs between the in progress and fix committed, for when you fixed the bug and waiting for merge...

Other stakeholder issues also relevant to Ubuntu:

  1. Wiki markup in blueprints (OEM)

  2. Task tracking in blueprints (aka Blueprint decomposition) (OEM)

  3. Add a "workaround" field to bug (54652). (Corp Services)

  4. Launchpad doesn't support multiple attachment (82652). (Corp Services)

Historical infrastructure needs

Ubuntu/InfrastructureNeeds (last edited 2011-11-22 03:34:55 by bryce)