I understand the intention and it's wonderful. I remember proposing multi-dimensional bug tracking/tasks in a former job for similar reasons (multiple supported releases and multiple vendor variants of a single product).
Although even with a single distro you still need separate bug tasks. That clearly delineates a bug fix that exists upstream from one that has made it into a package release. And in Mir we have an additional use: A bug that exists in "Mir" might be Invalid in Ubuntu if it was regressed, found and fixed all within a single cycle.
You only need one motivated bug triager to keep things up to date. The Mir project has that, but sadly USC does not. I feel I will care about this in the future and when that happens I'll end up being the maintainer for USC bugs. But until then, *shrug*.
I understand the intention and it's wonderful. I remember proposing multi-dimensional bug tracking/tasks in a former job for similar reasons (multiple supported releases and multiple vendor variants of a single product).
Although even with a single distro you still need separate bug tasks. That clearly delineates a bug fix that exists upstream from one that has made it into a package release. And in Mir we have an additional use: A bug that exists in "Mir" might be Invalid in Ubuntu if it was regressed, found and fixed all within a single cycle.
You only need one motivated bug triager to keep things up to date. The Mir project has that, but sadly USC does not. I feel I will care about this in the future and when that happens I'll end up being the maintainer for USC bugs. But until then, *shrug*.