2026-01-19 16:00:04 <@patrikp:matrix.org> !startmeeting RELENG (2026-01-19)
2026-01-19 16:00:07 <@meetbot:fedora.im> Meeting started at 2026-01-19 16:00:04 UTC
2026-01-19 16:00:07 <@meetbot:fedora.im> The Meeting name is 'RELENG (2026-01-19)'
2026-01-19 16:00:24 <@patrikp:matrix.org> !info Meeting is 60 minutes MAX. At the end of 60, it STOPS.
2026-01-19 16:00:24 <@patrikp:matrix.org> !info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.
2026-01-19 16:00:24 <@patrikp:matrix.org> !meetingname releng
2026-01-19 16:00:24 <@patrikp:matrix.org> !chair nirik jnsamyak patrikp amedvede
2026-01-19 16:00:27 <@meetbot:fedora.im> The Meeting Name is now releng
2026-01-19 16:00:32 <@nirik:matrix.scrye.com> morning
2026-01-19 16:00:37 <@amedvede:fedora.im> hey all
2026-01-19 16:00:46 <@patrikp:matrix.org> Hello.
2026-01-19 16:01:04 <@patrikp:matrix.org> !topic Init process.
2026-01-19 16:01:04 <@patrikp:matrix.org> Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?
2026-01-19 16:01:15 <@patrikp:matrix.org> I have one thing for init if I may.
2026-01-19 16:02:10 <@nirik:matrix.scrye.com> go for it
2026-01-19 16:02:24 <@patrikp:matrix.org> Having a couple of bullet points as a starting point about what is needed, how to investigate, in which direction to look, coupled with story points would make it much easier to pull things from the backlog into the sprint when we do the planning.
2026-01-19 16:02:24 <@patrikp:matrix.org> Would it be possible for us to have a longer session of backlog refinement in the near future? The Agile mandate requires story points but the vast majority of the tickets still have low/medium/high trouble.
2026-01-19 16:02:57 <@patrikp:matrix.org> I often struggle to say what I want to pull in because I'm unsure of what is needed and unable to scope it properly...
2026-01-19 16:04:50 <@nirik:matrix.scrye.com> sounds like it might be a good idea if we can all find a time...
2026-01-19 16:05:00 <@amedvede:fedora.im> IMHO, we can do it once in two weeks, e.g week 1 discuss usual staf, week 2 prepare tickets that we would like to work on and discuss with creating bullet points of what needs do be done
2026-01-19 16:05:01 <@nirik:matrix.scrye.com> or perhaps use next meeting or something?
2026-01-19 16:06:03 <@jnsamyak:matrix.org> !hi
2026-01-19 16:06:06 <@zodbot:fedora.im> Samyak Jain (jnsamyak) - he / him / his
2026-01-19 16:06:52 <@jnsamyak:matrix.org> sure thing, we can plan a call for this 
2026-01-19 16:07:18 <@patrikp:matrix.org> You would be willing to attend it Kevin?
2026-01-19 16:07:45 <@patrikp:matrix.org> If so then I can accommodate your busy schedule and you can pick a time that would suit.
2026-01-19 16:08:15 <@nirik:matrix.scrye.com> so, not this meeting, but a new one off ? yeah, happy to help if I can... but timezones are not great between me and all of you. ;)
2026-01-19 16:08:40 <@jnsamyak:matrix.org> We can just use half of this meeting as well
2026-01-19 16:09:19 <@amedvede:fedora.im> I'm also think that we better use existing meeting instead of creating new ones
2026-01-19 16:09:41 <@patrikp:matrix.org> Either one sounds good to me.
2026-01-19 16:10:10 <@jnsamyak:matrix.org> I can add a tag inititally for it saying needs-refinement and we can all go over with it next week -> but we can take a look at it before (10 tickets each week will be a good exercise)
2026-01-19 16:10:14 <@patrikp:matrix.org> But e.g. next week is the sprint planning and it's directly BEFORE the releng meeting, not after.
2026-01-19 16:10:17 <@amedvede:fedora.im> we don't need much time i guess, 2-3 tickets in 1 week = 4-6 tickets in two weeks and this is exactly the plan for sprint
2026-01-19 16:10:33 <@jnsamyak:matrix.org> I can add a tag inititally for it saying needs-refinement and we can all go over with it next week -> but we can take a look at it before so we know what we are talking and discussing (10 tickets each week will be a good exercise)
2026-01-19 16:11:12 <@jnsamyak:matrix.org> I think we should use this meeting only 
2026-01-19 16:12:55 <@amedvede:fedora.im> i agree, maybe plan some tickets for next sprint and ask people opinion on infra meet at thu is right way how to prepare for next sprint
2026-01-19 16:13:04 <@nirik:matrix.scrye.com> and sorry I have to usually step away during this meeting to feed cats. ;(
2026-01-19 16:13:55 <@amedvede:fedora.im> I'm having lunch after this meet, jeez wanna be a cat
2026-01-19 16:14:09 <@amedvede:fedora.im> I'm having lunch after this meet, jeez wanna be a cat xd
2026-01-19 16:15:17 <@jnsamyak:matrix.org> circling back - i think it is fine to use this meeting; if there are conflicts we can make a change.
2026-01-19 16:16:18 <@patrikp:matrix.org> Sure. That's all I had for init.
2026-01-19 16:16:28 <@nirik:matrix.scrye.com> ha. Yeah, the cats seem to have some kind of inner clock. They won't leave me alone if they don't get food in time.
2026-01-19 16:17:12 <@patrikp:matrix.org> Anything else for init? Not sure if the mass rebuild falls under this section or "scheduled actions coming up" since it's in progress.
2026-01-19 16:17:54 <@amedvede:fedora.im> nothing from me for init
2026-01-19 16:19:31 <@jnsamyak:matrix.org> let's discuss it it next one
2026-01-19 16:20:13 <@patrikp:matrix.org> !topic Scheduled actions coming up in the next week.
2026-01-19 16:20:13 <@patrikp:matrix.org> !link https://fedorapeople.org/groups/schedule/f-44/f-44-releng-tasks.html
2026-01-19 16:20:13 <@patrikp:matrix.org> !info Here we list/discuss anything about items that are due to be done in the next week.
2026-01-19 16:22:28 <@jnsamyak:matrix.org> So the mass rebuild is almost in its last movement, I have to check but for the failed builder issue, I resubmitted those tasks
2026-01-19 16:22:53 <@jnsamyak:matrix.org> I more inclined to do a merge carefelly after having a conversation about it from QE folks
2026-01-19 16:22:55 <@nirik:matrix.scrye.com> yeah, I think we should cancel all the stuck ones and call it done
2026-01-19 16:23:38 <@nirik:matrix.scrye.com> but two things to note: 1) we should untag those things QE told us to in the ticket from the f44-rebuild tag if they were rebuilt... and 2) there's a number of unsigned packages we need to make sure are signed.
2026-01-19 16:26:06 <@nirik:matrix.scrye.com> The reason some are unsigned is that I thought I merged that pr to do signing, but somehow I didn't... and then jnsamyak did merge it, but it was not deployed on autosign01. I fixed that, but it was already running so a number of builds didn't get signed.
2026-01-19 16:27:13 <@jnsamyak:matrix.org> sigh my bad i should have it run by you or run it
2026-01-19 16:27:20 <@jnsamyak:matrix.org> I'll check those about
2026-01-19 16:27:35 <@jnsamyak:matrix.org> do we need to run signing on them manually?
2026-01-19 16:30:37 <@nirik:matrix.scrye.com> so I think we need to use the same process as signing before branching.. basically get the list of unsigned, and sign them...
2026-01-19 16:30:53 <@jnsamyak:matrix.org> yeah same thought
2026-01-19 16:30:59 <@jnsamyak:matrix.org> let me work on it
2026-01-19 16:31:05 <@jnsamyak:matrix.org> and fix those
2026-01-19 16:31:06 <@nirik:matrix.scrye.com> https://docs.fedoraproject.org/en-US/infra/release_guide/sop_mass_branching/#_mass_resigning
2026-01-19 16:31:15 <@jnsamyak:matrix.org> yep yep
2026-01-19 16:31:23 <@nirik:matrix.scrye.com> we should be quick about it tho and merge today if we at all can...
2026-01-19 16:32:21 <@jnsamyak:matrix.org> ./scripts_new/release-process/signing/koji_rpm_signer.py --just-list --tag f44-rebuild fedora-44 | grep src | sed -e 's|.src||' > unsigned-packages
2026-01-19 16:32:21 <@jnsamyak:matrix.org> ```
2026-01-19 16:32:21 <@jnsamyak:matrix.org> ```
2026-01-19 16:32:30 <@jnsamyak:matrix.org> This should look something like this; 
2026-01-19 16:33:06 <@nirik:matrix.scrye.com> yeah. looks plausable. ;)
2026-01-19 16:33:50 <@patrikp:matrix.org> Alright, backlog refinement?
2026-01-19 16:36:07 <@nirik:matrix.scrye.com> sure, but I have a cat hitting my head with his tail.. back in a min
2026-01-19 16:36:19 <@patrikp:matrix.org> !link https://forge.fedoraproject.org/releng/tickets/issues
2026-01-19 16:36:19 <@patrikp:matrix.org> !topic Tickets that need attention.
2026-01-19 16:36:19 <@patrikp:matrix.org> !info This is the time where you can bring up RelEng tickets for discussion, for example if there are blockers, etc.
2026-01-19 16:36:29 <@jnsamyak:matrix.org> okay so the unsigned grep script is running
2026-01-19 16:37:09 <@patrikp:matrix.org> Sorry about that. Usually in these text based meetings I see people start typing or say something one millisecond after I hit enter on topic change...
2026-01-19 16:38:48 <@jnsamyak:matrix.org> no please go ahead
2026-01-19 16:38:52 <@jnsamyak:matrix.org> you dont have to wait 
2026-01-19 16:39:07 <@patrikp:matrix.org> Yeah, I'm looking at the tracker, unsure where to start.
2026-01-19 16:39:11 <@jnsamyak:matrix.org> if you have a potential ticket to groom bringit
2026-01-19 16:43:59 <@jnsamyak:matrix.org> side note: unsigned list always takes hours to run i hope it runs faster
2026-01-19 16:45:29 <@patrikp:matrix.org> Silver lining is that I see quite a few that I think could be closed.
2026-01-19 16:46:28 <@jnsamyak:matrix.org> https://koji.fedoraproject.org/koji/builds?state=0&userID=releng&order=-build_id so these are the ones stuck
2026-01-19 16:46:35 <@jnsamyak:matrix.org> I'll cancel them up
2026-01-19 16:47:05 <@nirik:matrix.scrye.com> yeah, we have a lot of old tickets...
2026-01-19 16:47:24 <@nirik:matrix.scrye.com> one way would be to look at them in least recently modified order
2026-01-19 16:47:32 <@nirik:matrix.scrye.com> ie, the oldest ones first
2026-01-19 16:48:12 <@amedvede:fedora.im>  least recently modified not showing in good way on forge
2026-01-19 16:48:29 <@amedvede:fedora.im> i mean there is no timeframe exactly on ticket
2026-01-19 16:48:51 <@amedvede:fedora.im> i mean there is no exact time of modification on ticket
2026-01-19 16:50:13 <@nirik:matrix.scrye.com> yeah: https://forge.fedoraproject.org/releng/tickets/issues?q=&type=all&sort=leastupdate&state=open&labels=&milestone=0&project=0&assignee=0&poster=0
2026-01-19 16:50:37 <@amedvede:fedora.im> yeah, but it doesn't show last modification date from tickets overview
2026-01-19 16:51:01 <@nirik:matrix.scrye.com> yeah, but it sorts by it anyhow right?
2026-01-19 16:51:23 <@amedvede:fedora.im> yeah
2026-01-19 16:51:49 <@patrikp:matrix.org> OK how about this one (with 9 minutes to go in the meeting 🤣):
2026-01-19 16:51:49 <@patrikp:matrix.org> https://forge.fedoraproject.org/releng/tickets/issues/9153
2026-01-19 16:52:40 <@jnsamyak:matrix.org> [stuck builds](https://koji.fedoraproject.org/koji/builds?state=0&userID=releng&order=-build_id) are cancelled 
2026-01-19 16:54:05 <@nirik:matrix.scrye.com> I am not sure what the status of this one is.
2026-01-19 16:55:07 <@nirik:matrix.scrye.com> If we want to try and do the thing where pungi does this we should make a pungi RFE... but I could be wrong and it's already doing something, so someone should look into it and see what the current state is.
2026-01-19 16:57:25 <@patrikp:matrix.org> Well, we're nearly at time. Perhaps it would be more reasonable to bring specific tickets to you for help with pointers and story point estimates...
2026-01-19 16:57:32 <@patrikp:matrix.org> Next chair?
2026-01-19 16:57:38 <@patrikp:matrix.org> !info Next chair January 26th: ?
2026-01-19 16:57:38 <@patrikp:matrix.org> !topic Choose next chair.
2026-01-19 16:58:17 <@jnsamyak:matrix.org> 26th is indian holiday btw
2026-01-19 16:58:25 <@jnsamyak:matrix.org> so I might not be there
2026-01-19 16:58:35 <@amedvede:fedora.im> i can take next chair
2026-01-19 16:59:00 <@patrikp:matrix.org> Oh no, you might miss sprint retro and planning? Terrible fate, I don't envy you.
2026-01-19 16:59:16 <@patrikp:matrix.org> !info Next chair January 26th: Anton
2026-01-19 16:59:50 <@patrikp:matrix.org> And I think that is all for today...
2026-01-19 17:00:00 <@patrikp:matrix.org> !endmeeting
2026-01-19 17:00:00 <@patrikp:matrix.org> !info Thank you all for coming!