In the test list at:
https://fedoraproject.org/wiki/Test_Results:Fedora_32_Branched_20200212.n.1_Desktop
There are 27 rows of things to test on between 1 and five platforms.
Even given that much of the testing is automated. You still need test
engineers to keep that all updated, running, and check the results. Also
there are still many things that need testing by people. Though VMs are
handy for that, there is a need for some real bare metal hardware testing.
All the above only covers Desktop. So there a huge amount of
testing/validation to be done.
Forgive me for starting to sound like a manager: Clearly the composes
that RHEL draws from are where effort must be put first. With a
relatively fixed staffing, everything else needs to be prioritized. Some
will need to be classified as something like "best effort", "automation
tests only", or "development compose use at your own risk". This is
especially true given that at lease one composes wants to step up the
testing / quality.
From my view in the nosebleed seats. I don't think it's possible with
the large volume of composes to have everything qualify as battle
hardened. An old well proven industrial truth: Sometimes small groups of
"customers" have to be dropped or disappointed so you can do a superb
job for the big "customers".
I know this is a very strict view and we'll probably end up somewhere
between this and the current situation, but I think some movement is needed.
Have a Great Day!
Pat (tablepc)
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
