Unity 7 & Compiz bug triage
Alberto Salvia Novella
es20490446e at gmail.com
Tue Aug 18 16:50:22 UTC 2015
Stephen M. Webb:
> Focusing on simply setting importance or on confirmed bugs is not
> working well enough for Unity.
When the software is under as much use as Unity 7 is, nearly all new
bugs are false or minor. If you want to make sure the incoming Ubuntu
release is stable, it's rather productive to ask people to have a look
around it, try to break Unity on it in every corner, and to confirm the
bugs they see. More productive than confirming a pool of hundreds of
false reports.
Stephen M. Webb:
> Most of these bugs are in the form 'Unity mysteriously crashed for no
> reason' and has been autoconfirmed because someone saw it and clicked
> 'affects me' -- they also saw a crash window pop up for no reason.
What I'm suggesting is setting importance without validating the bug.
Because its status will still be untriaged and everyone will understand
nobody has validated it. Then the prioritization will give a guide on
where to start validating.
Stephen M. Webb:
> With well over 3000 bugs in the entire stack, just a simple linear
> iteration for an individual to determine the importance of a bug is
> untenable.
That's why I'm suggesting working in confirmed bugs or also tagged with
supported releases. On these we have the following scenario:
<https://bugs.launchpad.net/unity/+bugs?&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=UNDECIDED&field.tag=wily+vivid+trusty&orderby=-heat>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6472 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20150818/6b9da6b9/attachment.bin>
More information about the Ubuntu-bugsquad
mailing list