#meeting:fedoraproject.org log

<@kparal:matrix.org>

15:01:29

!startmeeting Quality

<@meetbot:fedora.im>

15:01:33

Meeting started at 2025-08-18 15:01:29 UTC

<@meetbot:fedora.im>

15:01:33

The Meeting name is 'Quality'

<@kparal:matrix.org>

15:01:40

!topic Roll Call

<@kparal:matrix.org>

15:02:00

hello, who do we have around?

<@hricky:fedora.im>

15:03:11

!hi

<@zodbot:fedora.im>

15:03:13

Hristo Marinov (hricky) - he / him / his

<@derekenz:fedora.im>

15:03:25

!hi

<@zodbot:fedora.im>

15:03:26

Derek Enz (derekenz)

<@kparal:matrix.org>

15:03:42

good morning, afternoon, evening and night to everybody

<@derekenz:fedora.im>

15:03:54

Morning

<@kparal:matrix.org>

15:04:14

let's start with

<@kparal:matrix.org>

15:04:16

!topic Previous meeting follow-up

<@kparal:matrix.org>

15:04:40

and I don't believe we have anything from the last meeting, so we can skip this one

<@kparal:matrix.org>

15:04:51

!topic Fedora 43 status

<@kparal:matrix.org>

15:05:04

!info F43 is now Branched

<@kparal:matrix.org>

15:05:50

we have branched successfully, so the first important step is done. Now just all the remaining ones 🙂

<@kparal:matrix.org>

15:06:33

now that we're branched, we'll need to start dealing with blocker bugs

<@lruzicka:matrix.org>

15:06:39

I say let's ship it.

<@kparal:matrix.org>

15:06:45

note that proposed blockerbugs are listed at:

<@kparal:matrix.org>

15:06:48

#link https://qa.fedoraproject.org/blockerbugs/milestone/43/beta/buglist

<@kparal:matrix.org>

15:06:53

and

<@kparal:matrix.org>

15:06:55

#link https://qa.fedoraproject.org/blockerbugs/milestone/43/final/buglist

<@kparal:matrix.org>

15:07:09

please go and vote for blockerbugs, according to our criteria

<@kparal:matrix.org>

15:07:22

#link https://fedoraproject.org/wiki/Fedora_Release_Criteria

<@kparal:matrix.org>

15:07:34

#info please vote for blocker bugs

<@kparal:matrix.org>

15:08:02

we'll need to start having blocker meetings soon as well, for those bugs that are not resolved in voting tickets

<@kparal:matrix.org>

15:08:41

also, you can start testing and filling out release validation matrices, they are announced in the test-announce list

<@kparal:matrix.org>

15:09:11

and over the time coverage is visible at:

<@kparal:matrix.org>

15:09:14

#link https://openqa.fedoraproject.org/testcase_stats/43/

<@kparal:matrix.org>

15:09:49

doh, I used #command instead of !command everywhere, let me fix it

<@kparal:matrix.org>

15:09:57

!link https://qa.fedoraproject.org/blockerbugs/milestone/43/beta/buglist

<@kparal:matrix.org>

15:10:06

!link https://qa.fedoraproject.org/blockerbugs/milestone/43/final/buglist

<@kparal:matrix.org>

15:10:17

!link https://fedoraproject.org/wiki/Fedora\_Release\_Criteria

<@kparal:matrix.org>

15:10:22

!info please vote for blocker bugs

<@kparal:matrix.org>

15:10:31

!link https://openqa.fedoraproject.org/testcase\_stats/43/

<@kparal:matrix.org>

15:10:51

sigh, and now all the urls are broken

<@kparal:matrix.org>

15:11:19

!link https://openqa.fedoraproject.org/testcase_stats/43/

<@kparal:matrix.org>

15:11:19

!link https://fedoraproject.org/wiki/Fedora_Release_Criteria

<@kparal:matrix.org>

15:11:19

fixed urls:

<@kparal:matrix.org>

15:11:48

ok, anything else regarding F43 that you want to mention?

<@kparal:matrix.org>

15:11:54

any noteworthy problems?

<@derekenz:fedora.im>

15:11:56

<@derekenz:fedora.im>

15:11:58

yes

<@derekenz:fedora.im>

15:12:15

