Our purpose in this meeting is to review
proposed blocker and nice-to-have bugs and decide whether to accept
them, and to monitor the progress of fixing existing accepted
blocker and nice-to-have bugs.(adamw,
17:13:21)
We'll be following the process outlined
at:(adamw,
17:13:25)
AGREED: 2032085 -
punt (delay decision) - we don't think this qualifies as a blocker
under the release criteria currently, but there seems to be a strong
case for FESCo to declare it a blocker as current state is not at
all how we want things to be, and this is an important area. so
instead of rejecting, we will file a ticket for FESCo to consider
declaring it a blocker (as they are allowed to do)(adamw,
17:24:52)
(2017043) GNOME doesn't accept input from wireless keyboard if there's not another "keyboard" input available(adamw, 17:25:08)
AGREED: 2017043 -
AcceptedBlocker (Beta) - accepted as a conditional violation of "A
system installed with a release-blocking desktop must boot to a log
in screen where it is possible to log in to a working desktop using
a user account created during installation or a 'first boot'
utility" (can't log in or create user if you can't type) on affected
systems (aarch64 with multi-capability input device)(adamw,
17:43:57)
AGREED: 2008179 -
RejectedBlocker (Beta) AcceptedFreezeException (Beta) - this does
not appear to violate any Beta criteria, but it's useful
functionality and would be a showstopper for anyone using it on F35
who upgrades to F36, so accepted as an FE issue(adamw,
18:09:06)
AGREED: 2050615 -
RejectedBlocker (Final) - this bug appears to be specific to the
cups-pdf virtual printer, which isn't actually covered by the
criteria. We will revisit if it turns out to affect GNOME's or KDE's
built-in PDF printing features, or a real physical printer. we'll
consider whether and how to adjust the openQA tests as well(adamw,
18:34:17)
(2049849) Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader(adamw, 18:34:28)
AGREED: 2049849 -
AcceptedBlocker (Final) - accepted as a conditional violation of
Final criterion "The installer must be able to install into free
space alongside an existing clean Windows installation and install a
bootloader which can boot into both Windows and Fedora" in the case
of Windows being installed with Bitlocker enabled (as is
increasingly common). We recognize this is technically difficult to
fix and may change or defer(adamw,
18:59:54)
AGREED: 2020759 -
AcceptedBlocker (Final) - accepted as a violation of Final criterion
"There must be no SELinux denial notifications or crash
notifications on boot of or during installation from a
release-blocking live image, or at first login after a default
install of a release-blocking desktop."(adamw,
19:07:28)
(2042877) crash happens on the newly installed system(adamw, 19:08:31)
AGREED: 2042877 -
punt (delay decision) - other testers have not immediately been able
to reproduce this, we will ask lili for more details on the scenario
and try again to reproduce(adamw,
19:14:40)
(2006393) [DNS over TLS] following connection to a wifi AP, internet is not available for ~30s(adamw, 19:14:59)
AGREED: 2006393 -
punt (delay decision) - this is an automatic transfer from F35 and
we don't know the exact status of F36 currently wrt this bug.
delaying decision to ask cmurf to report back on how F36 is(adamw,
19:22:24)