Meeting started at 2026-02-16 16:01:03 UTC

The Meeting name is 'RELENG (2026-02-16)'

The Meeting Name is now releng

!chair nirik jnsamyak patrikp amedvede

Hello. 👋

Hey all, how you doing?

Nice day of learning?

morning

morning

not bad for me, learned how to install custom PS1 var

lets move to open floor but I'm really curious how .bashrc or Kevin setup looks like

lets move it to open floor but I'm really curious how .bashrc or Kevin setup looks like

Hello

I watched a bunch of configmgmtcamp and fosdem videos. ;)

Finally I made my way to home like two hours back

I use zsh and oh-my-zsh with it. :)

A fellow zsh and oh-my-zsh enjoyer?

I would 100% watch a tech talk titled "How I do my computing" by Kevin Fenzi. Please and thank you.

okay, let me ask you, do you have something for Init?))

ha, thats a big topic. No, I don't think I have anything for init, other than beta freeze tomorrow... and I do have one item for open floor/later...

For init, I'm still looking at the branching SOP, it's taking too long so I split the attributes update to a separate PR and merged it so the docs (e.g. upcoming beta freeze) should show proper values.

We don’t have any blockers as of now for beta freeze, I checked it once, we are good to go

Next section?

What is the lacking, restructuring taking time? Any blockers there?

No blockers, it's formatting/reformatting/prettifying stuff and I'm currently not at home so doing it on a small laptop on a couch.

yeah, sound like not confy env

lets move to next topik

FTI were filed already, beta freeze tomorrow.

So beta freeze is go? Where did you check for possible blockers?

Look at tracker, all the approved changes if they are in, or if someone opens a ticket no rule book in general but this is all I look for

Also good to have a check with QE sometimes in case of blockers

I saw that you assigned yourself to the beta freeze ticket. Will you handle it then?

Yes

SOP seems pretty straightforward. At first glance, does it look right to you guys? Anything incorrect or missing?

https://docs.fedoraproject.org/en-US/infra/release_guide/sop_beta_freeze/

seems right to me. Just adjusting koji/bodhi to require manual updates and compose updates-testing repo from testing

wanted also to ask what are restrictions for us during final freeze. i know that builds shouldn't be marked as stable but what else? can we performe any actions for packages on not pending branches?

I can take a look, and fix it on the go tomorrow, and yeah the sop seems right and updated otherwise.

you can make changes to packages, but those updates will not go stable without a valid/accepted blocker or freeze exception.

until after the freeze.

okay, and freeze will last untill we make beta release?

until the day after the beta release (or final release for final) is accepted as go.

okay, thx for clarification

oh do you see it? its next topic comming

I'm not sure I have anything specific... we might want to look at the least recently touched tickets tho if we don't have any specific ones.

about that, i can throw tickets that looks interesting to me and discuss them

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

I'm curious if we can process it, with newly added script that removes tarballs

yeah, I think this is exactly that case

oh nice

it that case, reviews are wecome, but i think its good to use

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

I can try and look at it soonish...

Anton Medvedev: i'll do the reviews too, dont wait for the meeting to ask for reviews, tag us or let u sknow anytime

on forge you can also request review (on pr's anyhow) from a specific person(s)

on forge you can also request review (on pr's anyhow) from a specific person(s) or group(s)

1) where Matt got this interesting stats https://pagure.io/fedora-workstation/issue/500#comment-1001924

now qs about that one https://forge.fedoraproject.org/releng/tickets/issues/13207:

2) is it just require update configs where we introduce releases or something else as well?

just fedora-pungi change I think...

oh nice, its exactly what i did, i was curious if there something more underwater

and it would be nice to land it in rawhide/f44 today... so it's in before freeze.

there might be something in the sync script for release candidates?

nope, seems not. But there is a line in variants.xml that needs removed.

variants-fedora.xml rather

no there is not

feel free to send any concerns to ticket comments, I'll send there PR with removal after meet

okay, we can do some backlog polishing if you don't have anything

btw there will be Fedora 44 Blocker Review Meeting in case you folks want to attend after this one

i didn't check forge chat tbh, did you get response about creating releng user jnsamyak (at DevConf.IN 12-16 Feb)

we probably won't migrate compose-tracker for now because of freeze, but it would be nice to have it after)

oh no I didnt get time to do that, I can take a follow up tomorrow and give you that details

but I think I know a fix for it, wait let me try to do that now

oh, like teoreticall for tmp solution we can use my credentials for user that will create tickets automatically

oh, like theory for tmp solution we can use my credentials for user that will create tickets automatically

I think releng user credentials got updated. Did something you know of happened nirik ?

Not able to login in through accoutns.fpo

Not able to login in through accounts.fpo as releng user

I don't recall doing anything there...

nirik: also do we store releng user credentials in ansible-private? i wasn't able to locate anything so i added an entry in our bitwarden vault

I have credentials for it able to login through - accounts.fpo

bitwarden seems fine for that... since it's not directly used in ansible or anything.

yeah

note that we also have a releng-bot user that toddlers uses...

ok I need to look I added the rreleng user to forge-releng-owners, so it should be good.

hum... what does it need that for?

But, the new forge, reports it is disbaled, and we need to contact the adminstrator, I'll check with folks tomorrow.

just for info, do we have corporate bitwarden account which stores fedora account credentials?

able to migrate compose-tracker, and let releng bot open ticket for fedora-scm-request in later too? right Anton Medvedev

yeah, if you create an account with a redhat.com address it gives you the corp plan...

we do but it mainly is accessible for sysadmin-mainers

it should not need to be owner for that? just a member?

yeah, exactly, it needed for creating a tickets in new `compose-tracker-issues` repo, basically migration of failed composes

we short in time and Kevin wanted to discuss something on openfloor

we can return to that later after meet

Yup, time check. I can host next week. What did you have in mind Kevin?

it should not need to be an owner. owners can delete/create new repos. It should not have that priv. ;)

I actually had two things now that I think about it. ;)

1. jnsamyak (at DevConf.IN 12-16 Feb) any problems with adding suprakeen as a releng member? he works on the osbuild stuff and has worked on a lot of the definitions... I see you added Neal already...

it sould be added to the member list of releng space is it?

Anton Medvedev: yeah, exactly. just a member.

2. https://forge.fedoraproject.org/releng/tickets/issues/13223 we only want 'x86_64 aarch64 ppc64le' for noarch_arches on build tags. We should adjust the koji branching script to do this right. (another followup from branching I guess)

yeah +1

he has been working with me also, while branching sometimes telling if there is a requirement that was missing that they need

I can add them or do you want to?

either way, just wanted to bring it up.

sold

3. I think this one can be closed: https://forge.fedoraproject.org/releng/tickets/issues/12629

we now have new issue about pkgs with 0 commits

is suprakeen the fas id too or is it just matrix one?

so that one seems oudated

it's supakeen

yeah, sorry. need more coffee

and added; you can be the wizard for telling the news to them! :D

yeah I am just staring at my bed, after one week I'm home

after this I'm going to get a long sleep

did the email go out for that one?

not sure let me check

I think I was looking into it through a script, I can check again once before closing it out, sign it to me, and can put it in backlog

assign*