Comment 9 for bug 91013

Last time we discussed this it was agreed that there should be a single Launchpad product, not several. The only reason for having several was limitations in blueprint (which have hopefully been fixed by now), as it did not have tags like Malone. And this is the only reason they haven't already been merged into a single one.

Having multiple products for the single code base causes lots of other problems, as we are using Launchpad in a way it was not intended. In particular, branches - if a branch is registered against the 'Launchpad' product, it is problematic linking it to soyuz bugs or rosetta specs. I'm aware of at least one feature currently being worked on by Tim that we want for Launchpad, but will be unable to use until the lp products are collapsed into a single one.

If we can't use Launchpad the way it was intended, we need to redesign it rather than trying to work around these issues, and work around the new issues the work arounds create, ad infinitum.