15:00:18 #startmeeting Fedora QA Meeting 15:00:18 Meeting started Mon Mar 30 15:00:18 2020 UTC. 15:00:18 This meeting is logged and archived in a public location. 15:00:18 The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:18 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:18 The meeting name has been set to 'fedora_qa_meeting' 15:00:23 #meetingname fedora-qa 15:00:23 The meeting name has been set to 'fedora-qa' 15:00:28 #topic Roll call 15:00:32 * kparal is here 15:00:34 gooooood qa morning folks 15:00:50 .hello2 15:00:51 frantisekz: frantisekz 'František Zatloukal' 15:00:59 .hello2 15:00:59 coremodule: coremodule 'Geoffrey Marr' 15:01:12 .hello2 15:01:13 bcotton: bcotton 'Ben Cotton' 15:01:39 * sumantro is here 15:02:35 hello 15:03:12 .hello chrismurphy 15:03:13 cmurf: chrismurphy 'Chris Murphy' 15:03:39 hope we're not keeping anyone from important appointments in crowded areas :P 15:04:42 yeah that would be the farmers market in Brentwood... 15:05:25 alrighty, let's get going right away with What Adam Forgot Last Time 15:05:28 #topic Previous meeting follow-up 15:05:43 ooo hey not this time! 15:05:54 #info "adamw to create and populate F32 Common Bugs page" - this is done: https://fedoraproject.org/wiki/Common_F32_bugs 15:06:19 "kparal to write a mail summarizing the validation tests for which hardware access may be an issue" - i believe that was done too right kamil? 15:06:55 .hello2 15:06:56 lruzicka: lruzicka 'Lukáš Růžička' 15:07:01 .hello2 15:07:03 tablepc: tablepc 'Pat Kelly' 15:07:55 helllooooooo kparal 15:08:15 sorry, got distracted 15:08:39 yes I replied to that 15:09:11 excellent 15:09:25 please read that in a mr. burns voice 15:09:50 also i think we got the firmware RAID box out of brno rh office, right? so that's coverted 15:10:07 I believe frantisekz did that, yes 15:10:55 yeah, I have raid box at my place 15:10:57 cool 15:11:27 #info "kparal to write a mail summarizing the validation tests for which hardware access may be an issue" - this was done, brno rh folks also retrieved some test hw from the office, so we should be in good shape 15:11:40 anything else frm last time? 15:13:27 okey dokey then 15:13:28 #topic F32 Final status and plans 15:13:50 so, i hate to say this as things will inevitably burn down if i do, but we actually seem to be looking kinda okay for final 15:14:11 (as i write that i see we haven't had a compose for two days, so i guess i get to go figure out why not after the meeting!) 15:14:30 F32 is looking good to me. There are a couple bugs but nothing close to blocker 15:14:56 tablepc, there are 4 proposed blockers, so that might change 15:14:59 6 now 15:15:08 but yeah, nothing that looks incredibly problematic 15:15:08 even 15:16:03 Yes, I read the blockers, but have not encountered them. The folks I support and I all run Workstation in a pretty vanilla config. 15:16:44 yeah, it's quite normal that we don't all hit the blockers ourselves 15:16:50 if we did the job would be easier :P 15:17:20 but yep, normally this topic is where we look at particularly awkward issues and things that aren't being taken care of and stuff, but i can't think of much 15:17:42 there is still the issue of what's going on with IoT and CoreOS for the release, I guess. i'll have to keep bugging matt about that 15:17:49 I guess the release parties will be virtual. 15:17:52 :D 15:17:58 unless we slip a *lot* :P 15:18:54 so for IoT we have Test day coming up on 8th 15:19:43 right, it's more the process stuff i keep harping on about 15:20:08 and CoreOS as dustymabe told me, he will have `next` stream up and running and then we write test cases 15:20:36 announce a test day or test week as apt ( given how much time we have) 15:20:41 #info F32 seems pretty on-track for Final, we don't have any major concerns at present aside from the ongoing question regarding status and release process for IoT and CoreOS 15:20:42 cool 15:20:54 #topic Criteria / test case changes and proposals 15:21:12 Are the test cases all updated to the latest thinking now. I'm king of looking for a time when I can print out new copies of everything and get familiar with them again. 15:21:31 tablepc: i believe the next event will look a bit different 15:21:40 kind of looking... 15:21:46 check the template pages 15:21:58 so, that's mostly what i wanted to mention here: just wanted to point up a few recent changes 15:22:20 coremodule extended the 'storage devices' table with an 'install to NVMe' test: https://fedoraproject.org/wiki/Template:Installation_test_matrix#Storage_devices 15:22:52 i mentioned that in future it'd be best to post a draft before making changes directly to the prod pages, but this is a pretty straightforward and obvious change so it shouldn't really be a problem 15:23:08 it's just a storage interface we should cover which didn't really exist when we made this section. 15:23:32 the test is just the same as all the other 'install to X' tests, only for NVMe. we should have several folks with NVMe disks, i think. 15:23:50 #info 'install to NVMe' test case has been added to Installation Storage devices matrix 15:24:50 If you need more testing with NVMe I would mind getting one for my test machine. 15:25:10 i don't think we can put it on expenses though :P 15:25:30 I was offering to buy one myself 15:25:52 the other thing to call out is that kparal's proposed changes to the desktop criteria and matrix are live 15:26:09 tablepc: i know, it was just me joking - that'd be great if you can, the more coverage the better 15:26:16 Remember I'm electrical Hardware is where I live mostly 15:27:57 Any particular brand or size absent from the current population? 15:28:07 tablepc: don't think we have a survey or anything 15:29:12 #info kparal's proposed changes to desktop matrix - https://fedoraproject.org/w/index.php?title=Template:Desktop_test_matrix&oldid=569662 - and release criteria - https://fedoraproject.org/w/index.php?title=Fedora_32_Final_Release_Criteria&type=revision&diff=569667&oldid=564126 - are now in effect 15:29:29 so, we have not had a validation event since 0222, so i don't think all those changes are in the current one 15:29:34 but next event will have them, so look out for it. 15:29:42 any other outstanding proposals or anything that i forgot about? 15:29:52 anyone have concerns with the ones that have already been made? 15:32:17 Everyone seems to be busy with bugs 15:32:26 that's...good? :D 15:32:39 #topic Test Day / community event status 15:32:42 #chair sumantro 15:32:42 Current chairs: adamw sumantro 15:32:47 sumantro, where are we at? 15:33:15 So first all, we had a great cloud base test day thanks to all to participated 15:33:33 coremodule and dustymabe helped out! 15:33:54 we have Upgrade test day coming up on 2020-04-02 15:34:20 https://fedoraproject.org/wiki/Test_Day:2020-04-02_F32_Upgrade_Test_Day 15:34:36 and then IoT on 2020-04-08 15:35:04 woot woot 15:35:05 and then Kernel Test Week from 2020-04-13 through 2020-04-17 15:35:42 I am in talks with dustymabe for the FCOS test day in between sometime 15:35:44 sumantro: can you copy the cloud results to the wiki? 15:35:50 sure sure 15:35:56 #info Cloud test day went off well on 2020-03-20, results will be at https://fedoraproject.org/wiki/Test_Day:2020-03-20_Cloud_Testday shortly 15:36:22 sumantro: btw, my pedantic side would like to not put 'test day' on the end of the page names because it's already there at the start :P 15:36:49 :D 15:36:56 #info Upgrade Test Day is coming up on Thursday April 2: https://fedoraproject.org/wiki/Test_Day:2020-04-02_F32_Upgrade_Test_Day 15:37:07 noted adamw :D 15:37:24 #info IoT Test Day will be the following Wednesday, April 8 15:37:37 #info Kernel Test Week will run 2020-04-13 to 2020-04-17 15:37:46 also, silverblue team is not in favor to run a Silverblue test day this cycle 15:37:51 roger 15:38:10 when are you planning to do another onboarding day? 15:38:27 adamw I am planning sometime next week 15:38:33 between test days 15:38:35 cool 15:38:54 #info an onboarding day should be coming up next week, so new folks can look out for the announcement of that soon 15:39:08 thanks sumantro! anything else? any questions on community events, folks? 15:39:23 Special Shout out to kparal, for making IoT name suggestion and getting most number of votes :) 15:39:37 adamw np, thats all from my side :D 15:39:58 💪 15:40:11 kparal: that name idea must have kept you up at nights 15:40:23 no, the other ones did 15:40:48 * cmurf is laughing even though these jokes are going over his head 15:40:51 so I had to submit the sane version :) 15:41:24 cmurf: the name kparal proposed was 'IoT' 15:41:39 yeah i got that i just don't know the context 15:42:05 cmurf: https://lists.fedoraproject.org/archives/list/iot@lists.fedoraproject.org/message/DPK554RJ3NTAEU6FJURN2ZXNMLOVONTB/ 15:42:19 kparal, I voted for one name, and one name only: IoT 15:42:27 so thank you for that brilliant suggestion 15:42:56 Does IoT only run on ARM? 15:42:59 * kparal tips hat 15:43:12 tablepc: nope, it's built for other arches too 15:43:31 i think most real-world IoT hardware is ARM, but having x86_64 is useful for running it in VMs and such 15:43:58 i do find https://fedoraproject.org/wiki/IoT/Name a fascinating example of how terminology shifts 15:44:28 with two different people who've decided that 'silverblue' is a sort of generic term for ostree-based things, when it was specifically not meant to be that...heh 15:45:32 anyhow! 15:45:38 #topic Open floor 15:45:40 any other business, folks? 15:45:50 blocker review meeting coming up in 15 mins in #fedora-blocker-review, btw 15:45:56 nothing from me 15:46:03 Maybe we need a Fedora vending machine running IoT and selling Fedora SWAG 15:47:07 nothing from my side too 15:47:13 that'd be a cool project for someone, tablepc 15:47:19 when there are conferences and things again, anyway :P 15:48:17 Have a Great Day!Expensive though Vending machines aren't cheap. 15:48:50 even old second hand ones? 15:49:01 That's an idea 15:50:28 alrighty, sounds like we're done 15:50:34 i like nice quiet meetings it means nothing is exploding 15:51:11 Good luck with blockers. TTFN 15:51:57 #endmeeting