releng
LOGS
<@patrikp:matrix.org>
15:05:13
!startmeeting RELENG (2026-09-21)
<@meetbot:fedora.im>
15:05:15
Meeting started at 2026-09-21 15:05:13 UTC
<@meetbot:fedora.im>
15:05:15
The Meeting name is 'RELENG (2026-09-21)'
<@patrikp:matrix.org>
15:05:19
Noice.
<@patrikp:matrix.org>
15:05:27
!meetingname releng
<@patrikp:matrix.org>
15:05:27
!chair nirik jnsamyak patrikp
<@patrikp:matrix.org>
15:05:27
!info Meeting is 60 minutes long at most. At the end of the hour it stops.
<@patrikp:matrix.org>
15:05:27
!info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.
<@meetbot:fedora.im>
15:05:29
The Meeting Name is now releng
<@nirik:matrix.scrye.com>
15:05:33
morning
<@patrikp:matrix.org>
15:05:38
!topic Init process.
<@patrikp:matrix.org>
15:05:38
!info This is a good time to bring up things like tickets that people are stuck on, blockers, tasks, requests, and/or features that require release engineering intervention.
<@patrikp:matrix.org>
15:05:58
Hello. I don't have anything for init, just a couple of questions about upcoming actions.
<@patrikp:matrix.org>
15:06:28
Anything you'd like to discuss in this section?
<@nirik:matrix.scrye.com>
15:06:58
I don't think so...
<@patrikp:matrix.org>
15:08:07
Next section would be chair for next week, but I'll be on PTO and calendar says Samyak will still be at the conference on Monday. Let's cancel next week's meeting?
<@nirik:matrix.scrye.com>
15:08:37
yeah, sounds reasonable to me...
<@patrikp:matrix.org>
15:09:25
!topic Choose next chair.
<@patrikp:matrix.org>
15:09:25
!info Next chair September 28th: MEETING CANCELLED
<@patrikp:matrix.org>
15:09:56
I will be away on Oct 5th as well, ordinarily I wouldn't mind assigning it to myself but I'll leave it empty for now.
<@patrikp:matrix.org>
15:10:16
!topic Scheduled actions coming up in the next week.
<@patrikp:matrix.org>
15:10:16
!info Here we discuss items that are due to be done in the next week.
<@patrikp:matrix.org>
15:10:16
<@nirik:matrix.scrye.com>
15:11:19
final freeze is really the next big thing... but not next week
<@patrikp:matrix.org>
15:12:55
So, since we have a release process section in the backlog, we can create the tickets in batches and in advance. On that note, I was wondering, looking at the schedule, which upcoming actions do we (not) do? Before final freeze there's "Retire FTI packages in NEW state".
<@patrikp:matrix.org>
15:13:15
We already did it once this cycle and it was handled by Samyak.
<@patrikp:matrix.org>
15:13:20
!releng 13473
<@zodbot:fedora.im>
15:13:22
**releng/tickets #13473** (https://forge.fedoraproject.org/releng/tickets/issues/13473):**F45 Cycle: Retire FTI packages in NEW state**
<@zodbot:fedora.im>
15:13:22
<@zodbot:fedora.im>
15:13:22
● **Closed** a month ago
<@zodbot:fedora.im>
15:13:22
● **Opened:** a month ago by patrikp
<@zodbot:fedora.im>
15:13:22
● **Last Updated:** a month ago
<@zodbot:fedora.im>
15:13:22
● **Assignee:** jnsamyak
<@patrikp:matrix.org>
15:13:58
Is there a duplicate by accident or it should actually happen multiple times per cycle?
<@nirik:matrix.scrye.com>
15:14:01
huh, perhaps it's in the wrong place in the schedule?
<@nirik:matrix.scrye.com>
15:14:11
no, it should only be once I thought...
<@patrikp:matrix.org>
15:14:46
!releng 13277
<@zodbot:fedora.im>
15:14:48
**releng/tickets #13277** (https://forge.fedoraproject.org/releng/tickets/issues/13277):**Retire FTI packages stuck in NEW state - F44 round two**
<@zodbot:fedora.im>
15:14:48
<@zodbot:fedora.im>
15:14:48
● **Closed** 6 months ago
<@zodbot:fedora.im>
15:14:48
● **Opened:** 6 months ago by churchyard
<@zodbot:fedora.im>
15:14:48
● **Last Updated:** 6 months ago
<@zodbot:fedora.im>
15:14:48
● **Assignee:** Not Assigned
<@patrikp:matrix.org>
15:14:55
Looks like it's intended.
<@nirik:matrix.scrye.com>
15:15:32
seems odd to me, but ok...
<@nirik:matrix.scrye.com>
15:15:42
I guess we should have a new ticket on it?
<@patrikp:matrix.org>
15:15:48
I can create it.
<@patrikp:matrix.org>
15:16:11
Do I tag Miro afterwards? Or do we handle it ourselves from now on?
<@nirik:matrix.scrye.com>
15:16:13
sounds good
<@patrikp:matrix.org>
15:16:40
Pretty sure it's not too difficult and I believe Samyak was working on an SOP so we should have that as well going forward...
<@nirik:matrix.scrye.com>
15:17:26
I think there was a sop now yeah...
<@nirik:matrix.scrye.com>
15:18:25
I can't seem to find it tho.
<@nirik:matrix.scrye.com>
15:18:41
ah, not merged yet
<@nirik:matrix.scrye.com>
15:18:42
https://forge.fedoraproject.org/infra/docs/pulls/544
<@nirik:matrix.scrye.com>
15:19:08
there's some changes to be made to it.
<@patrikp:matrix.org>
15:19:19
Nice, it already has feedback from Miro, so we should have that ready for the following cycles.
<@nirik:matrix.scrye.com>
15:19:24
so, perhaps we ask churchyard to run it one last time and sort our the sop ?
<@patrikp:matrix.org>
15:20:59
Yes. Either that or Samyak can do round 2 and finish the SOP. I'll create the ticket and tag them both in it.
<@nirik:matrix.scrye.com>
15:21:12
sounds good
<@patrikp:matrix.org>
15:22:42
I had another question that's related to "Retire all packages with broken deps" that is supposed to happen on the same day as the freeze. Do you know more about it? I don't see an SOP and I can't seem to find such a ticket in the history. (this should be less of an issue going forward as we started using the release-process label)
<@jnsamyak:matrix.org>
15:22:46
0/ i’m here but on pto back tomorrow
<@patrikp:matrix.org>
15:23:15
PTO? Shoo!
<@jnsamyak:matrix.org>
15:23:18
my 10 days of fasting are in progress first 5 days are usually triggering but feeling better now and four more days left but should be back tomorrow
<@nirik:matrix.scrye.com>
15:24:38
I don't know that we have ever done that... I'd have to look for history on it. I suspect that was something that was desired, but never put in place? not sure... but I don't recall ever doing it in the past
<@patrikp:matrix.org>
15:24:53
Neither do I.
<@patrikp:matrix.org>
15:25:11
It does sound like a reasonable thing to do though. Oh well.
<@nirik:matrix.scrye.com>
15:26:03
a search shows it was done in 2017... but I don't see before or after.
<@patrikp:matrix.org>
15:26:21
So no need to create a ticket for it then?
<@jnsamyak:matrix.org>
15:26:59
any immediate fires for me to look at?
<@patrikp:matrix.org>
15:27:17
Not that I'm aware of personally.
<@jnsamyak:matrix.org>
15:27:30
cool cool
<@patrikp:matrix.org>
15:27:39
As an aside 10 days of fasting is very hardcore.
<@nirik:matrix.scrye.com>
15:27:49
yeah, wow.
<@patrikp:matrix.org>
15:27:53
3 is reasonable for health but 10... Oof.
<@jnsamyak:matrix.org>
15:28:57
hehe ties with my religious beliefs also but can talk later about it please continue
<@nirik:matrix.scrye.com>
15:31:01
https://forge.fedoraproject.org/releng/tickets/issues/6877
<@nirik:matrix.scrye.com>
15:32:17
ie, it was done for a short time, but there were issues and it was stopped.
<@patrikp:matrix.org>
15:32:57
Last question I had about the schedule and ticket creation. Would you be opposed to creating all tickets related to the release process in one big batch at the beginning of the cycle? Then they can sit in the backlog "Release Process" section until their time comes.
<@nirik:matrix.scrye.com>
15:33:47
sure, thats an approach too...
<@patrikp:matrix.org>
15:35:47
I think that's all for this section. Shall we do some tickets?
<@nirik:matrix.scrye.com>
15:35:52
forge also has 'milestones' that could perhaps work to show them in series... although I have no played with it.
<@patrikp:matrix.org>
15:36:16
Good thinking, exploring the new features and possibilities of the new forge is worth looking into.
<@patrikp:matrix.org>
15:37:09
I don't even know how you managed to dig this one up tbh. I was unsuccessful based on my chosen keywords.
<@patrikp:matrix.org>
15:37:39
But release process tickets are in a category of their own so it makes sense to distinguish between them and others.
<@patrikp:matrix.org>
15:37:49
AND we know about them well in advance.
<@nirik:matrix.scrye.com>
15:39:05
yeah.
<@patrikp:matrix.org>
15:39:38
!topic Tickets.
<@patrikp:matrix.org>
15:39:38
!info This section goes over old tickets, ordered from least recently touched.
<@patrikp:matrix.org>
15:39:38
<@patrikp:matrix.org>
15:40:27
How does this section interact with the newly introduced backlog refinement sessions we do with the PO?
<@nirik:matrix.scrye.com>
15:41:00
no idea.
<@nirik:matrix.scrye.com>
15:42:54
I'm happy to discuss tickets as needed...
<@patrikp:matrix.org>
15:43:08
!releng 11782
<@zodbot:fedora.im>
15:43:10
**releng/tickets #11782** (https://forge.fedoraproject.org/releng/tickets/issues/11782):**Update bootloader components assignee to "Bootloader Engineering Team"for Improved collaboration**
<@zodbot:fedora.im>
15:43:10
<@zodbot:fedora.im>
15:43:10
● **Opened:** 2 years ago by raravind
<@zodbot:fedora.im>
15:43:10
● **Last Updated:** a year ago
<@zodbot:fedora.im>
15:43:10
● **Assignee:** Not Assigned
<@nirik:matrix.scrye.com>
15:43:20
perhaps if you have more questions about some in other places you can bring them here for more input?
<@nirik:matrix.scrye.com>
15:44:23
I'm not sure where this one is...
<@nirik:matrix.scrye.com>
15:44:53
I guess it's not done?
<@nirik:matrix.scrye.com>
15:45:37
propose: ask on ticket if things are still desired, figure out whats left to do if so?
<@patrikp:matrix.org>
15:46:42
Last comment would indicate that it's still desired and they have the mailing list.
<@nirik:matrix.scrye.com>
15:47:22
note that normally these are infra tickets... but oh well.
<@nirik:matrix.scrye.com>
15:47:42
I guess I can try and see whats left...
<@nirik:matrix.scrye.com>
15:47:47
we have a sop.
<@nirik:matrix.scrye.com>
15:48:23
well, a howto
<@nirik:matrix.scrye.com>
15:48:30
https://docs.fedoraproject.org/en-US/infra/howtos/groups_in_fedora/#_pkgdb_groups
<@patrikp:matrix.org>
15:49:38
I vaguely recall doing this for another ticket in the past.
<@patrikp:matrix.org>
15:50:53
Or parts of it.
<@nirik:matrix.scrye.com>
15:51:10
if you would like to do it, feel free. ;)
<@patrikp:matrix.org>
15:51:27
But I think I got blocked by lack of sysadmin-main powers.
<@nirik:matrix.scrye.com>
15:51:30
or I can try and look.
<@nirik:matrix.scrye.com>
15:51:48
yeah, the pagure-admin part does need sysadmin-main indeed.
<@nirik:matrix.scrye.com>
15:53:55
I've got cats eager for breakfast... will have to go feed them in a few.
<@patrikp:matrix.org>
15:54:06
Let's leave it for now and I'll make a note to ask Samyak about it during tomorrow's call, he outlined a plan in one of the comments.
<@nirik:matrix.scrye.com>
15:54:14
ok
<@patrikp:matrix.org>
15:54:28
Feel free to go feed the cats and we can call it a wrap?
<@nirik:matrix.scrye.com>
15:54:55
sounds good. Thanks @patrikp:matrix.org
<@patrikp:matrix.org>
15:55:07
!info Thank you all for coming!
<@patrikp:matrix.org>
15:55:07
!endmeeting