On Thu, Apr 20, 2023 at 11:39 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote:
Is there a way we can add regular testing for it without making it a
blocker then?
For popular third-party software, I think this testing occurs quite naturally - people just use it. E.g. Steam, Chrome, VSCode, etc. I've been running Steam on F38 since Beta (and it helped me to discover an issue in mutter, which was later accepted as a blocker - but not because of Steam, but because of general issues). But if you want to have an explicit test case, Adam described how to do it. We could also have a test day for popular third-party software, if it makes sense.
Note that we had proprietary software-related blockers in the past. We accepted the EAC glibc issue as a blocker in one of the recent releases. We also accepted the RPM signatures change as a blocker for F38. But in these cases, it was always accepted as an exceptional blocker confirmed by FESCo. I guess it makes sense to use this exceptional process for these cases (blocking on issues with third-party software, which can affect our user base badly). We could talk about some general rule related to popular third-party software, but that would again need to go through FESCo. At the moment, we only block on our own code in our own workflows, with a few very specific exceptions (boot usb creation, dual boot configuration, cloud images deployment).
_______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
