On Thu, Sep 11, 2025 at 8:14 PM Adam Williamson <adamw...@fedoraproject.org>
wrote:

> The nightly events are all announced to a similarly long set of mailing
> lists.


And again, I had no idea :-D


> I don't know what we can do to make it clearer to people that,
> yes, we really need tests of those. Thoughts?
>

I think the current announcements are easy to mentally filter out, because
they are frequent, regular, and templated. "Just a machine-generated
announcement, I don't care about those". I was hoping a more personalized
email like the one I sent would draw more attention. I have no idea if it
did, though.

There are a few ideas we can try:
a) send out *fewer* "compose nominated for testing" emails to team lists.
That will make them stand out more when they actually appear. For example
we can drop all the rawhide ones (just send them to test-announce), and
send them to team lists only after branching.
b) add a few "human" emails during the release cycle (it doesn't mean they
can't use a template, but we can try to make them feel less like that)
c) make some special views in testcase stats which would show only relevant
areas to a specific team (so server-related test cases for the Server team,
etc). It would then be very easy for them to check what the current
coverage is.
d) add statistics to our emails that list the current coverage per team
(e.g. 30% of required test cases last tested more than a month ago), that
could give urgency to areas which need it
e) create occasional tickets in team trackers if the coverage is low and
the milestone is approaching

To be honest, I ignore those "compose nominated for testing" emails myself
as well, unless we're getting close to a milestone. Nobody will spend time
testing throughout the year again and again, that's machines' job. It makes
sense that humans get involved close to the cycle end, when the priority of
"milestone incoming" exceeds the priority of "whatever I'm doing
regularly". So we should probably tailor the messaging as well, to make it
more meaningful.
-- 
_______________________________________________
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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to