© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I still find this slightly confusing:
Take this page for example: https:/
I wanted to know where are the other bugs for Chromium-Browser. Clicking "bugs" in the menu-major at the top takes me here,
https:/
"Chromium Browser must be configured in order for Launchpad to forward bugs to the project's developers." doesn't seem to apply to me though. I'm just looking for other peoples bugs, like #621786. And, even if I wanted to file bugs, why do I really care if it is set to work with Chromium-browser upstream. We all know 95% of the bugs on launchpad are for Google, and single-login. Not to actually get stuff done. That's why the peon-team files and tracks them upstream after verifying them.
If that isn't clear, deleting the bug id in the URL isn't any better...
https:/
Now I get a simple, "Chromium Browser does not use Launchpad for bug tracking." That still begs the question why was the original bug on Launchpad to begin with...
Alas, I'll check the overview
https:/
But, still not a single mention of how bug tracking works; or, how the original bug was filed... This behavior is not typical of Launchpad. Because it stands out an infobox should inform the user what is going on each Launchpad page in the project. Especially, the user's original landing page...
https:/