On Mon, Sep 17, 2018 at 9:56 AM, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > On Mon, 2018-09-17 at 17:25 +0200, Kamil Paral wrote: >> On Mon, Sep 17, 2018 at 2:45 PM Stephen Gallagher <sgallagh@xxxxxxxxxx> >> wrote: >> >> > On Mon, Sep 17, 2018 at 5:16 AM Petr Šabata <contyk@xxxxxxxxxx> wrote: >> > >> > > I hope this won't just mean we discover the problems later, in practice. >> > >> > The policy of Fedora QA is to run all of the GA-blocking tests at Beta as >> > well. >> > >> >> My goal has always been to run all Final testcases with the publicly >> released Beta image as soon as possible. I don't think we're too successful >> at running all Final testcases with pre-Beta images or Beta RCs. I'm not >> aware of any policy per say. But we certainly try. > > I've been saying for a long time that we ought to be doing that, and > it's why we started doing validation events for nightly composes > throughout the cycle (instead of starting shortly before Alpha as we > used to). I definitely would like us to be running the validation tests > a long time before Beta freeze. Maybe there needs to be a milestone for it? Something like alpha in terms of the timing, but non-blocking since there's no release specific to this hypothetical milestone, but does give you the resources to plan for and implement it. -- Chris Murphy _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
