Subject: Bugs

From: Daniel van Vugt <[email-masked]>
Date: Wed, 04 Dec 2013 14:30:14 +0000

All,

Several times recently, people have been talking about issues that 
already have bugs for them, but people are not familiar with the bugs.

It's probably a good idea to familiarize yourself with at least the most 
severe bugs:
     https://bugs.launchpad.net/mir/+bugs
     https://bugs.launchpad.net/xmir/+bugs
     https://bugs.launchpad.net/unity-system-compositor/+bugs

- Daniel

---

From: Ricardo Salveti <[email-masked]>
Date: Wed, 11 Dec 2013 02:02:07 -0200

On Wed, Dec 4, 2013 at 12:30 PM, Daniel van Vugt
<[email-masked]> wrote:
> All,
>
> Several times recently, people have been talking about issues that already
> have bugs for them, but people are not familiar with the bugs.
>

Do you know if we also have someone doing bug triaging for the
package-specific launchpad tasks (and maybe linking them with the
upstream projects)?

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

Cheers,
-- 
Ricardo Salveti de Araujo

---

From: Daniel van Vugt <[email-masked]>
Date: Wed, 11 Dec 2013 12:05:45 +0800

I try to do so every day. Was something missed?

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.

---

From: Ricardo Salveti <[email-masked]>
Date: Wed, 11 Dec 2013 02:11:10 -0200

> 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 :-)

> 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,

---

From: Daniel van Vugt <[email-masked]>
Date: Wed, 11 Dec 2013 12:18:16 +0800

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.

---

From: Oliver Ries <[email-masked]>
Date: Wed, 11 Dec 2013 03:23:09 -0700

On Tue, Dec 10, 2013 at 9:18 PM, Daniel van Vugt <
[email-masked]> wrote:

> 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.
>

just a random comment (oh beware...:)

I think it's flawed if a project (e.g. Mir) does not actively look at the
bugs of it's key consumer (i.e. Ubuntu). I really appreciate Daniel's
effort in triaging all the bug, but that might be an issue if/when he is
going on vacation etc.

@mir-developers, I would suggest that you make this a team effort to
support Daniel in this task.

@Daniel, do you have some documentation to guide new contributors in that
effort? (thinking of coordinated use of states, importance etc)

thx
Olli

>>> that
> Mir-devel mailing list
> [email-masked]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/mir-devel
>

---

From: Daniel van Vugt <[email-masked]>
Date: Wed, 11 Dec 2013 18:44:25 +0800

I don't think there's anything different about the Mir project. Just the 
standard Ubuntu instructions. All the relevant links are here:

https://wiki.ubuntu.com/HelpingWithBugs

On 11/12/13 18:23, Oliver Ries wrote:
> On Tue, Dec 10, 2013 at 9:18 PM, Daniel van Vugt
> <[email-masked] <mailto:[email-masked]>>
> wrote:
>
>     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/mir/+bugs>
>     https://bugs.launchpad.net/__ubuntu/+source/mir/+bugs
>     <https://bugs.launchpad.net/ubuntu/+source/mir/+bugs>
>     https://bugs.launchpad.net/__xmir/+bugs
>     <https://bugs.launchpad.net/xmir/+bugs>
>     https://bugs.launchpad.net/__ubuntu/+source/xmir/+bugs
>     <https://bugs.launchpad.net/ubuntu/+source/xmir/+bugs>
>     https://bugs.launchpad.net/__unity-system-compositor/+bugs
>     <https://bugs.launchpad.net/unity-system-compositor/+bugs>
>     https://bugs.launchpad.net/__ubuntu/+source/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.
>
>
> I think it's flawed if a project (e.g. Mir) does not actively look at
> the bugs of it's key consumer (i.e. Ubuntu). I really appreciate
> Daniel's effort in triaging all the bug, but that might be an issue
> if/when he is going on vacation etc.
>
> @Daniel, do you have some documentation to guide new contributors in
> that effort? (thinking of coordinated use of states, importance etc)
>
> thx
> Olli
>
>
>
>
>         <[email-masked]
>         <mailto:[email-masked]>__> wrote:
>
>     [email-masked] <mailto:[email-masked]>
>     Modify settings or unsubscribe at:
>     https://lists.ubuntu.com/__mailman/listinfo/mir-devel
>     <https://lists.ubuntu.com/mailman/listinfo/mir-devel>
>
>

---

From: Timo Aaltonen <[email-masked]>
Date: Wed, 11 Dec 2013 16:43:45 +0200

> https://bugs.launchpad.net/ubuntu/+source/xmir/+bugs

this doesn't exist

-- 
t

---

From: Kevin Gunn <[email-masked]>
Date: Wed, 11 Dec 2013 09:49:11 -0600

I think Daniel meant this
https://bugs.launchpad.net/ubuntu/+source/mir/+bugs

As you can imagine, I also triage. And I try to be hygienic about both the
upstream bugs & ubuntu project-mir bugs. And agree with Olli, its not just
for managers...we all benefit. If nothing else carve out some time to look
at triaged high/critical bugs and new/untriaged bugs.
This isn't to say medium/low priority is a black hole, but I would leave
that to management to do a monthly review of those.

br,kg

On Wed, Dec 11, 2013 at 8:43 AM, Timo Aaltonen <[email-masked]> wrote:

> https://lists.ubuntu.com/mailman/listinfo/mir-devel
>

---

From: Daniel van Vugt <[email-masked]>
Date: Thu, 12 Dec 2013 14:45:40 +0800

:)

Correction; XMir is in:
https://bugs.launchpad.net/xmir/+bugs
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bugs

---

From: Timo Aaltonen <[email-masked]>
Date: Thu, 12 Dec 2013 11:18:59 +0200

> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bugs

yes, looks better :)

also, during saucy we got a bunch of crashers against
xserver-xorg-video-intel that turned out to be due to xmir. Is running a
full xmir session still supposed to be supported? I'd expect not, now
that we're not doing that by default. From what I understand the
situation with rootless xmir is much different and shouldn't hit (all)
these issues..

-- 
t

---

From: Daniel van Vugt <[email-masked]>
Date: Thu, 12 Dec 2013 17:21:36 +0800

XMir support is still in distro. It's not in a form that represents the 
end goal, but I don't think we had plans to remove it either.

Some users report that XMir is useful in smoothing out their desktop 
experience... where the default X driver doesn't page flip as nicely as 
Mir does (!?). So it does have users :)