On Wed, 2016-12-07 at 08:49 -0500, Kamil Paral wrote: > I think there are two things combined. The first one is blocking > status. I'd like to have blocking status set exactly for that > milestone which we believe it should block (and not an earlier one, > just in case). The second thing is detection. We should be able to > detect these issues early in the process, but we often don't, and we > can talk about improvements here. I usually strive to avoid the > situation where we test a Final test case for the first time only > after Beta release (or with Final RC1). That's too late. Yeah, this is something I try to push every cycle. We do post repeated reminders that *all* tests should be run on Alpha / Beta composes, not only the tests for Alpha / Beta criteria. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
