It's easy to get a product completely wrong, for the same reason it's easy to get a package completely wrong: one could file a gEdit bug that's really a GTK+ issue, an Evolution bug that's really a Cairo issue, or a Launchpad bug that's really a Malone issue.
But to get the distrbution wrong can only be explained, IMHO, by terrible flaws in the design of the filebug workflow, or near fatal blood-alcohol levels. The current flaw is that we have this contextless filebug page:
So I think the real fix here, incrementally speaking, is not to allow changing distro, but to remove the +package page, and replace it with a "jump to distribution" box like we already have for products.
It's easy to get a product completely wrong, for the same reason it's easy to get a package completely wrong: one could file a gEdit bug that's really a GTK+ issue, an Evolution bug that's really a Cairo issue, or a Launchpad bug that's really a Malone issue.
But to get the distrbution wrong can only be explained, IMHO, by terrible flaws in the design of the filebug workflow, or near fatal blood-alcohol levels. The current flaw is that we have this contextless filebug page:
https:/ /launchpad. net/malone/ bugs/+package
and it defaults to Baltix.
So I think the real fix here, incrementally speaking, is not to allow changing distro, but to remove the +package page, and replace it with a "jump to distribution" box like we already have for products.
Thoughts?