ubuntu-phone team mailing list archive

[Łukasz 'sil2100' Zemczak <lukasz.zemczak@xxxxxxxxxxxxx>]

Hi!

W dniu 30.07.2014 o 22:53, Steve Langasek pisze:
> On Wed, Jul 30, 2014 at 09:16:33PM +0100, Brendan Donegan wrote:
>>> * Blocking issues:
> 
>>> ** [mako #158] apparmor denies access to /etc/ssl/openssl.cnf
>>> https://bugs.launchpad.net/bugs/1350152
>>>  -> Issue fixed in the archive, next image should have this fixed
> 
>>> ** test_note_focus_on_second_click_outside failed on mako #159
>>> https://bugs.launchpad.net/bugs/1350361
> 
>> This should go in 'Issues not impacting User Experience'. Also according
>> to the process, doesn't it only become a blocker after 7 images?
> 
> FWIW I was going to mark this as a "critical" bug in Launchpad, but then I
> saw that it had also been tagged "lt-prio-low".  So now I'm confused. 
> Łukasz, can you clarify please?  If it's truly a blocker, I can't see how it
> should be considered "low".
> 
> Thanks,
> 
> 
> 

So, the reason for things to be like this are: as per Alexander's
request, every autopilot failure that is constantly reproducible should
become a blocker by nature. This can be then whitelisted (removed from
the blocker list) by us if we see that it's not breaking anything in
particular. The reason its priority is set to low is because if the
nature of issue.

I'm not particularly fond of this approach, but it does make sense
somewhat. The 7 day period is for flaky tests that we cannot reproduce
locally but are, for instance, appearing on the dashboard. The 7 day
period is also usable whenever we decide that the issue does not shadow
any visible regressions and remove it from the blocker list temporarily.
This way the issue does not get forgotten.

Best regards,

-- 
Łukasz 'sil2100' Zemczak
 lukasz.zemczak@xxxxxxxxxxxxx
 www.canonical.com