15:01:08 #startmeeting Fedora QA meeting 15:01:08 Meeting started Mon Mar 28 15:01:08 2022 UTC. 15:01:08 This meeting is logged and archived in a public location. 15:01:08 The chair is adamw. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:01:08 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:08 The meeting name has been set to 'fedora_qa_meeting' 15:01:12 #meetingname fedora-qa 15:01:12 The meeting name has been set to 'fedora-qa' 15:01:17 #topic Roll Call 15:01:21 .hello2 15:01:22 bcotton: Something blew up, please try again 15:01:22 morning folks, who's around? 15:01:25 bcotton: An error has occurred and has been logged. Please contact this bot's administrator for more information. 15:01:52 * kparal lurks 15:02:07 * coremodule is here 15:04:41 .hello 15:04:41 cmurf: (hello ) -- Alias for "hellomynameis $1". 15:04:52 .hello2 15:04:53 cmurf: Something blew up, please try again 15:04:55 cmurf: An error has occurred and has been logged. Please contact this bot's administrator for more information. 15:05:05 Haha 15:05:27 I still like the you don't exist message better 15:06:43 i'm happy to tell you you don't exist if that'd help 15:06:43 alrighty, let's see here 15:06:43 #topic Previous meeting follow-up 15:06:58 #info "adamw to consider updating network criteria proposal to cover types of network connection (wired, wireless, security types...)" - sorry, didn't quite get around to this, busy weeks with beta and all. will try and do it this week 15:07:11 #action adamw to consider updating network criteria proposal to cover types of network connection (wired, wireless, security types...) 15:07:18 any other follow-up? 15:09:05 guess not! 15:10:17 #topic Fedora 36 Beta wrap-up and Final planning 15:10:56 alright, so we managed to get Beta out the door. uh, I should check in with mboddu on freeze lift and 0-day update push, i guess. i think we've documented the major bugs that made it in. anyone got any other notes? 15:11:43 adamw: Beta freeze is lifted and all the pending updates were pushed to stable 15:11:57 awesome, thanks 15:12:11 #info f36 freeze is lifted for now and pending updates have gone stable 15:12:39 F36 Common Issues are ready 15:12:45 https://ask.fedoraproject.org/tags/c/common-issues/141/f36 15:12:51 (although I just fixed the older nvr getting tagged after the newer nvr due to multiple updates were in pending state, so the next push/compose will have the higher nvr's in the stable compose) 15:13:13 mboddu: sigh, we really need to make bodhi...not do that. 15:13:48 adamw: Well, that is hard as an update contains multiple builds, which is the problem 15:13:57 I think it's impossible unless we give up having pending stable updates and being able to submit new ones... 15:14:52 well, we could potentially have bodhi edit earlier builds out of pending updates when a later build is pushed, or something... 15:15:23 IMHO, we should reject any update submissions where there's a version non stable yet 15:16:24 ^ -1, then if an update fixes something, then they have to wait at least a day for it to be available in stable (provided the newer build got enough karma) 15:16:49 Some systems will be broken till then 15:17:31 In my opinion, if a build is not stable yet, just mention it to the user and ask him to edit the update instead creating a new one 15:17:43 But that comes with perms and stuff 15:17:51 they have to... communicate with whoever made the other update/edit it? 15:18:02 and there's a corner case exactly with releases 15:18:05 anyhow, probibly not the place to solve this. 15:18:06 Yeah 15:18:14 And yes, not the right place 15:18:17 where we need to push exactly the update that was in the candidate stable 15:18:20 and yeah, that. 15:18:37 any more on-topic f36 business? :D 15:19:10 freeze for final is very soon... 15:19:35 yes, this is what happens when we don't push out final when beta is delayed :| 15:19:55 i'll talk to gnome/kde/kernel folks and highlight that they have a tight window to get things in without an FE 15:21:07 #info F36 Beta release will happen tomorrow, freeze is lifted, first 0-day update push has happened, common bugs are live at https://ask.fedoraproject.org/tags/c/common-issues/141/f36 15:21:56 #info Final freeze starts in eight days (2022-04-05) 15:23:25 adamw: not sure if this is the right place / time to ask but is the GNOME on-screen keyboard part of the final release criteria? should it be added to the beta release criteria? 15:23:46 I'm asking becuase of this bug: https://bugzilla.redhat.com/show_bug.cgi?id=2069164 15:24:01 Anders: i don't think we explicitly cover it atm 15:24:23 maybe it should be mentionned in the beta release note as a common bug? 15:24:37 a way to handle bugs with it would be to count that as a conditional violation of the 'you must be able to log in' criterion, the condition being 'on a tablet device', or something like that 15:24:55 Anders: common bugs is a separate thing, it would certainly make sense to include it there, yes 15:25:01 to nominate it just add the CommonBugs keyword 15:25:21 .hello geraldosimiao 15:25:22 geraldosimiao: geraldosimiao 'Geraldo S. Simião Kutz' 15:25:31 Sorry for being late 15:25:38 kparal: oh, btw, i edited the "commonbugs?" search in bugzilla to handle ask.fp.o urls, but not sure if that changes the search for everyone or if it's saved per-account. did the change take effect for you? 15:26:19 hi geraldo, no problem 15:26:25 * kparal looking 15:27:01 adamw: that's per account, it seems 15:27:09 fun. 15:27:42 but we linked the search from the commonbugs wiki pages, so there must be some kind of site-wide version. i'll have to ask a bugzilla admin how that works.. 15:27:47 (or did we just link an entire search construction url? hmm.) 15:27:56 but perhaps because I might have saved it even myself in the past? 15:28:52 oh yeah, it looks like the URL contains the entire search terms. plus it goes via a redirect and i don't know who created that redirect and has power to edit it. great! 15:29:31 the bit.ly one? I thought you did 😀 15:29:42 i don't think i did? 15:30:08 anyway, i'll look into that more later 15:30:20 #action adamw to contact kde, gnome and kernel folks regarding Final freeze date 15:30:21 anyway, https://fedoraproject.org/wiki/Common_F36_bugs has a correct search link 15:30:49 (under Expand) 15:32:23 ah, cool. would be good if we had a space in the forum for that kinda meta thing too 15:33:18 what do you mean? 15:34:25 well, stuff we used to keep in the wiki page header templates, i guess. links to the bugzilla searches, release notes, things like that. 15:35:25 There's this pinned topic which can host some additional information: 15:35:25 https://ask.fedoraproject.org/t/about-the-common-issues-category/18526 15:35:57 And this pinned topic for people proposing and working with common issues (so, us): 15:35:57 https://ask.fedoraproject.org/t/about-the-proposed-common-issues-category/18527 15:35:58 ah, cool. 15:36:20 And general feedback and improvements discussion is here: 15:36:20 https://ask.fedoraproject.org/t/we-are-testing-a-new-common-issues-category-and-process/18916 15:37:15 It took me a while to understand the navigation in Discourse, but it no longer feels like a jungle to me and I can find stuff in there 🙂 15:37:36 alrighty, moving on, i guess 15:37:42 #topic Current criteria / test case proposals 15:37:50 #info networking proposal still waiting on an update, see earlier 15:38:20 #info the Council Edition identification waiver was put into production 15:38:49 where are we up to with test cases for the graphical package manager criteria? i don't recall seeing any progress there yet 15:41:38 * kparal has no information on that 15:42:12 I believe that Sumantro volunteered to do it? 15:42:20 yeah, https://pagure.io/fedora-qa/issue/688 15:42:23 looks like nothing happened yet 15:42:38 #info still waiting on test cases for the graphical package management criteria: https://pagure.io/fedora-qa/issue/688 15:42:50 #action adamw to check in with sumantro on status there 15:43:29 i think that's all the proposals we have hanging around, unless I forgot any? 15:46:22 alrighty 15:47:06 #topic Test Day / community event status 15:47:12 sumantro: don't suppose you're around for this? 15:47:54 I know IoT test day will be Wednesday, April 6th 15:48:15 yeah, we seem to have several events overlapping next week 15:48:42 #info Fedora CoreOS Test Week runs 2022-04-04 to 2022-04-11: https://pagure.io/fedora-qa/issue/695 (no wiki page yet) 15:49:15 #info kernel 5.17 test week runs 2022-04-03 to 2022-04-09: http://fedoraproject.org/wiki/Test_Day:2022-04-03_Kernel_5.17_Test_Week 15:49:39 #info IoT Test Day runs 2022-04-06: https://pagure.io/fedora-qa/issue/696 (no wiki page yet) 15:50:32 so, please help with those tests if you can! 15:50:40 anything else on that topic? 15:52:34 alrighty 15:52:37 #topic Open floor 15:52:45 blocker review meeting at the top of the hour over in #blocker-review:fedoraproject.org 15:55:03 any other business? 15:56:30 guess not! thanks for coming, folks 15:56:32 #endmeeting