https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Default_application_functionality "Basic functionality means that the app must at least be broadly capable of its most basic expected operations, and that it must not crash without user intervention or with only basic user intervention." a. I take "basic functionality" as a compound noun, equivalent to "fundamental purpose". b. If the package manager has a reproducible crash, it's a blocker. I'm having difficulty parsing the double negative above. Does it means "it may crash with non-basic user intervention"? I have no idea how to categorize basic and non-basic interventions. Insofar as this applies to GNOME Software and KDE Discover, anything a GUI application lets a user do, is in the course of achieving its fundamental purpose. I'd say any bug that is not a cosmetic bug is a release blocking bug for these components, when the problem is experienced on a release blocking desktops. I'd be OK distinguishing between two categories: bugs with a documented workaround are OK for beta; but only cosmetic bugs are OK for final. Also, a suitable error message indicating that a requested action can't be completed, along with a hint for an alternative course of action, requires a high burden to make the error a blocker bug (not impossible but it's a higher bar than just silently failing, crashing, or leaving the system in some disfunctional in between state). If some offered functionality doesn't work, fix it or rip it out. -- Chris Murphy _______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
