Diff for "Ubuntu/InfrastructureNeeds"

Not logged in - Log In / Register
Differences between revisions 26 and 27
⇤ ← Revision 26 as of 2011-11-15 21:55:59 →
Size: 7552
Editor: bryce
Comment: Incorporating various ideas for features that came up in UDS discussions
← Revision 27 as of 2011-11-15 22:05:51 → ⇥
Size: 8195
Editor: bryce
Comment:
Deletions are marked like this. Additions are marked like this.
Line 28: Line 28:

 1. Only Series Tasks
  * Tracked at:
    * https://dev.launchpad.net/LEP/OnlySeriesTasks
    * 20111103 - https://blueprints.launchpad.net/ubuntu/+spec/other-p-bugtaskseries
    * Bugs 314432, 777861, ...
  * Rationale: Many times bugs are specific to a particular version of Ubuntu, but this is not tracked by Launchpad. We work around this by tagging bugs with the release codename but this is done inconsistently (apport will include the tag automatically, but non-apport filed bugs don't). There are various bugs, features, and usability issues for which being able to segregate bugs by series would be a possible solution.

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

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:

  2. Bug Q&A

  3. Bug Bookmarks
  4. Only Series Tasks
    • Tracked at:
    • Rationale: Many times bugs are specific to a particular version of Ubuntu, but this is not tracked by Launchpad. We work around this by tagging bugs with the release codename but this is done inconsistently (apport will include the tag automatically, but non-apport filed bugs don't). There are various bugs, features, and usability issues for which being able to segregate bugs by series would be a possible solution.

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. Subscribe Team to Tag, e.g. 'regression'
  5. Hiding comments or removing comments (Req'd by kernel team)
  6. Soyuz archive index
  7. Structured bug json data - aka "tags with values"
  8. PPA developer usability enhancements

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. Search PPAs for version of app you want, for version of ubuntu you're on
  4. A new status for bugs between the in progress and fix committed, for when you fixed the bug and waiting for merge
  5. Ability to clone a bug
  6. Search across attachments
    • From previous discussion, sounds like this would be quite hard / resource intense
  7. Tarball visibility / navigation

Undefined

  1. Package version tracking for bugs (shortcoming of Launchpad relative to debbugs)
    • Not targeted in Launchpad 2.0
    • What does this mean exactly?
  2. Blueprints need love
  3. Improve mailing lists

  4. Answers needs either significantly improved, or scrapped in favor of just using AskUbuntu.com

  5. PPA improvements. Build status notification. Ability to host multiple versions of a given package (e.g. for bisection study purposes). Expose more of the internal API through the external Launchpad API.
  6. QA tracking. Some way to better flag bugs/branches/patches/etc. as needing testing, passed testing, failed testing, and so on. Ideally should also support hooking into automated testing in some fashion, with the goal of being able to delineate between code ready to be released from that needing additional work.
  7. Some sort of integrated task tracking. Would replace the makeshift work-items currently done in blueprint whiteboards. Could also consolidate the use of team subscriptions, bug tasks, tagging, merge review requests, sync requests, and other makeshift task-workflow-management systems currently in use.
  8. wiki-like functionality in various places throughout launchpad. E.g. PPA descriptions, project home/about pages, blueprints, whiteboards, etc. We need wiki-like markup (including tables), revision tracking, and easy cross-linking to other LP entities.

Other stakeholder issues also relevant to Ubuntu:

  1. git support. Native git hosting.

  2. Wiki markup in blueprints (OEM)

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

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

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

See also: Launchpad's RoadMap and list of LEPs.

Historical infrastructure needs

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