2024-07-22 15:00:37 <@kparal:matrix.org> !startmeeting Quality
2024-07-22 15:00:39 <@meetbot:fedora.im> Meeting started at 2024-07-22 15:00:37 UTC
2024-07-22 15:00:39 <@meetbot:fedora.im> The Meeting name is 'Quality'
2024-07-22 15:00:55 <@kparal:matrix.org> !topic Roll Call
2024-07-22 15:01:19 <@kparal:matrix.org> So, who do we have here today?
2024-07-22 15:01:26 <@kparal:matrix.org> Adam is away, I'll be leading the meeting this time
2024-07-22 15:01:44 <@kparal:matrix.org> Welcome, Sumantro
2024-07-22 15:01:55 <@sumantrom:fedora.im> yaay! 
2024-07-22 15:02:06 <@kparal:matrix.org> Great, welcome jednorozec 
2024-07-22 15:02:41 <@sumantrom:fedora.im> jednorozec: František Zatloukal  is our chosen guy, I will also be able to help!! :) 
2024-07-22 15:03:12 <@kparal:matrix.org> Anyone else around? Poke coremodule František Zatloukal Lukas Brabec 
2024-07-22 15:05:21 <@kparal:matrix.org> Seems not, everybody on vacation, apparently
2024-07-22 15:05:29 <@kparal:matrix.org> So let's move forward
2024-07-22 15:05:36 <@sumantrom:fedora.im> sure sure
2024-07-22 15:05:41 <@kparal:matrix.org> !topic Previous meeting follow-up
2024-07-22 15:05:58 <@kparal:matrix.org> This should be easy, we have no action items from the last meeting
2024-07-22 15:06:03 <@kparal:matrix.org> At least I haven't found any
2024-07-22 15:06:37 <@kparal:matrix.org> Alright, moving on
2024-07-22 15:06:47 <@kparal:matrix.org> !topic Fedora 41 status
2024-07-22 15:07:12 <@sumantrom:fedora.im> F41 branching happens soon ? 
2024-07-22 15:07:40 <@kparal:matrix.org> Let's see: https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html
2024-07-22 15:07:56 <@kparal:matrix.org> Branch Fedora Linux 41 from Rawhide 	Tue 2024-08-13
2024-07-22 15:08:04 <@kparal:matrix.org> so in 3 weeks
2024-07-22 15:09:05 <@kparal:matrix.org> Also, a notable change is that we have a new release-blocking deliverable. This got accepted by FESCo:
2024-07-22 15:09:05 <@kparal:matrix.org> https://fedoraproject.org/wiki/Changes/Fedora_KDE_AArch64_ReleaseBlocker
2024-07-22 15:09:40 <@kparal:matrix.org> !info KDE AArch64 image will be release blocking from F41
2024-07-22 15:09:45 <@kparal:matrix.org> !link https://fedoraproject.org/wiki/Changes/Fedora_KDE_AArch64_ReleaseBlocker
2024-07-22 15:09:47 <@sumantrom:fedora.im> so the IOT bits of it ? 
2024-07-22 15:10:17 <@sumantrom:fedora.im> coremodule: does most of the bits for aarch64, should we suggest him to do a test day?
2024-07-22 15:10:24 <@kparal:matrix.org> no, this is not IoT, this is the same as Workstation on aarch64, just KDE
2024-07-22 15:10:50 <@kparal:matrix.org> Sumantro Mukherjee: a test day is a good idea, please ping the Change owners to discuss, thanks
2024-07-22 15:11:31 <@kparal:matrix.org> they promised they'll handle most (if not all) of the testing, because I'm afraid we won't have the capacity. So let's see how it works out during this cycle.
2024-07-22 15:12:22 <@sumantrom:fedora.im> so, we do need the test cases to be associated with release criteria?
2024-07-22 15:12:52 <@kparal:matrix.org> I think we have already test cases ready, don't we?
2024-07-22 15:13:22 <@kparal:matrix.org> we need to add a KDE column here: https://fedoraproject.org/wiki/Template:Desktop_test_matrix#Release-blocking_desktops:_aarch64
2024-07-22 15:13:28 <@sumantrom:fedora.im> yes we might not have them for the apps in the relval matrix .. since I wrote them for just test days
2024-07-22 15:14:12 <@kparal:matrix.org> we already block on KDE on x86 (a section above the one I linked), we just need to replicate the look for aarch64
2024-07-22 15:14:40 <@sumantrom:fedora.im> https://testdays.fedoraproject.org/events/174  , this has the new test cases for the apps
2024-07-22 15:15:39 <@sumantrom:fedora.im> or we do have like a general one for GNOME and KDE apps
2024-07-22 15:15:43 <@kparal:matrix.org> that's all already in the release validation template
2024-07-22 15:15:47 <@sumantrom:fedora.im> in that case we should be good
2024-07-22 15:15:58 <@sumantrom:fedora.im> yep, I understood 
2024-07-22 15:15:58 <@kparal:matrix.org> just look at the link I posted 🙂
2024-07-22 15:16:39 <@kparal:matrix.org> #action kparal to update Desktop test matrix template to mark KDE as blocking on aarch64
2024-07-22 15:16:39 <@sumantrom:fedora.im> yep, nevermind.. my bad
2024-07-22 15:16:43 <@kparal:matrix.org> !action kparal to update Desktop test matrix template to mark KDE as blocking on aarch64
2024-07-22 15:17:17 <@kparal:matrix.org> alright, good that you brought that up, otherwise I'd have forgotten about the template
2024-07-22 15:17:43 <@kparal:matrix.org> anything else regarding current F41 status?
2024-07-22 15:18:09 <@sumantrom:fedora.im> nothing that's shocking rn 
2024-07-22 15:19:32 <@sumantrom:fedora.im> should be move forwards?
2024-07-22 15:19:41 <@sumantrom:fedora.im> should be move forward?
2024-07-22 15:20:31 <@kparal:matrix.org> let's move on
2024-07-22 15:20:39 <@kparal:matrix.org> !topic Test Day / community event status
2024-07-22 15:20:52 <@kparal:matrix.org> Sumantro Mukherjee: your time to shine!
2024-07-22 15:21:35 <@sumantrom:fedora.im> we have Podman 5.2 which is going to happen 2024-07-29 through 2024-07-31
2024-07-22 15:21:44 <@sumantrom:fedora.im> https://testdays.fedoraproject.org/events/193
2024-07-22 15:21:58 <@kparal:matrix.org> ok, I don't see it in fedocal, though
2024-07-22 15:22:18 <@sumantrom:fedora.im> lsm5 is going to give me a few more test cases by EOD and I will be creating the Fedocal as well
2024-07-22 15:22:29 <@kparal:matrix.org> great
2024-07-22 15:23:16 <@sumantrom:fedora.im> The next up is  Kernel 6.10 Test Week , https://testdays.fedoraproject.org/events/192 ..  	Jul 28, 2024 - Aug 03, 2024
2024-07-22 15:23:29 <@sumantrom:fedora.im> this will also end up on fedocal soon
2024-07-22 15:23:48 <@sumantrom:fedora.im> I will be reaching out to folks soon for these test days
2024-07-22 15:24:17 <@sumantrom:fedora.im> upcoming plans are for sorting xorg drop and modernizing live media 
2024-07-22 15:24:22 <@sumantrom:fedora.im> as we get closer 
2024-07-22 15:24:36 <@kparal:matrix.org> !info Podman and Kernel test days are upcoming
2024-07-22 15:25:05 <@kparal:matrix.org> alright, sounds good
2024-07-22 15:25:14 <@kparal:matrix.org> anything else to add?
2024-07-22 15:26:24 <@sumantrom:fedora.im> nothing much on my end.. I wish to publish the fedora 39 and 40 contributor stats soon .. on commblog 
2024-07-22 15:26:42 <@sumantrom:fedora.im> so keeping an eye there would be great to mention
2024-07-22 15:27:30 <@kparal:matrix.org> it's a bit late for those stats, I wonder if it's still worth it
2024-07-22 15:27:48 <@sumantrom:fedora.im> it will be , I have some recognition plan that's in works 
2024-07-22 15:28:05 <@sumantrom:fedora.im> and getting the stats out would help, that's important
2024-07-22 15:28:31 <@kparal:matrix.org> !action sumantrom to publish F39 and F40 community stats on commblog
2024-07-22 15:28:52 <@kparal:matrix.org> alright, thanks for the update!
2024-07-22 15:29:10 <@sumantrom:fedora.im> that's all from my end
2024-07-22 15:29:20 <@kparal:matrix.org> !topic Git forge replacement
2024-07-22 15:29:40 <@kparal:matrix.org> jednorozec: now's your time 🙂
2024-07-22 15:29:53 <@humaton:fedora.im> sure 
2024-07-22 15:30:33 <@humaton:fedora.im> so, we have identified 2 QA processes that are tightly integrated with distgit and bugzilla
2024-07-22 15:31:03 <@humaton:fedora.im> that is Blocker bugs and Freeze exception 
2024-07-22 15:31:16 <@humaton:fedora.im> they are both simillar in workflow with some differences
2024-07-22 15:31:20 <@humaton:fedora.im> did we missed something?
2024-07-22 15:31:57 <@kparal:matrix.org> blockers and freeze exceptions is basically the same process, just uses different field names
2024-07-22 15:32:07 <@humaton:fedora.im> yeah
2024-07-22 15:32:23 <@kparal:matrix.org> I believe we can find other our processes that would be impacted
2024-07-22 15:32:26 <@humaton:fedora.im> are there other processes that are not in docs? that we should take look at?
2024-07-22 15:32:43 <@kparal:matrix.org> But I wasn't clear whether we should look at it and submit feedback somewhere
2024-07-22 15:32:44 <@humaton:fedora.im> please point me to docs I searched but those two are the only I found
2024-07-22 15:33:12 <@humaton:fedora.im> yeah for those we captured we translated them into user stories over here https://pagure.io/fedora-infra/arc/issue/164
2024-07-22 15:33:12 <@kparal:matrix.org> There was a "Intent to start ARC investigation git-forge replacement" email in devel list in Apr, to which I replied in May and asked some questions, but never received any answers
2024-07-22 15:33:32 <@kparal:matrix.org> so we decided to wait, we weren't clear whether it's just some inception phase or what
2024-07-22 15:33:51 <@humaton:fedora.im> the tracker its just ingestion point for the stories, I am going to sort them to groups QA,packaging,releng 
2024-07-22 15:33:58 <@humaton:fedora.im> any intup is welcome
2024-07-22 15:34:14 <@sumantrom:fedora.im> also, I remember proposing František Zatloukal from our team , did someone get in touch with him ? 
2024-07-22 15:34:27 <@humaton:fedora.im> oh that is on me, there was bunch of things happening around that time
2024-07-22 15:34:34 <@kparal:matrix.org> so should we now start looking into our processes, describe them in detail and post them somewhere?
2024-07-22 15:34:38 <@humaton:fedora.im> let me get back to the email and answer your questions
2024-07-22 15:35:04 <@humaton:fedora.im> Do you have any docs like we do for releng or infra?
2024-07-22 15:35:12 <@humaton:fedora.im> of its more tribal knowledge
2024-07-22 15:35:22 <@kparal:matrix.org> > Tomas, the email title and the referenced ticket only talk about "git forge", but your description also talks about Bugzilla replacement. So should we also mention Bugzilla-related requirements in that ticket? (As QA, we might have a lot of those).
2024-07-22 15:35:22 <@kparal:matrix.org> This was my reply:
2024-07-22 15:35:22 <@kparal:matrix.org> > Also, what is the deadline for providing the requirements?
2024-07-22 15:35:22 <@kparal:matrix.org> > Should we separate the requirements into "must have" and "nice to have"?
2024-07-22 15:35:45 <@kparal:matrix.org> we have some SOPs here: https://fedoraproject.org/wiki/Category:QA_SOPs
2024-07-22 15:35:54 <@kparal:matrix.org> but they don't cover nearly everything
2024-07-22 15:35:57 <@humaton:fedora.im> So the council didnt frame it properly
2024-07-22 15:36:30 <@kparal:matrix.org> I think it's better for us to look at it and create some document, it will be more complete than if you look at our incomplete docs
2024-07-22 15:36:41 <@humaton:fedora.im> we are looking into changing the gitforge but bugzilla is going away as well. And it seems that it make sense to use integrated ticket trackers for package related stuff
2024-07-22 15:36:57 <@amoloney:fedora.im> I can help here with some guidelines :)
2024-07-22 15:37:11 <@sumantrom:fedora.im> hey @aoife!
2024-07-22 15:37:11 <@kparal:matrix.org> welcome, Aoife!
2024-07-22 15:37:46 <@kparal:matrix.org> are you pinged on each "SOP" keyword being mentioned in meetings? 😄 
2024-07-22 15:38:09 <@amoloney:fedora.im> Feels like it 🤣
2024-07-22 15:38:45 <@kparal:matrix.org> I'm afraid the meeting bot won't handle threaded replies, but let's see, I haven't tested that yet 🙂
2024-07-22 15:38:49 <@amoloney:fedora.im> Kamil Páral: the instruction for ARC investigation is to look at dist-git first as part of the gir forge replacement, *but* I think framing your requirements for bugzilla-interactions are relevant, if still a bit premature for this portion of the investigation 
2024-07-22 15:38:58 <@humaton:fedora.im> If you can do that the group is meeting every Wednesday 8:30 UTC and we can discuss it.
2024-07-22 15:39:03 <@amoloney:fedora.im> @kparal:matrix.org: the instruction for ARC investigation is to look at dist-git first as part of the git forge replacement, but I think framing your requirements for bugzilla-interactions are relevant, if still a bit premature for this portion of the investigation
2024-07-22 15:40:14 <@sumantrom:fedora.im> I can make it for 8:30UTC .. but i believe having a doc will help both of us and agree with kamil 
2024-07-22 15:40:23 <@sumantrom:fedora.im> damn :)
2024-07-22 15:40:32 <@humaton:fedora.im> Oh what I mean is we can discuss the doc as a group 
2024-07-22 15:40:42 <@kparal:matrix.org> Ok, we'll try to look at our processes and write them down wrt distgit and bugzilla, but it'll take some time
2024-07-22 15:40:50 <@kparal:matrix.org> especially with all the holidays now
2024-07-22 15:41:09 <@kparal:matrix.org> then we can post it to your tracker and discuss it with you in the meeting
2024-07-22 15:41:24 <@humaton:fedora.im> Sure if you can focus on distgit first, because with bugzilla I think we have some more time.
2024-07-22 15:41:36 <@amoloney:fedora.im> Wrt deadline's for requirements submissions, I think Akashdeep mentioned a deadline we had set in a discussion for early June, but it was not intended to be a hard stop as the scope of the investigation needed to be a little flexible given holidays, travel, etc
2024-07-22 15:42:05 <@amoloney:fedora.im> So consider this discussion with jednorozec: (and to a smaller extent me) as part of the due diligence for the investigation 
2024-07-22 15:42:23 <@humaton:fedora.im> Yeah we had plans and deadlines and just forgot that rhel7 is going EOL at the same time :D
2024-07-22 15:42:45 <@kparal:matrix.org> that's how plans work
2024-07-22 15:43:37 <@amoloney:fedora.im> You can expect more firmer deadlines and milestones to be formed and published post flock for the investigation, review, decision and ultimate migration plan to be set against
2024-07-22 15:43:39 <@kparal:matrix.org> !info distigt replacement investigation is ongoing and we should collect and describe our requirements and submit them to CPE
2024-07-22 15:44:00 <@humaton:fedora.im> BTW if any of you are by any chance in Brno we could sit in a room and talk about it in person...
2024-07-22 15:45:01 <@sumantrom:fedora.im> all of these folks are in Brno :F
2024-07-22 15:45:09 <@sumantrom:fedora.im> *:D
2024-07-22 15:45:29 <@kparal:matrix.org> !action kparal to create a document for describing distgit-related QA processes and our requirements/feedback for the replacement
2024-07-22 15:45:41 <@amoloney:fedora.im> * amoloney goes back to lurking now and awaits a ping if needed :)
2024-07-22 15:45:47 <@kparal:matrix.org> that's not true, just some of us are in Brno
2024-07-22 15:45:55 <@kparal:matrix.org> thanks, Aoife
2024-07-22 15:46:34 <@derekenz:fedora.im> !Lurking
2024-07-22 15:46:55 <@kparal:matrix.org> !info bugzilla replacement process will come later, we don't need to focus on it atm, unless it's related to the distgit replacement within our processes
2024-07-22 15:47:10 <@kparal:matrix.org> I hope I described it correctly?
2024-07-22 15:47:18 <@humaton:fedora.im> +1
2024-07-22 15:47:29 <@humaton:fedora.im> that is what I had in mind
2024-07-22 15:48:13 <@kparal:matrix.org> !action everyone to collect our distgit-related processes, stories and requirements, once the document is live (see previous action item)
2024-07-22 15:48:32 <@kparal:matrix.org> thanks jednorozec for pinging us
2024-07-22 15:48:36 <@kparal:matrix.org> anything else on this topic?
2024-07-22 15:48:53 <@sumantrom:fedora.im> nothing from my end 
2024-07-22 15:48:57 <@humaton:fedora.im> all from me
2024-07-22 15:49:09 <@humaton:fedora.im> sorry for the late timings
2024-07-22 15:49:41 <@kparal:matrix.org> that's fine, thanks for stopping by
2024-07-22 15:49:47 <@kparal:matrix.org> !topic Open floor
2024-07-22 15:50:07 <@kparal:matrix.org> alright, anyone else has a topic to discuss?
2024-07-22 15:50:41 <@sumantrom:fedora.im> nothing else comes to mind
2024-07-22 15:51:21 <@kparal:matrix.org> bye Sumantro Mukherjee 
2024-07-22 15:51:22 <@sumantrom:fedora.im> cya folks!! :) 
2024-07-22 15:51:22 <@sumantrom:fedora.im> thanks Kamil Páral for hosting
2024-07-22 15:51:41 <@derekenz:fedora.im> Thank you!
2024-07-22 15:51:41 <@sumantrom:fedora.im> @kparal++
2024-07-22 15:52:27 <@kparal:matrix.org> alright, thanks everyone for coming today
2024-07-22 15:52:32 <@kparal:matrix.org> !endmeeting