Cannot get the aarch64 KDE to boot

<@derekenz:fedora.im>

15:12:36

Left a message in Fedora ARM

<@kparal:matrix.org>

15:12:44

is there a bug report?

<@derekenz:fedora.im>

15:12:51

It seems they will look at it

<@derekenz:fedora.im>

15:13:07

For Rpi4

<@derekenz:fedora.im>

15:13:27

This was just a day or two ago

<@kparal:matrix.org>

15:13:39

please file a bug report and propose it as a blocker either through our blockerbugs app, or ping us at #quality:fedoraproject.org and we'll add it

<@derekenz:fedora.im>

15:13:46

Havnt looked at BZ yet

<@kparal:matrix.org>

15:14:04

aarch64 KDE is still release-blocking, even though we're trying to sneak out of that 🙂

<@derekenz:fedora.im>

15:14:18

I hope not lol

<@lruzicka:matrix.org>

15:14:35

It's a long way to Tiperary, it's a long way to GO.

<@kparal:matrix.org>

15:15:53

Derek Enz: ok, thanks for mentioning it, but please do create the bug report, so that we can track it, thanks a lot

<@derekenz:fedora.im>

15:16:06

Ok yes no problem

<@kparal:matrix.org>

15:16:15

alright, anything else?

<@lruzicka:matrix.org>

15:17:25

I do not have anything, just that fiddle around the repositories to get the system upgrade itself, but other than that I have not spotted anything serious ... I have been running 43 since yesterday.

<@kparal:matrix.org>

15:18:13

ok, thanks, let's go to

<@kparal:matrix.org>

15:18:15

!topic Scope reduction discussion

<@kparal:matrix.org>

15:18:44

so if you look at the summary, three proposals have been already implemented

<@kparal:matrix.org>

15:18:48

!link https://discussion.fedoraproject.org/t/fedora-quality-scope-reduction-announcement-and-summary/160523

<@kparal:matrix.org>

15:19:37

those are Drop optical media boot release criterion, Drop Intel-based Macbook dual boot release criterion, and Require just the standard set of apps to be release-blocking on Workstation x86_64, not all apps

<@kparal:matrix.org>

15:20:06

the other proposals are getting more complicated and will likely require changes

<@kparal:matrix.org>

15:20:25

the BIOS reduction will likely get an exception for RAID on Server

<@kparal:matrix.org>

15:21:02

aarch64 desktops has hit a strong opposition from Neal from the KDE SIG (while Workstation folks seem OK with dropping the status)

<@kparal:matrix.org>

15:21:36

IoT folks are not happy with the proposal of de-editioning it, unsurprisingly

<@kparal:matrix.org>

15:22:31

and aarch64 hardware unification to just RPi4 gets voices for alternative boards choices, etc

<@kparal:matrix.org>

15:23:09

if you can participate in the discussions and add some valuable data, for example around aarch64, IoT, etc, that's very welcome

<@kparal:matrix.org>

15:23:37

!info implemented proposals: "Drop optical media boot release criterion", "Drop Intel-based Macbook dual boot release criterion", and "Require just the standard set of apps to be release-blocking on Workstation x86_64, not all apps"

<@kparal:matrix.org>

15:23:54

!info other proposals will require more discussion and possible tweaks

<@kparal:matrix.org>

15:24:46

which means so far, we've gained only minor time and effort savings

<@kparal:matrix.org>

15:25:24

anyone has some feedback regarding this?

<@derekenz:fedora.im>

15:26:14

Being in the KDE SIG I know myself and Troy have covered aarch64

<@amoloney:fedora.im>

15:26:19

This made me legitimately LOL in real life :D

<@derekenz:fedora.im>

15:26:38

Isnt the issue in OpenQA?

<@lruzicka:matrix.org>

15:26:52

What do you mean?

<@derekenz:fedora.im>

15:27:24

It was a convo between Neal and Kamil

<@kparal:matrix.org>

15:27:50

the issue is not with lack of automation for KDE, but the with manual effort needed to shape it up for a release-ready state

<@kparal:matrix.org>

15:28:11

we have automation for GNOME, and it doesn't help us with manpower much

<@kparal:matrix.org>

15:28:21

yes it detects problems, but dealing with those problems is still a lot of time

<@kparal:matrix.org>

