Hi, folks! It's been noted a few times before that we have a release criterion that requires *updating* packages (or, these days, 'software', to cover things like modules) to work...but we don't have criteria covering other basic software management tasks, notably installing and removing. There is a possible justification for this: so long as update works, bugs in installation and removal can be fixed with updates. But really, it seems reasonable to me that we should require basic installation/removal of packages (and modules, and anything else we may choose to consider release critical now or in future, e.g. flatpaks, Shell extensions...) to work on release. So, I'm proposing we modify the existing Basic and Beta criteria that cover only updates, to also cover installation and removal. I like this a bit more than adding separate criteria as the footnotes would be very similar, and combining allows the footnotes to be shared. So, the Basic criterion would change from: "The installed system must be able to download and install appropriate updates with the default console tool for the relevant update type (e.g. default console package manager)." to: "The installed system must be able to install, remove, and install appropriate updates for software with the default console tool for the relevant software type (e.g. default console package manager). This includes downloading of packages to be installed/updated." the Beta criterion would similarly change from: "The installed system must be able to download and install appropriate updates with the default tool for the relevant update type in all release-blocking desktops (e.g. default graphical package manager)." to: "The installed system must be able to install, remove, and install appropriate updates for software with the default tool for the relevant update type in all release-blocking desktops (e.g. default graphical package manager). This includes downloading of packages to be installed/updated." the footnotes would be tweaked to refer more generically to 'software' and stuff instead of 'updates', just kinda logical changes to reflect the broadened criterion; I can go into detail on that if anyone wants. Obviously if the criterion change is agreed upon, we will add test cases to the test matrices. Thoughts, comments, suggestions, acks and nacks? Thanks! -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx/message/LQIXML42QXJLFJWOYMYXW36QNWFG4FII/
