UbuntuEngineering
Bugs
Escalated Ubuntu Engineering Stakeholder Bugs
Bug # |
Issue |
On Behalf Of |
Launchpad Status |
removal of arch-all packages while there are arch-specific packages dependent on it results in uninstallable binaries |
David Mandala / ARM |
Escalated 2011-07, Fixed 2011-10 |
|
Distribution drivers permissions may need redesign |
Marjo Mercado / QA |
Escalated 2011-03, no action, still issue worked around by hack use of ubuntu-release perms |
|
It's impossible to see all the bugs that affect a Bug Target if some are targetted to one or more series and the Master task is closed. |
Jamie Strandboge / Security |
Escalated 2011-10 |
|
Limited upload rights no longer give series nomination accept/decline rights |
Marjo Mercado / QA |
Escalated 2011-03, Fixed 2011-05 |
|
Show linked upstream projects to the translatable templates in the +templates page |
David Planella / Translations |
Escalated 2011-05, Fixed 2011-08 |
|
Empty translations on one side do not get translated by the other side |
David Planella / Translations |
Escalated 2011-05, Declined 2011-07 (corner case) |
|
multiple people seeing bug, status stays new |
Kate Stewart / Release |
Escalated 2011-05, Fixed 2011-07 |
|
Bugs assigned to new targets/series are easily missed (their default values sort at the end of bug lists) |
Kate Stewart / Release |
Escalated 2011-05, Workaround script 2011-06 |
|
Raise priority of time-sensitive copy archives |
Matthias Klose / Foundations |
Escalated 2011-07, Colin ok'd fix - 2012-08 |
|
BugNomination:+editstatus timeout for bugs with many tasks |
Jamie Strangboge / Security |
Escalated 2011-10 |
|
adding/removing user/team subscriptions to bug reports edits date_last_updated |
Ursinha/ DA&Server |
Escalated 2011-11 |
|
timeout when marking as duplicate |
Ursinha/DA&Server: impacting workflow |
Escalated 2011-11 |
|
queue and override manipulations should have audit trail |
Kate Stewart/Release |
attempted to Escallated 2012-03 - being worked, need to find out status |
|
Merge's dying from late evaluation of security rules |
dholbach: Community prio - requested escalation 2012/08/13 |
||
timeout on code.launchpad.net/~ubuntu-branches |
dholbach: Community prio - requested escalation 2012/08/13 |
Bugs being Assessed - Maintenance or Feature scope
Bug # |
Issue |
comments |
bug search fails to find results despite exact search string being in bug titles |
bdmuray: DA prio: useful for launchpad to return relevant results, Need to understand if will be handled by column search LEP - escalated 2011/11/16 |
|
findSimilarBugs() in the Launchpad API returns strange things |
bdmurray: DA prio: we have lots of duplicate bug reports in Launchpad and it would be useful if the text searching within and using Launchpad returned relevant results. - escalated 2011/11/16 |
Bugs To Monitor & Review
Bug # |
Issue |
comments |
bug watches for archived debian bug reports appear not to exist |
budmurray: DA prio: They are actually showing up as Fix Released now which is wrong and makes it very hard to tell from what set of bugs we may be able to find a fix upstream. |
|
janitor shouldn't blindly set duplicate bugs to Fix Released |
bdmurray: DA prio: Brian found about 232 cases where the janitor, using changelog info, set a duplicate bug to Fix Released. That's 232 less bugs! Really the janitor knows or can know whether or not a bug is a duplicate and should do something smarter. |
|
bug to question not available in the API |
bdmurray: DA prio: You have to use the web interface to convert a bug to a question and converting a bug to question would be useful for enforcing a minimum bug quality. |
|
Improve bug association with specific Ubuntu releases |
LEP should cover, need to get status of LEP |
|
Cannot have a bug targetted only to an old series |
LEP handle? else what alternatives? |
|
When the Janitor autoconfirms a bug, it should explain why |
Bryce escalated, result of autoconfirm change (777874) - Fixed |
|
Ubuntu bugs marked "Fix released" before fix is generally available |
closing on upload is not correct dynamic, should be closing on publishing |
|
Message sharing should prioritize messages from the current distro |
dpm: High: Right now the latest package upload with translations, regardless of the distro series, will be used as the source for current translations and these translations get propagated to all series. This means that a Lucid upload will take over as the current source of translations over Natty. This tends to confuse translators and overwrite their fixes (i.e. data loss) done in Launchpad. |
|
Sharing details page: automatic synchronization detection needs to be aware of LP usage |
dpm: high: We want this feature to be used for both external projects and for projects hosted in Launchpad. Right now projects in Launchpad are expected to do automatic imports of both translations and templates to use the feature, where it should be possible for them to just import templates to do upstream sharing. Importing both templates and translations is not only a bit of a waste, but unless the maintainers are really active in fetching translations from Ubuntu -which is not generally the case-, it can lead to overwriting new translation data with old one. A common example is the case where translations are automatically imported, but out of sync with newer translations from Ubuntu: in that case upstream imports have got precedence and will overwrite newer Ubuntu translations. |
|
"Bouncing" between branch imports and branch exports |
dpm: medium: This hasn't got directly to do with upstream translations sharing, but it might become more of an issue when upstream sharing gets widely used and translations precedence starts kicking in. It'd be great if upstream maintainers in Launchpad could fully automate the translations process, and having the same branch for translations imports and exports is the way to go. However, they cannot use this feature right now, due to commits being done even if translations have not changed. |
|
?? |
Bug Heat is not intuitive or consistent |
Many don't know what it means, see: bug survey |
No way of deliberately requesting someone's input in a bug |
|
|
"Also affects distribution" fields default to the worst possible values |
|
|
Bugs need a way to link test cases and an api to extract them |
|
|
Allow the option of selectively blacklisting certain bug tags |
|
|
searching for reopened bug tasks |
|
|
Incomplete and Confirmed bug statuses use the same color |
|
|
timeout querying a list of bugs ordered by heat on packages a team is subscribed to |
Foundations prio |
Bug Collections:
Features
Bug Lifecycle and Developer/Triager Workflow Improvements: https://dev.launchpad.net/LEP/BugLifecycle
https://blueprints.launchpad.net/launchpad/+spec/other-o-bug-lifecycle
20111103 - https://blueprints.launchpad.net/ubuntu/+spec/other-p-bug-workflows
consistency for states between teams so effective aggregation (common interpretation of states, incomplete, fix committed, fix released (eg. 827912))
- standardize notation for expressing state transition
- 2011117 - per stakeholders meeting, agreement that Francis will help ensure merged model is implementable before we survey back to teams for feedback.
Bug Series Cleanup: https://dev.launchpad.net/LEP/OnlySeriesTasks
20111103 - https://blueprints.launchpad.net/ubuntu/+spec/other-p-bugtaskseries
- 20111117 - per stakeholders meeting will be handled as part of maintenance.
Help Upstream Bug: https://dev.launchpad.net/LEP/BugzillaComponents
better handoff of bugs to upstream, and detection of fixes from upstream (improve fix detection: 605293)
- 20111117 - per stakeholders, agreement this should be considered for roadmap
- Improved Bug Search Capabilities
- 2011117 - if scope of escalated bugs exceeds maintenance squad capability, need to look at getting this added.
Undefined
- A way to mark bugs as fixed (no longer in progress), but waiting for a merge (not yet fix committed)
- Probably should be folded into Kate's Bug Status rework plans
- 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
- Need to investigate current status of this need, and raise it through the bug escalation process
- 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?)
- Hand this one to the Ubuntu Engineering stakeholder list
see also Ubuntu Community Features tracked at: https://dev.launchpad.net/Ubuntu/InfrastructureNeeds
Launchpad/Stakeholder/UbuntuEngineering (last edited 2012-08-15 18:11:12 by 99-191-111-134)