In the past, I've tried to observe myself how I work with bugs in Launchpad. In essence, I have locally a mailfolder, where mails from Launchpad go in whenever a bug I'm assigned or subscribed to get a new message. These are of course bugs I should and in most cases I actually want to pay attention for. However if one would rely on that emails it would be pretty easy to miss older bugs without activity for some time.
So an ubuntu developer must somehow actively query Launchpad for his bugs. In theory this listing should be listed from your the personal bugs page . However, this page is close to useless if you want to triage your 'own' bugs. You can search for bugs you are assigned or subscribed to, that's for sure, but that listing is not restricted to your bugs in ubuntu but bugs in other distribution like debian or other any other projects are listed there as well. Moreover that query ist not restricted to packages I care for, but rather to all bugs I'm subscribed to!
So in the need to query untriaged bugs more effectively, another method is needed. It is a bit cumbersomly hidden in the launchpad UI, but rather useful. First, you need to tell Launchpad what Packages you care for. This is done by subscribing to all bug notification of a package, which effectively makes you a bug supervisor for that particular package in ubuntu. I'm not sure how to navigate there (because I have a smart bookmark in my browser), but have a look at e.g. the bug page for dpkg . You'll find a link 'subscribe' in the green portlet on the left. Click on that and check the box “I want to subscribe to notifications.”. This will notify you about all bugs in that package via email.
Now you do the following steps:
Wow, that's a way more useful list, isn't it? You now have all bugs for packages you care for that need triaging.
As a developer, you are of course interested in all already triaged bugs in packages you care about. The way is exactly the same, follow the instructions above and search for bugs in the 'confirmed' and 'triaged' state.
Similar, you might want to query all bugs you are assigned for:
On the flip side, this works for other developers as well. In effect, using these queries, it should be possible to generate per developer reports of their pending backlog of bugs they should look at.
tech english ubuntu
~~DISCUSSION~~