Hi Ben, Thanks for starting the discussion.
I agree with the intent. This has been a topic of discussion within the Fedora QA team for a while now and we have made some efforts to engage SIGs early in the cycle. As far as the question of when the testing should be a focus from respective SIGs? In my humble opinion, it should be continuous and should be a priority in their respective upstream. SIGs start testing during RC will act as a helping hand but it won't prevent late findings of issue. Cheers, Sudhir On Tue, Mar 29, 2022 at 1:28 AM Ben Cotton <bcot...@redhat.com> wrote: > Hi friends, > > I was a little concerned that we were running some tests during the > Go/No-Go last week, especially considering it seemed like we had most > of the blockers wrapped up well ahead of when we normally do. Part of > the answer, in my opinion, is to lean on some of the SIGs/WGs to take > a more active role in the testing process for RCs and the period > leading up to RCs. > > In particular, I'd like to see the Server WG taking care of the Active > Directory tests (which is a non-trivial thing to remove our dependence > on sgallagh's setup, admittedly) and the Cloud SIG taking care of many > of those tests. The fact that we didn't have any AWS AMIs uploaded > until after the meeting started suggests there's a gap in our process. > And of course, pwhalen and coremodule could always use more support in > running ARM tests. > > This isn't a criticism of the QA team, because y'all do a tremendous > job. And I don't want to suggest that _all_ of the testing be pushed > out onto other teams. But I'd like to start a conversation on how we > can spread the responsibility out more. This should hopefully make > everyone's life a little easier and make our Go/No-Go meetings more > efficient to boot. > > Thoughts? > > -- > Ben Cotton > He / Him / His > Fedora Program Manager > Red Hat > TZ=America/Indiana/Indianapolis > _______________________________________________ > test mailing list -- test@lists.fedoraproject.org > To unsubscribe send an email to test-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- S*UDHIR D* SENIOR MANAGER, FEDORA QE,
_______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
