7622
Comment: My notes from sessions I attended
|
7646
formatting!
|
Deletions are marked like this. | Additions are marked like this. |
Line 68: | Line 68: |
= desktop-maverick-desktop-as-IDE = |
= Session Notes = == desktop-maverick-desktop-as-IDE == |
Line 76: | Line 76: |
= kernel-maverick-bug-process = | == kernel-maverick-bug-process == |
Line 88: | Line 88: |
= kernel-maverick-launchpad-bug-requests = | == kernel-maverick-launchpad-bug-requests == |
Line 99: | Line 99: |
#1: Disable dupe suggestion for all source packages the kernel team is a supervisor for (i.e.: https://edge.launchpad.net/~ubuntu-kernel-team/+packagebugs ) #2: Implement mechanism for hiding comments (LP #522741, #557386, #58670) #2.1: Near term - Change from displaying the first 80 comments to the first 40 and last 40 (LP #335120) #3: Implement (possibly per-package) way to control who can re-open fix released bugs #4: Implement a 'lock down' functionality (LP #73122) #5: Get greasemonkey scripts higher profile on LP web docs |
1. Disable dupe suggestion for all source packages the kernel team is a supervisor for (i.e.: https://edge.launchpad.net/~ubuntu-kernel-team/+packagebugs ) 2. Implement mechanism for hiding comments (LP #522741, #557386, #58670) 2.1. Near term - Change from displaying the first 80 comments to the first 40 and last 40 (LP #335120) 3. Implement (possibly per-package) way to control who can re-open fix released bugs 4. Implement a 'lock down' functionality (LP #73122) 5. Get greasemonkey scripts higher profile on LP web docs |
Line 107: | Line 106: |
= desktop-maverick-gpu-hang-reporting = | == desktop-maverick-gpu-hang-reporting == |
Line 116: | Line 115: |
= desktop-maverick-kms-bug-collaboration = | == desktop-maverick-kms-bug-collaboration == |
Line 121: | Line 120: |
= dx-m-qa-workflow = | == dx-m-qa-workflow == |
This page contains notes and links related to Launchpad from UDS Maverick (Belgium, May 2010).
The idea is to collect raw data here and then quickly process it into a more useful form.
Relevant sessions
Note that this deliberately excludes translations stuff, since jml doesn't feel qualified to filter translations gobby notes
-rw-r--r-- 1 jml jml 3459 2010-05-18 10:54 arm-m-archive-features -rw-r--r-- 1 jml jml 3193 2010-05-18 10:54 arm-m-automated-bootstrap -rw-r--r-- 1 jml jml 2791 2010-05-18 10:54 arm-m-automated-testing-framework -rw-r--r-- 1 jml jml 1928 2010-05-18 10:54 arm-m-derived-archive-rebuild -rw-r--r-- 1 jml jml 1150 2010-05-18 10:54 arm-m-development-environment -rw-r--r-- 1 jml jml 4800 2010-05-18 10:54 arm-m-image-building -rw-r--r-- 1 jml jml 1523 2010-05-18 10:55 bazaar-m-agenda -rw-r--r-- 1 jml jml 4250 2010-05-18 11:26 bazaar-m-healthcheck -rw-r--r-- 1 jml jml 2472 2010-05-18 10:55 community-m-adopt-upstream -rw-r--r-- 1 jml jml 3680 2010-05-18 10:55 community-m-development-workflow-review -rw-r--r-- 1 jml jml 2643 2010-05-18 11:20 community-m-document-daily-builds -rw-r--r-- 1 jml jml 1111 2010-05-18 10:55 community-m-harvest -rw-r--r-- 1 jml jml 3570 2010-05-18 10:55 community-m-launchpad-bugs -rw-r--r-- 1 jml jml 3209 2010-05-18 10:55 community-m-launchpad-patches -rw-r--r-- 1 jml jml 3319 2010-05-18 10:55 community-m-patch-review-process -rw-r--r-- 1 jml jml 3061 2010-05-18 10:55 desktop-maverick-desktop-as-IDE -rw-r--r-- 1 jml jml 1916 2010-05-18 10:55 foundations-m-cycle-review -rw-r--r-- 1 jml jml 3054 2010-05-18 13:47 foundations-m-distributed-development-review-and-planning -rw-r--r-- 1 jml jml 1608 2010-05-18 10:55 foundations-m-robust-python-packaging -rw-r--r-- 1 jml jml 2856 2010-05-18 10:55 foundations-m-software-center-roadmap -rw-r--r-- 1 jml jml 2401 2010-05-18 11:23 kernel-maverick-bug-process -rw-r--r-- 1 jml jml 2604 2010-05-18 10:55 kernel-maverick-launchpad-bug-requests -rw-r--r-- 1 jml jml 1901 2010-05-18 10:55 qa-maverick-improving-communication -rw-r--r-- 1 jml jml 2827 2010-05-18 10:55 qa-m-launchpad-test-cases -rw-r--r-- 1 jml jml 626 2010-05-18 10:55 server-m-daily-builds
Ad-hoc feature requests
These are requests that jml got in corridors and side conversations at UDS.
- Store arbitrary metadata on bugs
- Disable bug duplicate detection on apport-filed kernel bugs
- Templates based on host header
Categories for answers & FAQs (bug 236556)
- Merge the patches view with the branches view
- Get all of the patches for any distro for a given upstream
- Need the ability to search for bugs that are targetted for a series in advanced bug search
- Fix the "resolved-upstream" behaviour in Harvest
- When upstream duplicates a bug, harvest thinks it's resolved
- Good mass export of data for Debian / Ubuntu
Bug Q&A could help with noisy, low quality bugs
Other notes
Soyuz/UDS-Maverick has some stuff relevant to Soyuz.
TODO
- Actually put Gobby docs up here, or link, or something
- Link to blueprints
Extract action items for Launchpad & Launchpadders
- Blog about what everyone asked us for
- Share this with Launchpad Stakeholders
Put up some notes about sprints & side initiatives (e.g. user testing)
- Give some kind of indication about which bits we're going to try to do
Session Notes
desktop-maverick-desktop-as-IDE
Fairly high level / conceptual discussion. Launchpad really didn't come up except in the context of groundcontrol. I don't recall any specific Launchpad action items or ideas.
kernel-maverick-bug-process
Planning on an online 'triager summit' in near future to train triagers. Planning a focus on bugs with patches (or SHA1's). Discussed improvements to various launchpadapi scripts shared with X and other teams, and expanded use of tagging to sort their pile of bug reports. Anticipates expiring about 2/3rds of the kernel bugs this month.
Kernel team has requested to turn off dupe suggestion by launchpad for bug reporters. (See next session)
kernel-maverick-launchpad-bug-requests
1. Bug duplication. Hardware-specific bug reports tend to get set as duplicates improperly by bug reporters, because they match based on similarity of *symptoms* when in reality they need to be matched on *symptoms AND hardware*. This is resulting in bug reports falling through the cracks and not getting fixed. For maverick the kernel team wants to switch off any automated or tool-driven mechanism that sets or suggests dupes, and leave this work to triagers.
2. Comment Hiding. Needed for cleaning up 'me-too storms' to make launchpad bugs more palatable to upstream developers, by hiding less relevant comments.
3. Fix Released locking. Disallow re-opening of bugs marked Fix Released except by bug supervisors. Was suggested this be done only for HW-specific packages (although I mentioned this in a Desktop team session and this idea got applause and ooh's from everyone there, so there may be wider interest in this).
4. Lock down. Problem is that certain bugs turn into 'me-too storms'. These bugs get looked into by upstream developers, who are put off by the excessive dogpiling and thence get a dim impression of launchpad bugs and become less likely to help with Ubuntu bugs. Desire is for a mechanism for triagers to switch off comments and status changes from random people other than the original reporter and bug supervisors.
ACTIONS FOR LAUNCHPAD TEAMS:
Disable dupe suggestion for all source packages the kernel team is a supervisor for (i.e.: https://edge.launchpad.net/~ubuntu-kernel-team/+packagebugs )
- Implement mechanism for hiding comments (LP #522741, #557386, #58670) 2.1. Near term - Change from displaying the first 80 comments to the first 40 and last 40 (LP #335120)
- Implement (possibly per-package) way to control who can re-open fix released bugs
- Implement a 'lock down' functionality (LP #73122)
- Get greasemonkey scripts higher profile on LP web docs
desktop-maverick-gpu-hang-reporting
Plans involve turning on higher level of debugging info with certain types of X failure modes. Want to investigate having apport detect if debugging was not on, and offer to reconfigure system to rerun with it switched on.
A concern is that this may result in *much* larger logs (GiB's), so X/kernel team has some actions around avoiding or minimizing that. No action for Launchpad except maybe to be aware of this potential.
The kernel team's request to disable dupe suggestions was discussed. The X.org team generally feels this is not as significant a problem for them (we think because the team updates bug titles pretty aggressively to include chipset and detailed descriptions, so false dupes occur less often). So they would prefer to not opt-in to having dupes disabled.
desktop-maverick-kms-bug-collaboration
X team uses a bunch of launchpadapi scripts for capturing and processing bug reports, this discussion involved a bunch of ideas for extending and improving them. Nothing particularly Launchpad-specific, but I did offer to help on three tasks that are considerably easier for me to do than would be for anyone else.
dx-m-qa-workflow
DX team changes impact Desktop and are quite visible. DX team is more like an upstream in this context. DX needs better follow up on testing, triaging and fixing bugs. No Launchpad action items.