fedora-qa
LOGS
16:00:33 <tflink> #startmeeting Fedora QA Meeting
16:00:33 <zodbot> Meeting started Mon Nov 14 16:00:33 2022 UTC.
16:00:33 <zodbot> This meeting is logged and archived in a public location.
16:00:33 <zodbot> The chair is tflink. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:00:33 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:33 <zodbot> The meeting name has been set to 'fedora_qa_meeting'
16:00:41 <tflink> #meetingname fedora-qa
16:00:41 <zodbot> The meeting name has been set to 'fedora-qa'
16:01:13 <tflink> yay! the bridge is working. I was a little worried there for a sec
16:01:24 <tflink> #topic Roll Call
16:01:24 * bittin is here
16:01:29 <bittin> .hello bittin
16:01:30 <zodbot> bittin: bittin 'Luna Jernberg' <droidbittin@gmail.com>
16:02:18 * coremodule is here
16:03:17 * kparal is here
16:07:30 * tflink waits a few more minutes to see if we get more people
16:07:57 <LunaJernberg[m]> i know adamw (away till 2022-11-15 evening PST) is out until tommorow before the F37 release atleast
16:08:19 <tflink> yeah, he'll be back tomorrow AFAIK
16:10:27 <tflink> ok, let's get started. there isn't a huge amount to cover
16:10:37 <tflink> #topic Previous meeting follow-up
16:10:57 <tflink> I didn't see any specific items from the last QA meeting, are there any items that I missed?
16:11:07 <tflink> or items that folks want to add?
16:12:29 <coremodule> nothing here
16:12:38 <geraldosimiao> .hello geraldosimiao
16:12:39 <zodbot> geraldosimiao: geraldosimiao 'Geraldo S. Simião Kutz' <geraldo.simiao.kutz@gmail.com>
16:12:52 <tflink> #info No follow-up items from last QA meeting
16:12:57 <tflink> moving on
16:13:08 <tflink> #topic Fedora 37 Status
16:13:14 <bittin> Ready for release tommorow i hope
16:13:28 <tflink> #info Fedora 37 went GO last THursday, will release tomorrow (Tuesday)
16:13:54 <tflink> I think we have the common issues covered?
16:14:05 <tflink> #link https://ask.fedoraproject.org/c/common-issues/141/none
16:14:46 <kparal> yes, it should be done
16:15:16 <kparal> F37 common issues specifically here: https://ask.fedoraproject.org/tags/c/common-issues/141/f37
16:15:24 <lruzicka> .hello lruzicka
16:15:25 <zodbot> lruzicka: lruzicka 'Lukáš Růžička' <lruzicka@redhat.com>
16:15:49 <tflink> ah, I'm still bit of a discord noob, thanks
16:15:52 <tflink> #undo
16:15:52 <zodbot> Removing item from minutes: <MeetBot.items.Link object at 0x7fc420549b00>
16:16:05 <tflink> #link https://ask.fedoraproject.org/c/common-issues/141/f37
16:16:07 <bittin> discourse*
16:16:28 <tflink> apparently, it's starting off as one of those mondays
16:17:43 <tflink> thanks for all the hard work getting F37 out the door, it was a bit of an interesting release at the end
16:18:00 <tflink> other than that, I don't think there's anything else we need to touch on WRT F37
16:18:39 <kparal> I don't think so, hopefully
16:19:03 <tflink> #topic Fedora 38 Changes
16:19:23 <tflink> #link https://fedoraproject.org/wiki/Releases/38/ChangeSet
16:19:34 <bittin> saw a few of those on the mailinglist, but has not had time to read them all, also F38 testing starts on Wednsday
16:20:04 <tflink> yeah, I haven't read them in detail, either but nothing jumps out at me as particularly scary
16:20:44 <tflink> the livemedia and xorg driver changes look to be the most directly impactful for QA, on first glance
16:20:45 <bittin> saw that Phoronix wrote about the new webbased installer and distrowatch wrote about the new image system proposed
16:20:49 <kparal> Changes/LegacyXorgDriverRemoval sounds problematic
16:21:18 <tflink> is the new installer landing for F38?
16:21:27 <tflink> for some reason, I didn't think it was ready yet
16:21:50 <kparal> Wayland for SDDM will surely break stuff again :0
16:21:51 <kparal> 🙂
16:21:55 <kparal> tflink: I don't think so
16:21:56 <bittin> not sure think it lands in Open Beta the day after F37 and then the plan is to land it stable in F38 or F39 i think
16:22:00 <lruzicka> tflink, I do not think so, I spoke to vslavik from Anaconda and he was speaking about tech preview
16:22:00 <bittin> but i can be wrong
16:22:38 <tflink> #info the Xorg driver removal change seems like it will need some attention during testing (https://fedoraproject.org/wiki/Changes/LegacyXorgDriverRemoval)
16:22:39 <lruzicka> tflink, I can check right now if you want ... let me do it
16:22:45 <bittin> https://www.phoronix.com/news/Anaconda-Web-UI-FESCo-F37
16:22:51 <tflink> lruzicka: it'd be good to figure out sooner than later
16:23:13 * tflink is suddenly having flashbacks to the last anaconda rewrite and is praying that this one goes more smoothly
16:23:57 <kparal> we can always skip a release again...
16:24:18 <bittin> so might be good to try the preview that comes out 16th Nov in Open Beta and give feedback to the Anaconda team
16:24:22 <bittin> on a spare computer or in a VM
16:25:05 <tflink> kparal: hopefully we all learned some lessons on communication for this rewrite so we don't have to skip a release again
16:25:20 <mkolman> https://fedorapeople.org/groups/anaconda/webui_preview_image/x86_64/
16:25:48 <lruzicka> tflink, kparal so there is no public timeline decided on the anaconda progress, mkolman told me right now that they do not have a specific target and they want to converge into fedora in the future
16:26:02 <mkolman> if anyone wants to give it a try - not a slightly outdated stand in, should have a more up to date image ready in a couple days :)
16:26:16 <LunaJernberg[m]> ah mkolman nice will help out testing in Virtualbox later tonight or this week :)
16:26:21 <tflink> #info please try out the new Anaconda tech demo if you have the time (new image should be posted this week) https://fedorapeople.org/groups/anaconda/webui_preview_image/x86_64/
16:26:27 <tflink> mkolman: thanks for the link
16:26:42 <LunaJernberg[m]> lruzicka: mkolman: thanks for the info and links :)
16:27:00 <lruzicka> they will however produce iso images with latest changes starting next week
16:27:16 <LunaJernberg[m]> ah alright thanks +1
16:27:28 <tflink> #info there is currently no target release for the upcoming Anaconda rewrite but there are tech demos available and it will likely be released into Fedora for one of the next several upcoming releases
16:27:45 <lruzicka> to sum up, they do not think in 38 new anaconda will replace the old one
16:28:17 <tflink> lruzicka++ mkolman++
16:28:17 <zodbot> tflink: Karma for lruzicka changed to 1 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:28:20 <zodbot> tflink: Karma for mkolman changed to 1 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
16:29:11 <tflink> I don't have a good feel for how disruptive the livemedia change could be. I thought that the overlay came from how the image was written, not how it was built
16:29:52 <tflink> it sounds like it shouldn't be too disruptive, though (famous last words) https://fedoraproject.org/wiki/Changes/ModernizeLiveMedia
16:30:35 <tflink> oh, I see. the change will enable creation of an overlay @ boot time
16:31:13 <tflink> either way, probably best to not leave testing that until freeze :)
16:31:27 <tflink> any other items of note or concern for the F38 change proposals?
16:31:42 <kparal> If it's enabled by default, we'll probably need to add some test cases
16:32:27 <tflink> yeah, it'll be baked into the images to add more boot options
16:33:49 <tflink> #info the livemedia change may require some new testcases to cover the additional boot options
16:34:06 <tflink> ok, moving on for now
16:34:18 <tflink> #topic Test Day / Community event status
16:34:35 <tflink> SumantroMukherje: around for a test day update?
16:34:36 <bittin> nothing planned yet i think but i think SumantroMukherje would know more
16:35:02 <tflink> yeah, it's a bit early in the F38 cycle for test days. I'm not aware of any imminent events
16:35:35 <tflink> #info no events are coming up soon due to the end of the F37 cycle, start of F38 cycle
16:35:42 <tflink> #topic Open Floor
16:35:52 * bittin does not have anything
16:35:54 <tflink> are there any more topics that folks want to bring up?
16:36:56 <lruzicka> not at the moment, i think
16:37:19 <kparal> nothing here
16:37:46 * tflink sets the 5 minute fuse and prepares to run
16:38:11 <lruzicka> why so long?
16:38:34 <lruzicka> I guess make it 20 secs and increase speed :D
16:38:51 <tflink> habit? speed of sync between IRC/matrix? I'm not a fast runner?
16:39:26 <lruzicka> ok, i did not know the sync lasted so long
16:39:54 <tflink> it doesn't, I'm just trying to think of possible reasons, regardless of likelyhood
16:40:20 <tflink> s/5min/30sec/
16:40:34 <tflink> ssss ... **BOOM**
16:40:46 <tflink> thanks for coming, everyone. I'll send out minutes shortly
16:40:49 <tflink> #endmeeting