15:28:38

and hardware-specific issues it doesn't detect, which are very frequent

<@kparal:matrix.org>

15:29:14

we appreciate a lot the work the KDE SIG is investing into aarch64 testing, btw

<@kparal:matrix.org>

15:31:06

was my answer sufficient? do you want to talk more about it?

<@derekenz:fedora.im>

15:31:23

Not sure what else I can say

<@kparal:matrix.org>

15:32:10

OK. Neal said that KDE SIG will handle it whole, so in that case QA can't argue much against the release-blocking status, except for some minor time spent on herding release blockers

<@derekenz:fedora.im>

15:32:27

EIther way myself and Troy will run tests

<@kparal:matrix.org>

15:32:29

so I guess we'll only try to drop GNOME aarch64 at this moment

<@lruzicka:matrix.org>

15:33:34

This is a fair promise to give and I would like to say that we never wanted to stand in any SIGs effort to create a release blocking edition with top quality, we just cannot make it happen for everything.

<@kparal:matrix.org>

15:34:13

ok, so let's move on

<@kparal:matrix.org>

15:34:20

!topic Test Day / community event status

<@kparal:matrix.org>

15:34:49

all test days have finished at this moment

<@kparal:matrix.org>

15:34:52

!link https://testdays.fedoraproject.org/

<@kparal:matrix.org>

15:35:09

if you still feel like contributing to one, you can do so, they're still quite current

<@kparal:matrix.org>

15:35:44

we don't have anything else planned at the moment, sadly, because of staffing issues

<@kparal:matrix.org>

15:36:06

we'll need to send out some announcement that teams should contact us, if they want to run something

<@kparal:matrix.org>

15:36:28

we no longer have a person to go and actively poke the teams or create our own test days

<@kparal:matrix.org>

15:36:49

so if you have an idea and want to run something, please create a ticket for us and let's discuss it!

<@kparal:matrix.org>

15:36:57

more info at

<@kparal:matrix.org>

15:36:59

!link https://fedoraproject.org/wiki/QA/Test_Days

<@kparal:matrix.org>

15:37:18

!info please reach us if you want to run some test day

<@kparal:matrix.org>

15:37:46

anything on this topic?

<@hricky:fedora.im>

15:37:57

Is it mandatory to be a member of a team or SIG to organize a test day?

<@lruzicka:matrix.org>

15:38:24

I do not think so.

<@kparal:matrix.org>

15:38:28

<@lruzicka:matrix.org>

15:38:30

Anybody could organize it.

<@kparal:matrix.org>

15:39:20

however, the useful part is when developers/maintainers are present in a support channel for the duration of the event

<@hricky:fedora.im>

15:39:43

Can a regular community member, i.e. me, write the test cases etc.?

<@kparal:matrix.org>

15:39:45

so collaboration is definitely a better way

<@kparal:matrix.org>

15:40:17

sure, do you have any specific area in mind?

<@lruzicka:matrix.org>

15:40:41

Yes, of course. You can write it (or help edit the existing if you think you could improve them).

<@hricky:fedora.im>

15:41:42

Fedora Atomic Desktops. I already have an agreement with the maintainer.

<@kparal:matrix.org>

15:42:00

you can have a good idea about past test days when you go through categories at https://fedoraproject.org/wiki/Category:Test_Days

<@kparal:matrix.org>

15:43:04

if you have some idea, please create a ticket and we'll figure out the details together. Or talk to us any time in #quality:fedoraproject.org

<@kparal:matrix.org>

15:43:25

Atomic Desktops is definitely a valid idea for test days

<@kparal:matrix.org>

15:43:51

awesome, let's move forward

<@kparal:matrix.org>

15:43:54

!topic Open floor

<@kparal:matrix.org>

15:44:07

anything else from anyone?

<@derekenz:fedora.im>

15:44:31

Not from me

<@kparal:matrix.org>

15:44:32

bugs, problems, ideas, your grandma's cookie recipe?

<@lruzicka:matrix.org>

15:45:56

From my grandmother: "It is better to sleep than lick honey."

<@kparal:matrix.org>

15:46:32

and with that wisdom, we'll close the meeting. Thanks everybody for coming!

<@kparal:matrix.org>

15:46:35

!endmeeting