Bugs

[Daniel van Vugt]

Yeah, we had a rude shock when people started using XMir last cycle. 
Bugs were piling up against the package tasks for some time, invisible 
to the upstream projects and invisible to mir-team. Now we're aware of 
it I think it's under control.

Anyone who wants to see all Mir bug reports should subscribe to all Mir 
bug sources:

https://bugs.launchpad.net/mir/+bugs
https://bugs.launchpad.net/ubuntu/+source/mir/+bugs
https://bugs.launchpad.net/xmir/+bugs
https://bugs.launchpad.net/ubuntu/+source/xmir/+bugs
https://bugs.launchpad.net/unity-system-compositor/+bugs
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bugs

A bug report in any of those could of course be a Mir bug. Users rarely 
file against the right project/package first time.


On 11/12/13 12:11, Ricardo Salveti wrote:
> On Wed, Dec 11, 2013 at 2:05 AM, Daniel van Vugt
> <daniel.van.vugt at canonical.com> wrote:
>> I try to do so every day. Was something missed?
>
> Nothing specifically, just checking as we had some bad experience with
> a few canonical-upstream projects in the past (people not checking the
> packaging bugs at all).
>
> Thanks for taking care of those bugs :-)
>
>> mir-team likely won't see most of the bug traffic because it wasn't
>> subscribed to them last I checked. Robert Ancell said he preferred it that
>> way, so people could opt-in. It's harder to opt-out. Although I personally
>> think mir-team should be subscribed to all Mir bug sources.
>
> Yeah, I see no reason why the mir-team would only track bugtasks
> assigned to the upstream project, as ideally we want trunk to be in
> sync with the package anyway.
>
> Thanks,
>