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