QA:Testcase_desktop_updates (notifications) failure on KDE

[Adam Williamson]

On Sat, 2015-03-28 at 21:07 +0100, Giulio 'juliuxpigface' wrote:
> > Giulio 'juliuxpigface' wrote:
> > 
> > > Hi guys,
> > > 
> > > I've just reported the bug
> > >  https://bugzilla.redhat.com/show_bug.cgi?id=1206760encountered 
> > > while I
> > > was testing the behavior of a freshly-installed Beta-TC5 with 
> > > KDE. As
> > > you surely know, this is described by part of
> > > "QA:Testcase_desktop_updates" and is one of the cases listed 
> > > under
> > > "Release-blocking desktops: x86 / x86_64".
> > > 
> > > What am I exactly supposed to do now? Should I propose it as a 
> > > "blocker"
> > > or "freeze exception"?
> > 
> > Yes, it's a blocker, but hopefully it won't come to that (the 
> > proposed 
> > updater replacement just got stable autokarma in -testing).
> > 
> > -- Rex
> > 
> 
> Hi Rex,
> 
> thank you for your answers (both here and on bugzilla).
> I apologize for the questions, but as I keep saying I'm new and I'm
> still learning.
> 
> 1) Is there anything further I should do with the bug-report? Are 
> other
> steps required or it's ok as it is now?
> 
> 2) Then; sorry but I didn't understand... Should I mark the failure 
> as a
> blocker, even though the bug it's now solved?

Hi Giulio! Thanks for reporting the bug. It's usually safe to err on 
the side of nominating the bug as a blocker if you're not sure - you 
can never cause a major problem by nominating a bug as a blocker, the 
worst that can happen is it takes us five minutes to review it in the 
meeting.

In this case, as the update is already being pushed stable, there's no 
need to treat it as a blocker, but it's always fine to nominate it 
just in case, so don't worry :)
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net