Mir bug importance
Daniel van Vugt
daniel.van.vugt at canonical.com
Tue Sep 10 02:40:13 UTC 2013
That's also not accurate. If a bug has crept into distro then it should
have a distro task: "mir (ubuntu)"
This is necessary to distinguish between a fix that has landed in
upstream Mir, but not yet landed in Ubuntu distro.
On 10/09/13 10:35, Robert Ancell wrote:
> Also worth mentioning about bugs:
> I've been moving all the Ubuntu bugs against Mir to Mir project bugs.
> This is what the software center team did as it makes it simpler to just
> have one bug list.
> On Tue, Sep 10, 2013 at 2:07 PM, Daniel van Vugt
> <daniel.van.vugt at canonical.com <mailto:daniel.van.vugt at canonical.com>>
> As we focus on the most severe bugs, it's worth discussing what bug
> severity actually is. I don't want to confuse everyone with a
> detailed examination/discussion/__argument. But to start with, I
> think we need to agree on what "Critical" means...
> Normally critical means that the system is unusable . Good
> examples of definitely critical bugs are:
> "Mir/unity-system-compositor fails to start: Error opening DRM device"
> "[radeon] Graphic glitches and screen corruption (vertical lines) on
> XMir surfaces only"
> These are bugs which prevent the machine from being usable. But if
> it's not that bad, then please consider marking bugs as High or Medium.
> - Daniel
>  https://wiki.ubuntu.com/Bugs/__Importance
> Mir-devel mailing list
> Mir-devel at lists.ubuntu.com <mailto:Mir-devel at lists.ubuntu.com>
> Modify settings or unsubscribe at:
More information about the Mir-devel