On Tue, Mar 29, 2022 at 12:05 AM Sudhir Dharanendraiah
<sdharane(a)redhat.com> wrote:
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.
Oh, great! I must have missed those conversations. If there's anything
I can do to help from a program management perspective, please let me
know.
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.
I totally agree in theory. In practice, a lot of contributors are
volunteers. I'd love to get to the point where the testing is
continuous, but getting them to test the RCs more would be an
improvement over where we are now.
On Wed, Mar 30, 2022 at 10:12 AM Kamil Paral <kparal(a)redhat.com> wrote:
I'm not sure if those mentioned parties read this list and will respond :-) But yes,
in general, it would be nice to see more people from various SIGs to get involved.
I assume everyone has all of the mailing lists beamed directly into
their brain. :-D But yeah, I wanted to start the conversation within
the QA team to figure out how we can rope them in before we engage
with the SIGs. For example, do the RC announcements (e.g. [1]) go to
the right places? I see some SIGs receive it, but Cloud doesn't seem
to. And there's no clear call-to-action for the SIGs. That could be a
low-effort way to potentially improve engagement from SIGs.
[1]
https://lists.fedoraproject.org/archives/list/test-announce@lists.fedorap...
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis