Meeting started at 2026-06-01 15:00:12 UTC

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

!chair nirik jnsamyak patrikp

The Meeting Name is now releng

morning

Hello! Welcome!

Anything from anyone for init? I don't personally have anything.

hello folks! how’s everyone doing?

nothing from me off hand.

not from me too, just migrations bits, before flock we need to ensure that we have migrated all the bits to new forge

I really don't see how scm-requests will move by flock. ;)

anything particular we are lacking right now? i think fedora-scam-requests and kiwi-descriptions is we are importantly missing

Could you say more, please? I haven't started looking into it yet so extra context is always welcome.

yeah, those... there's other repos for other places in fedora, but those for releng.

changing fedora-scm-requests to move to forge requires changing fedpkg and then pushing updates of it out and then getting all maintainers to update to that. Thats not going to be a super quick process.

i think we opened a ticket for fedpkg update not really looked too deep

!releng 13369

**releng/tickets #13369** (https://forge.fedoraproject.org/releng/tickets/issues/13369):**[ fedora-scm-requests ] - Update fedpkg**

● **Assignee:** patrikp

● **Last Updated:** an hour ago

● **Opened:** 4 days ago by humaton

Oh i had one bits for init - I also want to look at automating bits, do you folks want to propose or see areas of processes that we can automate?

Is there any chance you could give me a few pointers there Kevin? The ticket just says to update fedpkg.

In a comment asynchronously works just as well.

right now 'fedpkg request-repo' and 'fedpkg request-branch' file tickets in https://pagure.io/releng/fedora-scm-requests/issues. They would need to adjust to filing them in forge.fedoraproject.org... and the toddler would need to handle processing those, etc

or action runner (as I think tomas has suggested)

!releng 13370

● **Opened:** 4 days ago by humaton

**releng/tickets #13370** (https://forge.fedoraproject.org/releng/tickets/issues/13370):**[fedora-scm-requests] - Create forgejo workflow for processing tickets**

● **Last Updated:** an hour ago

● **Assignee:** patrikp

I need to do some investigative work here. Thanks for the information.

yes!

One idea would be the EOL process, I should have the updated SOP soonish. Another would be parts of mass branching.

coming back to this ⭕️

Just throw our docs into a LLM, ask it what could be automated, and then tell it to automate it. It's 2026 and we're fully agentic now. I don't see what's so difficult about this.

uh huh. ;)

mass branching bits are already in the tickets at least I want to see if there are process also if we can improve on - we should look more on such requests every month or so

so we don’t go out of touch

i would still like us to work on the most day to day work we do as associates which can solve our immediate problems, still real life problems can be explained by people who actually do work

This step could be automated for sure.

https://docs.fedoraproject.org/en-US/infra/release_guide/sop_release_eol/#_stage_the_eol_release_to_archive

For now I plan to at least change the relative paths to absolute paths for some clarity. But it'd be nice not to have to do the rsyncs manually as we know all the paths in advance and it's many hundreds of GB.

Shall we move on?

Sure. I need to run and feed cats here in a few... they are milling. ;)

yes i’ll try to make it to next meeting or something as official topic

Speaking of next meeting, anybody want to take a stab at chairing it?

sure

!info Next chair June 8th: Samyak

Notifications for retirement of packages with security issues Tue 2026-06-02

Is this something that we actually handle? Or Miro? Should we have a ticket open for it?

We haven't. There was a proposed process that never really got finalized.

I think it should be removed from the schedule until / unless it gets clarified.

yeah

need to actually reopen that discussion talk about it and see what needs to be done or close it

Removed from the schedule? May be easier and faster to finalize the process. 🤣

Someone proposed something, a bunch of discussion and a plan, but at the time releng said "Great, but we don't have cycles to do this" and then it just never went anywhere.

well, not so sure, but you can try. ;)

Is this something that would have to be brought up before FESCo then? And it already has and there's a ticket for it somewhere?

yes, and there were tickets and lots of devel list discussions in the past.

!releng 7793

● **Assignee:** Not Assigned

**releng/tickets #7793** (https://forge.fedoraproject.org/releng/tickets/issues/7793):**Implement new Fedora Security policy for retiring packages with security bugs**

● **Closed** 2 years ago

● **Opened:** 7 years ago by huzaifas

● **Last Updated:** 2 years ago

ouuuu good find

https://pagure.io/fesco/issue/2956

AGREED: In the current environment, FESCo feels that the CVE bug process is insufficient to support implementing this policy. This can be revisited in the future if conditions improve. (+6, 0, -0) (sgallagh, 18:23:40)

anyhow, feeding cats, back in a min

oho!

With Aoife back, perhaps there is a chance of removing it from the schedule with these two links? Is deleting it (for now) what we'd like to do then? I can try and reach out.

I think yeah reach out to aoife we can sort it out again if required

I think yeah reach out to aoife we can sort it out again if required again

Alrighty, a few tickets before we close it out? Or do you have any other topic you'd like to bring up?

morning from me

nothing from me

back.

Nothing here off hand. I still hope to trawl through releng tickets and close some/move some along...

!releng 10160

**releng/tickets #10160** (https://forge.fedoraproject.org/releng/tickets/issues/10160):**RFE in failed-composes list the DOOMED resons first**

● **Opened:** 4 years ago by churchyard

● **Last Updated:** 2 years ago

● **Assignee:** Not Assigned

either just close it, or refile on compose-tracker?

for all the releng related we try to consolidate in tickets repo itself

Closed with the reasoning given by Kevin.

but seems like a good request - why do we need to close?

It seems pretty minor to me... but also it is something that has to change in compose-tracker right? so not sure why it would need to be tracked in releng?

but perhaps I am missing something.

I’ll try to explain the structure from my head but i really need to head out

i think let’s leave it open for day, i’ll try to gather my thoughts once - and put it in the comment

Well, I already closed it unfortunately. But feel free to re-open?

One more or close it out for the day?

feel free to but i have to head out

thank you for running today

Sounds like a good place to end it then. Have a reasonably good start to the week everyone.