adamwill's meeting titled "Fedora QA Meeting" ended in #fedora-meeting
by notifications@fedoraproject.org
Notification time stamped 2019-05-27 16:02:02 UTC
==================================
#fedora-meeting: Fedora QA Meeting
==================================
Meeting started by adamw at 15:00:06 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2019-05-27/fedora-qa.201...
.
Meeting summary
---------------
* Roll call (adamw, 15:00:14)
* Previous meeting follow-up (adamw, 15:06:00)
* "sgallagh to add lruzicka to the invite list" - this was about
module behaviour issues. there was one meeting about this with some
progress, not all points are decided, there will be another such
meeting on thursday (adamw, 15:08:21)
* some action items from meeting before last (adamw, 15:10:42)
* "adamw to revise F30 Common Bugs for Final" - this was done, ongoing
revisions will continue until morale improves (adamw, 15:11:01)
* "adamw to resurrect the 'late blocker waiver' proposal with a third
draft or re-send of the second draft" - I did not manage to do this
before I went on holiday, but Patrick Kelly has done it instead and
the decision is ongoing (thread "Last-minute blocker bugs") (adamw,
15:12:02)
* Fedora 31 status / Change review (adamw, 15:15:06)
* Fedora 31 is generally in decent state right now, a bug affecting
install of KDE package sets was recently resolved (adamw, 15:24:35)
* several Changes look like they may be significant risk factors for
Fedora 31: mass Python 2 package removal, YUM 3 retirement, Firefox
defaulting to native Wayland backend. we will continue to monitor
the Change list as more changes are approved (adamw, 15:30:09)
* Release criteria / blocker process proposals (adamw, 15:33:13)
* LINK:
https://en.wikipedia.org/wiki/Amazon_Elastic_Compute_Cloud#Instance_types
(adamw, 15:38:26)
* several folks agree that the Xen criterion is not sufficiently
justified even if xen project provides testing; we should only block
on our primary virtualization stack, and we already have a specific
requirement that we boot on ec2, so blocking on xen is not needed
for that purpose either (adamw, 15:46:10)
* however, there was also some concern that dropping the criterion
might lead to xen project not providing the testing they promised if
the criterion remains (adamw, 15:46:39)
* there is ongoing discussion about exactly how the last-minute
blocker bugs provisions should be handled and if a quorum should be
required for waiving a blocker (adamw, 15:55:13)
* Open floor (adamw, 15:56:22)
* ACTION: lailah to propose KDE system settings crash as F31 blocker
(adamw, 16:01:24)
Meeting ended at 16:02:02 UTC.
Action Items
------------
* lailah to propose KDE system settings crash as F31 blocker
Action Items, by person
-----------------------
* **UNASSIGNED**
* lailah to propose KDE system settings crash as F31 blocker
People Present (lines said)
---------------------------
* adamw (100)
* Lailah (46)
* lruzicka (33)
* coremodule (17)
* zodbot (9)
* kparal (6)
* jlanda (4)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
https://meetbot.fedoraproject.org/fedora-meeting/2019-05-27/fedora-qa.201...
--
You received this message due to your preference settings at
https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedorap...