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:07:43)
We'll be following the process outlined
at:(adamw,
17:07:44)
AGREED: 1683197 -
AcceptedBlocker (Beta) - for now we accept this as a violation of
the cited criterion, note further testing on bare metal systems may
cause a re-evaluation if the bug turns out not to happen in some
cases(adamw,
17:17:32)
(1673710) [abrt] virt-manager: gst_caps_set_simple_valist(): python3.7 killed by SIGSEGV(adamw, 17:17:42)
AGREED: 1673710 -
AcceptedBlocker (Beta) - accepted as a violation of "The release
must be able host virtual guest instances of the same release". We
note that using VNC can be considered a 'workaround', but still
think the bug is a blocker, and note that it is not straightforward
to do this in Boxes and it is not equal in quality to the default
config(adamw,
17:25:29)
AGREED: 1684612 -
AcceptedBlocker (Beta) - accepted as a violation of "The default
desktop background must be different from that of the last two
stable releases" (the new package needs to be approved, built and
pushed in order to meet that criterion)(adamw,
17:30:03)
AGREED: 1684808 -
AcceptedFreezeException (Beta) - this bug makes it hard to read the
installer in MATE and obviously cannot be fixed with an
update(adamw,
17:36:56)
(1600444) Wrong conflicts between dnf and yum prevents upgrade(adamw, 17:37:02)
AGREED: 1600444 -
AcceptedFreezeException (Beta) - accepted as this interferes with
upgrades in a common case. Granting an FE allows a fix to go to F30
stable during freeze, so upgrades run without updates-testing
enabled (the usual case) during freeze period will not hit the
bug(adamw,
17:49:18)
(1677732) "Advanced Network Configuration" appears in "X-GNOME-Sundry" folder(adamw, 17:49:27)
AGREED: 1677732 -
AcceptedFreezeException (Beta) - this will be visible and confusing
in the Workstation live, so it's worth fixing and cannot be fixed
with an update(adamw,
17:55:37)
the fix for this is built and tagged f30 so
will be in any future composes, thus no practical need to consider
this bug, we will close it(adamw,
18:01:27)