I've filled in the vacation calendar too, but just in case anyone
doesn't check that - I'm going to be on vacation from 2019-05-02
(tomorrow) to 2019-05-19. Please contact anyone on the QA team (test@
list, #fedora-qa IRC) for general QA stuff, and lruzicka for openQA
stuff. I will be checking my email periodically, and am available via
Telegram in case of emergency. Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
==================================
#fedora-meeting: Fedora QA Meeting
==================================
Meeting started by adamw at 15:02:18 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting/2019-04-29/fedora-qa.2019-…
.
Meeting summary
---------------
* Roll call (adamw, 15:02:26)
* Previous meeting follow-up (adamw, 15:09:00)
* "adamw to put proposed printing criteria into production" - did
that, e.g.
https://fedoraproject.org/wiki/Fedora_30_Beta_Release_Criteria#Printing
(adamw, 15:09:34)
* "adamw to get printing test cases written and added to matrices" -
mostly did that too, see
https://fedoraproject.org/wiki/Template:Desktop_test_matrix (though
we might need a new one too) (adamw, 15:10:43)
* "adamw to implement move of 'basic graphics' criterion to Final and
follow up on mailing lists" - did that too,
https://fedoraproject.org/wiki/Fedora_30_Final_Release_Criteria#.27Basic_gr…
(adamw, 15:11:24)
* LINK: https://marc.info/?l=fedora-devel-list&m=155420938100327&w=2
(sumantro, 15:24:51)
* "lruzicka and sumantro to look over specific issues that came up in
the modularity test day and talk to sgallagh about possible
improvements, especially re. modules with no default profile" - some
discussion on devel@ in the thread
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
(adamw, 15:26:53)
* ACTION: lruzicka to follow up on "Modularity UX Questions" thread
again asking for more concrete results (adamw, 15:28:09)
* Fedora 30 wrap-up / final tasks (adamw, 15:28:44)
* thanks to everyone for Fedora 30 Final validation testing, release
will happen tomorrow (adamw, 15:29:17)
* ACTION: adamw to revise F30 Common Bugs for Final (adamw, 15:30:48)
* Xen release criterion (adamw, 15:33:45)
* general consensus that Xen criterion can go and test case be made
non-blocking, we will wait a few more days for list feedback
(adamw, 15:40:42)
* Late-discovered blocker waive proposal (adamw, 15:40:56)
* LINK:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/…
(adamw, 15:42:03)
* ACTION: adamw to resurrect the 'late blocker waiver' proposal with a
third draft or re-send of the second draft (adamw, 15:49:25)
* Test Day / community event status (adamw, 15:51:17)
* Fedora 31 call for test days was sent out (adamw, 15:53:05)
* media writer Test Day is 2019-04-30:
https://fedoraproject.org/wiki/Test_Day:2019-04-30_Fedora_Media_Writer
(adamw, 15:53:30)
* Kernel test week is 2019-05-13 to 2019-05-18, mark your calendar!
(adamw, 15:53:42)
* Open floor (adamw, 15:55:05)
* coremodule working on Heroes of Fedora blog posts for end of this
week or early next week (adamw, 15:56:09)
Meeting ended at 16:04:19 UTC.
Action Items
------------
* lruzicka to follow up on "Modularity UX Questions" thread again asking
for more concrete results
* adamw to revise F30 Common Bugs for Final
* adamw to resurrect the 'late blocker waiver' proposal with a third
draft or re-send of the second draft
Action Items, by person
-----------------------
* adamw
* adamw to revise F30 Common Bugs for Final
* adamw to resurrect the 'late blocker waiver' proposal with a third
draft or re-send of the second draft
* lruzicka
* lruzicka to follow up on "Modularity UX Questions" thread again
asking for more concrete results
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* adamw (103)
* lruzicka (31)
* tablepc (13)
* kparal (13)
* coremodule (13)
* sumantro (12)
* zodbot (9)
* bcotton (6)
* tflink (4)
* pingou (4)
* satellit (2)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
In the last QA team meeting (04/29/2019) I volunteered to help with
adding something to the blocker bug process to handle Last Minute
Blocker Bugs.
I started by reading:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org/…
Followed by: https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
and: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
I agree that the provisions for how to handle last minute proposed
blocker bugs should be in the Blocker Bug Process rather than Blocker
Bug Meeting.
Here's my draft:
Exceptions for Last Minute Proposed Blocker Bugs
Last Minute Proposed Blocker Bugs must meet Blocker Bug Criteria before
being processed per this section.
Last Minute Blocker Bugs shall be evaluated for being delayed to the
next release cycle according to the criteria below. Last Minute Proposed
Blocker Bugs that meet any of the listed criteria may be delayed to the
next release cycle as Blocker Bugs if the Release Team agrees. Other
Last Minute Proposed Blocker Bugs must be corrected before the current
cycle Final Release.
1) Any bug that can not be fixed in a reasonable amount of time
considering the current Release Cycle or due to complexity or resource
constraints.
2) Any bug in non-vital system operation or release package installed
application operation.
Delaying the current Release:
Delaying the current release cycle must take into account all of the
following criteria.
1) Consider if the cause of the delay should have been caught earlier in
the current cycle. What changes in process could help moving such
discoveries earlier in the cycle?
2) Adding the current proposed delay to any prior delays, is the total
delay becoming unacceptable in regard to Fedora release policy?
3) Will the current proposed delay enable other desirable work to be
completed for the release?
4) Impact on down stream projects.
Looking forward to your feedback.
Have a Great Day!
Pat (tablepc)