5748
Comment:
|
7552
Incorporating various ideas for features that came up in UDS discussions
|
Deletions are marked like this. | Additions are marked like this. |
Line 5: | Line 5: |
'''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 17: | Line 15: |
* Map remote bugtracker product/component to source package (Nearly done) * Forwarding of selected attachments from LP bug to external |
* Map remote bugtracker product/component to source package: '''https://dev.launchpad.net/LEP/BugzillaComponents''' (Nearly done) * Forwarding of selected attachments from LP bug to upstream - '''https://dev.launchpad.net/LEP/ForwardAttachmentsUpstream''' |
Line 21: | Line 19: |
1. Bug Q&A * Tracked at: https://dev.launchpad.net/Bugs/BugQ%26A * Status: * Is included on Roadmap - '''https://dev.launchpad.net/VersionFourDotO/Stories''' 1. Bug Bookmarks * Tracked at https://bugs.launchpad.net/bugs/193585 * Status: Needs escalation to Launchpad |
|
Line 41: | Line 48: |
1. [[https://dev.launchpad.net/Bugs/BugQ%26A|Bug Q&A]] | 1. Subscribe Team to Tag, e.g. 'regression' 1. Hiding comments or removing comments (Req'd by kernel team) 1. Soyuz archive index * Tracked at: '''https://dev.launchpad.net/ArchiveIndex''' * Rationale: Req'd by Software Center 1. Structured bug json data - aka "tags with values" 1. PPA developer usability enhancements |
Line 60: | Line 77: |
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 1. Ability to clone a bug 1. Search across attachments * From previous discussion, sounds like this would be quite hard / resource intense 1. Tarball visibility / navigation == Undefined == |
|
Line 64: | Line 94: |
1. Subscribe someone (or a team) to a tag, e.g. 'regression' | 1. Blueprints need love |
Line 66: | Line 96: |
1. Ability to clone a bug | 1. Improve mailing lists |
Line 68: | Line 98: |
1. Hiding comments or removing comments (Req'd by kernel team) | 1. Answers needs either significantly improved, or scrapped in favor of just using AskUbuntu.com |
Line 70: | Line 100: |
1. Soyuz archive index (Req'd by Software Center) | 1. 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. |
Line 72: | Line 102: |
1. Search across attachments | 1. 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. |
Line 74: | Line 104: |
1. Tarball visibility / navigation | 1. 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. |
Line 76: | Line 106: |
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... |
1. 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. |
Line 86: | Line 110: |
1. git support. Native git hosting. |
|
Line 88: | Line 114: |
1. Task tracking in blueprints (aka Blueprint decomposition) (OEM) | 1. Task tracking in blueprints (aka [[https://dev.launchpad.net/VersionFourDotO/OutOfScope/Blueprints|Blueprint decomposition]]) (OEM) |
Line 94: | Line 120: |
See also: Launchpad's RoadMap and list of [[LEP|LEPs]]. |
This page discusses ways Launchpad could better serve the Ubuntu community. Please contact us with thoughts or questions. |
Launchpad contact |
|
Ubuntu contact |
High Priority
- 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: https://dev.launchpad.net/LEP/BugzillaComponents (Nearly done)
Forwarding of selected attachments from LP bug to upstream - https://dev.launchpad.net/LEP/ForwardAttachmentsUpstream
- Automatic user registration in remote tracker
- Automatic fill-in of upstream bug report fields (title, description, priority, cc, etc.)
Bug Q&A
Tracked at: https://dev.launchpad.net/Bugs/BugQ%26A
- Status:
Is included on Roadmap - https://dev.launchpad.net/VersionFourDotO/Stories
- Bug Bookmarks
Tracked at https://bugs.launchpad.net/bugs/193585
- Status: Needs escalation to Launchpad
Medium Priority
- 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:
- 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:
original bug at https://bugs.launchpad.net/malone/+bug/81692
https://blueprints.launchpad.net/launchpad-registry/+spec/official-project-members covers this for Bugs and Answers
Launchpad claims this specification is related to the bug: https://blueprints.launchpad.net/launchpad-foundations/+spec/person-name-presentation
- Not targeted in Launchpad 4.0
Prohibit filing bugs on obsolete packages (46385)
- Subscribe Team to Tag, e.g. 'regression'
- Hiding comments or removing comments (Req'd by kernel team)
- Soyuz archive index
Tracked at: https://dev.launchpad.net/ArchiveIndex
- Rationale: Req'd by Software Center
- Structured bug json data - aka "tags with values"
- PPA developer usability enhancements
Low priority
- 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
- 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?)
- Search PPAs for version of app you want, for version of ubuntu you're on
- A new status for bugs between the in progress and fix committed, for when you fixed the bug and waiting for merge
- Ability to clone a bug
- Search across attachments
- From previous discussion, sounds like this would be quite hard / resource intense
- Tarball visibility / navigation
Undefined
- Package version tracking for bugs (shortcoming of Launchpad relative to debbugs)
- Not targeted in Launchpad 2.0
- What does this mean exactly?
- Blueprints need love
- Improve mailing lists
Answers needs either significantly improved, or scrapped in favor of just using AskUbuntu.com
- 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.
- 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.
- 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.
- 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:
- git support. Native git hosting.
Task tracking in blueprints (aka Blueprint decomposition) (OEM)
Add a "workaround" field to bug (54652). (Corp Services)
Launchpad doesn't support multiple attachment (82652). (Corp Services)