Using Launchpad as main QA tool

Why are we doing this?

Improve how we do QA today, by:
- Being able to search items dynamically using Launchpad search and Launchpad API
- Not forcing developers to edit the wiki pages to do their QA
To reduce/eliminate the number of orphaned commits per cycle.
To make easier and more reliable to gather stats of the cycle

Running an automated script that watches the main development branches analysing the commits one by one, as the current test-plan tool does, but instead of adding all items to the wiki test plans, it marks the mentioned bug as Fix Committed in Launchpad, adds a comment to it documenting which commit was responsible for that status change, and adds the qa-needstesting tag. If the commit is an orphaned one, it adds to the team wiki page as a fallback.
All the orphaned commits need to be handled by creating one bug for it. The goal is to eliminate orphaned commits per cycle.
The search for items to QA to a given person can be done through an advanced bug search in Launchpad:
- with Fix Committed or Fix Released status
- with qa-needstesting tag
- that are assigned to you
- Don't hide duplicates (some bugs fixed may be dupes of others and not show as pending)