Comment 2 for bug 1456271

I understand the theory of the multiple bug lists: I was a Launchpad developer 2005~2008. The idea was that by tracking upstream and distribution bugs separately, the developers of one could easily see when the developers of the other had fixed a bug they shared, and merge or cherry-pick the fix as appropriate. And that the benefits of doing this would outweigh the costs of misfiling and misprioritization caused by multiple bug lists with multiple importance levels and assignees.

But with unity-system-compositor you don't *have* multiple distributions with developers who ever fix bugs independently from upstream. (unity-system-compositor isn't even in Debian!) Maybe someday that will change. But right now, keeping separate lists inflicts all the costs and none of the benefits.