On Mon, Nov 8, 2021 at 11:39 AM Kamil Paral kparal@redhat.com wrote:
On Mon, Nov 8, 2021 at 4:28 PM Chris Murphy lists@colorremedies.com wrote:
https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Default_appl...
"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"?
Yes, I believe it says that.
I have no idea how to categorize basic and non-basic interventions.
With much difficulty, that's why we're having this thread :-)
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.
"anything a GUI application lets a user do" is a potential trap. You can submit app ratings in gnome-software, and I'm quite sure we don't want to block the release on that. That's why I proposed an exact list.
When installing, removing, or updating software? If I click an install button, the selected app should be installed or it's a blocking bug. Same for removal, same for updating. If it lets you click install for multiple programs in sequence, they should all be successfully installed. If that's not possible, then don't let users queue up multiple programs for installation.
I agree that if it crashes when submitting app ratings, I'd consider it cosmetic.