#meeting-3:fedoraproject.org log

<@patrikp:matrix.org>

16:00:04

!startmeeting RELENG (2026-01-19)

<@meetbot:fedora.im>

16:00:07

Meeting started at 2026-01-19 16:00:04 UTC

<@meetbot:fedora.im>

16:00:07

The Meeting name is 'RELENG (2026-01-19)'

<@patrikp:matrix.org>

16:00:24

!info Meeting is 60 minutes MAX. At the end of 60, it STOPS.

<@patrikp:matrix.org>

16:00:24

!info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.

<@patrikp:matrix.org>

16:00:24

!meetingname releng

<@patrikp:matrix.org>

16:00:24

!chair nirik jnsamyak patrikp amedvede

<@meetbot:fedora.im>

16:00:27

The Meeting Name is now releng

<@nirik:matrix.scrye.com>

16:00:32

morning

<@amedvede:fedora.im>

16:00:37

hey all

<@patrikp:matrix.org>

16:00:46

Hello.

<@patrikp:matrix.org>

16:01:04

!topic Init process.

<@patrikp:matrix.org>

16:01:04

Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?

<@patrikp:matrix.org>

16:01:15

I have one thing for init if I may.

<@nirik:matrix.scrye.com>

16:02:10

go for it

<@patrikp:matrix.org>

16:02:24

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.

<@patrikp:matrix.org>

16:02:24

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.

<@patrikp:matrix.org>

16:02:57

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...

<@nirik:matrix.scrye.com>

16:04:50

sounds like it might be a good idea if we can all find a time...

<@amedvede:fedora.im>

16:05:00

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

<@nirik:matrix.scrye.com>

16:05:01

or perhaps use next meeting or something?

<@jnsamyak:matrix.org>

16:06:03

!hi

<@zodbot:fedora.im>

16:06:06

Samyak Jain (jnsamyak) - he / him / his

<@jnsamyak:matrix.org>

16:06:52

sure thing, we can plan a call for this

<@patrikp:matrix.org>

16:07:18

You would be willing to attend it Kevin?

<@patrikp:matrix.org>

16:07:45

If so then I can accommodate your busy schedule and you can pick a time that would suit.

<@nirik:matrix.scrye.com>

16:08:15

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. ;)

<@jnsamyak:matrix.org>

16:08:40

We can just use half of this meeting as well

<@amedvede:fedora.im>

16:09:19

I'm also think that we better use existing meeting instead of creating new ones

<@patrikp:matrix.org>

16:09:41

Either one sounds good to me.

<@jnsamyak:matrix.org>

16:10:10

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)

<@patrikp:matrix.org>

16:10:14

But e.g. next week is the sprint planning and it's directly BEFORE the releng meeting, not after.

<@amedvede:fedora.im>

16:10:17

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

<@jnsamyak:matrix.org>

16:10:33

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)

<@jnsamyak:matrix.org>

16:11:12

I think we should use this meeting only

<@amedvede:fedora.im>

16:12:55

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

<@nirik:matrix.scrye.com>

16:13:04

and sorry I have to usually step away during this meeting to feed cats. ;(

<@amedvede:fedora.im>

16:13:55

I'm having lunch after this meet, jeez wanna be a cat

<@amedvede:fedora.im>

16:14:09

I'm having lunch after this meet, jeez wanna be a cat xd

<@jnsamyak:matrix.org>

16:15:17

circling back - i think it is fine to use this meeting; if there are conflicts we can make a change.

<@patrikp:matrix.org>

16:16:18

Sure. That's all I had for init.

<@nirik:matrix.scrye.com>

16:16:28

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.

<@patrikp:matrix.org>

16:17:12

Anything else for init? Not sure if the mass rebuild falls under this section or "scheduled actions coming up" since it's in progress.

<@amedvede:fedora.im>

16:17:54

nothing from me for init

<@jnsamyak:matrix.org>

16:19:31

let's discuss it it next one

<@patrikp:matrix.org>

16:20:13

!topic Scheduled actions coming up in the next week.

<@patrikp:matrix.org>

16:20:13

!link https://fedorapeople.org/groups/schedule/f-44/f-44-releng-tasks.html

<@patrikp:matrix.org>

16:20:13

!info Here we list/discuss anything about items that are due to be done in the next week.

<@jnsamyak:matrix.org>

16:22:28

So the mass rebuild is almost in its last movement, I have to check but for the failed builder issue, I resubmitted those tasks

<@jnsamyak:matrix.org>

16:22:53

I more inclined to do a merge carefelly after having a conversation about it from QE folks

<@nirik:matrix.scrye.com>

16:22:55

yeah, I think we should cancel all the stuck ones and call it done

<@nirik:matrix.scrye.com>

16:23:38

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.

<@nirik:matrix.scrye.com>

16:26:06

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.

<@jnsamyak:matrix.org>

16:27:13

sigh my bad i should have it run by you or run it

<@jnsamyak:matrix.org>

16:27:20

I'll check those about

<@jnsamyak:matrix.org>

16:27:35

do we need to run signing on them manually?

<@nirik:matrix.scrye.com>

16:30:37

so I think we need to use the same process as signing before branching.. basically get the list of unsigned, and sign them...

<@jnsamyak:matrix.org>

16:30:53

yeah same thought

<@jnsamyak:matrix.org>

16:30:59

let me work on it

<@jnsamyak:matrix.org>

16:31:05

and fix those

<@nirik:matrix.scrye.com>

16:31:06

https://docs.fedoraproject.org/en-US/infra/release_guide/sop_mass_branching/#_mass_resigning

<@jnsamyak:matrix.org>

16:31:15

yep yep

<@nirik:matrix.scrye.com>

16:31:23

we should be quick about it tho and merge today if we at all can...

<@jnsamyak:matrix.org>

16:32:21

./scripts_new/release-process/signing/koji_rpm_signer.py --just-list --tag f44-rebuild fedora-44 | grep src | sed -e 's|.src||' > unsigned-packages

<@jnsamyak:matrix.org>

16:32:21

```

<@jnsamyak:matrix.org>

16:32:21

```

<@jnsamyak:matrix.org>

16:32:30

This should look something like this;

<@nirik:matrix.scrye.com>

16:33:06

yeah. looks plausable. ;)

