"Ayatana Design" project pollutes "bugs resolved upstream" list
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ayatana Design |
New
|
Undecided
|
Unassigned | ||
Bug Description
1. Go to <https:/
2. Choose "Advanced search".
3. Check the checkbox "Show bugs that are resolved upstream", and choose "Search".
What you see: In the search results, many of the bugs are not, in fact, resolved upstream. (At the time of writing, examples include bug 201681, bug 751605, bug 1045269, bug 1045418, bug 1047271, and bug 1049593.)
They show up because they are marked as "Fix Committed" or "Fix Released" in the "Ayatana Design" project, but they are not actually fixed anywhere -- "Ayatana Design" is a fake project that does not have any code.
The "Show bugs that are resolved upstream" list is meant to provide a list of bugs that can easily be resolved -- by packaging the upstream version containing the fix, by cherry-picking the upstream fix, or by copying an upstream's "Won't Fix" decision. But if the "upstream" project is a fake one with no code, that doesn't work.
This problem could be fixed in several ways:
a. Abolish the ayatana-design project, instead using "Triaged" in Unity packages to denote bugs where the desired design is either specified or obvious. This is what we do for Ubuntu Software Center, Software Updater, and Ubiquity, for example.
b. Change the ayatana-design project itself to use "Triaged" to denote bugs where the solution is either specified or obvious, never using "Fix Committed", and using "Fix Released" only to mean "a Unity designer has tested and approved the fix". That way a bug would never be marked fixed in ayatana-design before being marked fixed in the Ubuntu package.
c. Change Launchpad to ignore ayatana-design specifically when determining whether a bug is resolved upstream.
