On Thu, 2022-01-20 at 14:17 -0500, John Mellor wrote:
The suggested criteria list is pretty generic, and offhand I
can't think
of a current GUI or CLI installer that does not conform to these
requirements.
Just before Fedora 35 was released, the KDE package manager did not
conform to several of them:
https://bugzilla.redhat.com/show_bug.cgi?id=2015809
https://bugzilla.redhat.com/show_bug.cgi?id=2011322
https://bugzilla.redhat.com/show_bug.cgi?id=2015491
https://bugzilla.redhat.com/show_bug.cgi?id=2011291
https://bugzilla.redhat.com/show_bug.cgi?id=2011333
It was largely these and a few other bugs that motivated us to draft
these criteria.
As I mentioned in my other mail, the point of the release criteria is
to specify a subset of expected functionality which is so important we
should block the release if it's not met. It's not *meant* to contain
anything novel or unexpected. *Everything* in the release criteria
should be "the way it's supposed to work already". What we're doing
with the release criteria is saying "if these things *don't* work the
way they're intended to, that's bad enough that we shouldn't ship the
release".
What this list does NOT cover are the pain points of the current
product, such as avoiding reboots.
Yes, because reboots are a part of the way it's supposed to work. It
would be wrong for the release criteria to say "there shouldn't be any
reboots" if some of the package managers the distribution has chosen to
use have chosen to require reboots on updates, and the distribution has
decided that it's fine with that (as we have). Release criteria are not
tools for advocacy about how we we like the software to work. That
should be done elsewhere.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net