<@patrikp:matrix.org>

16:33:50

Alright, backlog refinement?

<@nirik:matrix.scrye.com>

16:36:07

sure, but I have a cat hitting my head with his tail.. back in a min

<@patrikp:matrix.org>

16:36:19

!link https://forge.fedoraproject.org/releng/tickets/issues

<@patrikp:matrix.org>

16:36:19

!topic Tickets that need attention.

<@patrikp:matrix.org>

16:36:19

!info This is the time where you can bring up RelEng tickets for discussion, for example if there are blockers, etc.

<@jnsamyak:matrix.org>

16:36:29

okay so the unsigned grep script is running

<@patrikp:matrix.org>

16:37:09

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...

<@jnsamyak:matrix.org>

16:38:48

no please go ahead

<@jnsamyak:matrix.org>

16:38:52

you dont have to wait

<@patrikp:matrix.org>

16:39:07

Yeah, I'm looking at the tracker, unsure where to start.

<@jnsamyak:matrix.org>

16:39:11

if you have a potential ticket to groom bringit

<@jnsamyak:matrix.org>

16:43:59

side note: unsigned list always takes hours to run i hope it runs faster

<@patrikp:matrix.org>

16:45:29

Silver lining is that I see quite a few that I think could be closed.

<@jnsamyak:matrix.org>

16:46:28

https://koji.fedoraproject.org/koji/builds?state=0&userID=releng&order=-build_id so these are the ones stuck

<@jnsamyak:matrix.org>

16:46:35

I'll cancel them up

<@nirik:matrix.scrye.com>

16:47:05

yeah, we have a lot of old tickets...

<@nirik:matrix.scrye.com>

16:47:24

one way would be to look at them in least recently modified order

<@nirik:matrix.scrye.com>

16:47:32

ie, the oldest ones first

<@amedvede:fedora.im>

16:48:12

least recently modified not showing in good way on forge

<@amedvede:fedora.im>

16:48:29

i mean there is no timeframe exactly on ticket

<@amedvede:fedora.im>

16:48:51

i mean there is no exact time of modification on ticket

<@nirik:matrix.scrye.com>

16:50:13

yeah: https://forge.fedoraproject.org/releng/tickets/issues?q=&type=all&sort=leastupdate&state=open&labels=&milestone=0&project=0&assignee=0&poster=0

<@amedvede:fedora.im>

16:50:37

yeah, but it doesn't show last modification date from tickets overview

<@nirik:matrix.scrye.com>

16:51:01

yeah, but it sorts by it anyhow right?

<@amedvede:fedora.im>

16:51:23

yeah

<@patrikp:matrix.org>

16:51:49

OK how about this one (with 9 minutes to go in the meeting 🤣):

<@patrikp:matrix.org>

16:51:49

https://forge.fedoraproject.org/releng/tickets/issues/9153

<@jnsamyak:matrix.org>

16:52:40

[stuck builds](https://koji.fedoraproject.org/koji/builds?state=0&userID=releng&order=-build_id) are cancelled

<@nirik:matrix.scrye.com>

16:54:05

I am not sure what the status of this one is.

<@nirik:matrix.scrye.com>

16:55:07

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.

<@patrikp:matrix.org>

16:57:25

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...

<@patrikp:matrix.org>

16:57:32

Next chair?

<@patrikp:matrix.org>

16:57:38

!info Next chair January 26th: ?

<@patrikp:matrix.org>

16:57:38

!topic Choose next chair.

<@jnsamyak:matrix.org>

16:58:17

26th is indian holiday btw

<@jnsamyak:matrix.org>

16:58:25

so I might not be there

<@amedvede:fedora.im>

16:58:35

i can take next chair

<@patrikp:matrix.org>

16:59:00

Oh no, you might miss sprint retro and planning? Terrible fate, I don't envy you.

<@patrikp:matrix.org>

16:59:16

!info Next chair January 26th: Anton

<@patrikp:matrix.org>

16:59:50

And I think that is all for today...

<@patrikp:matrix.org>

17:00:00

!endmeeting

<@patrikp:matrix.org>

17:00:00

!info Thank you all for coming!