Bugs

Daniel van Vugt daniel.van.vugt at canonical.com
Wed Dec 11 10:44:25 UTC 2013


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
> <daniel.van.vugt at canonical.com <mailto:daniel.van.vugt at canonical.com>>
> 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.
>
>     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.
>
>
> 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
>
>
>
>
>     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
>         <mailto: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,
>
>
>     --
>     Mir-devel mailing list
>     Mir-devel at lists.ubuntu.com <mailto:Mir-devel at lists.ubuntu.com>
>     Modify settings or unsubscribe at:
>     https://lists.ubuntu.com/__mailman/listinfo/mir-devel
>     <https://lists.ubuntu.com/mailman/listinfo/mir-devel>
>
>



More information about the Mir-devel mailing list