<@patrikp:matrix.org>
16:00:05
!startmeeting RELENG (2026-02-02)
<@meetbot:fedora.im>
16:00:08
Meeting started at 2026-02-02 16:00:05 UTC
<@meetbot:fedora.im>
16:00:08
The Meeting name is 'RELENG (2026-02-02)'
<@patrikp:matrix.org>
16:00:17
!meetingname releng
<@patrikp:matrix.org>
16:00:17
!info Meeting is 60 minutes MAX. At the end of 60, it STOPS.
<@patrikp:matrix.org>
16:00:17
!info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.
<@patrikp:matrix.org>
16:00:17
!chair nirik jnsamyak patrikp amedvede
<@meetbot:fedora.im>
16:00:19
The Meeting Name is now releng
<@patrikp:matrix.org>
16:00:41
Hello. 👋
<@nirik:matrix.scrye.com>
16:04:14
morning
<@patrikp:matrix.org>
16:04:59
Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?
<@patrikp:matrix.org>
16:04:59
!topic Init process.
<@patrikp:matrix.org>
16:06:07
I don't have anything for init.
<@nirik:matrix.scrye.com>
16:06:22
nothing off hand from me
<@patrikp:matrix.org>
16:06:33
!topic Scheduled actions coming up in the next week.
<@patrikp:matrix.org>
16:06:33
!info Here we list/discuss anything about items that are due to be done in the next week.
<@patrikp:matrix.org>
16:06:33
!link https://fedorapeople.org/groups/schedule/f-44/f-44-releng-tasks.html
<@patrikp:matrix.org>
16:06:46
So, the big one... Mass branching tomorrow and Samyak is at a wedding.
<@patrikp:matrix.org>
16:08:16
We have the preparatory PRs in place (feel free to double check if you find the time).
<@nirik:matrix.scrye.com>
16:08:44
yeah, I will try and give a review pass through them all later today.
<@patrikp:matrix.org>
16:09:09
How do we go about it tomorrow? Should I start it at the scheduled time? Announcement is sent. But I'm very hesitant to just start doing things without responsible adults around.
<@nirik:matrix.scrye.com>
16:09:51
Whats the scheduled time? I should be around my normal waking times. :)
<@nirik:matrix.scrye.com>
16:10:27
14utc?
<@patrikp:matrix.org>
16:11:09
1400 UTC
<@nirik:matrix.scrye.com>
16:11:25
Thats a bit early for me, but I'd say it should be ok to start slowly moving forward and I will be in when I get up
<@patrikp:matrix.org>
16:12:31
Would it be OK for me to actually hold off on doing things until you are behind a computer? The SOP seems WAY too straightforward considering how these mass branchings usually go, I fear some context or steps may be omitted.
<@patrikp:matrix.org>
16:12:40
Not going to lie, I'm shaking in my boots.
<@nirik:matrix.scrye.com>
16:13:40
sure, thats fine... I can let you know when I get in...
<@nirik:matrix.scrye.com>
16:14:00
don't worry... it's very complex, but we have tried to make sure everything is documented well the last few times...
<@nirik:matrix.scrye.com>
16:14:14
and if there's things that need cleaning up we can do that... it's not the end of the world.
<@nirik:matrix.scrye.com>
16:14:41
So, just go slowly and carefully and understand each step and we should be fine
<@patrikp:matrix.org>
16:15:11
I will do my best to update the SOP during/afterwards. Completely understandable that it's not perfect, it's a monumental task to document it from scratch.
<@nirik:matrix.scrye.com>
16:15:44
it's been getting closer each time... someday it will be 100% :)
<@jnsamyak:matrix.org>
16:15:58
but also in car
<@jnsamyak:matrix.org>
16:16:00
hehe
<@patrikp:matrix.org>
16:16:05
And then we switch to Konflux!
<@jnsamyak:matrix.org>
16:16:45
I gave my +1 on some, and some needs a little fixing
<@jnsamyak:matrix.org>
16:16:55
🙈
<@patrikp:matrix.org>
16:17:04
Yep, saw the feedback, I'll update them.
<@patrikp:matrix.org>
16:17:08
Thanks for the feedback.
<@nirik:matrix.scrye.com>
16:17:46
The first pass of f45 resigning finished finally. I am sure there's a few things that still need signing tho...
<@jnsamyak:matrix.org>
16:18:12
+1111, and every breaking thing has a upcoming fix
<@jnsamyak:matrix.org>
16:19:19
98 more
<@nirik:matrix.scrye.com>
16:19:32
not too bad.
<@patrikp:matrix.org>
16:19:41
Step 1 of the branching is turning off Koji builders. But in the Ansible section there's this note:
<@patrikp:matrix.org>
16:19:41
For context here's the SOP: https://docs.fedoraproject.org/en-US/infra/release_guide/sop_mass_branching/
<@patrikp:matrix.org>
16:19:41
<@patrikp:matrix.org>
16:19:41
`Avoid running the koji-hub.yaml playbook after turning off Koji builders to prevent overwriting manual changes.`
<@patrikp:matrix.org>
16:19:41
Does that mean this playbook has to be run only after Koji is re-enabled?
<@jnsamyak:matrix.org>
16:19:42
my internet is flaky I'll try to get those in, if not, I'll ping you
<@nirik:matrix.scrye.com>
16:19:46
If you all can get me the list I can fire it off... or leave it to you
<@jnsamyak:matrix.org>
16:20:44
I have a list in my user
<@jnsamyak:matrix.org>
16:20:57
but wait for me, I'm almost on it
<@patrikp:matrix.org>
16:20:58
And should we make a habit of using statusfpo when we do release related things (and thus add relevant sections to the SOP)?
<@nirik:matrix.scrye.com>
16:21:50
So, the script/commands that block external people from koji will be reverted if you run the koji playbook after that. So, yeah, you should wait until koji is ready to be re-opened to external people for that
<@nirik:matrix.scrye.com>
16:22:00
yes, I think updating status would be a good thing.
<@nirik:matrix.scrye.com>
16:22:47
I don't think it needs to be updated a bunch. Just a 'branching f44 is underway if you are a contributor, please wait until the process is done' and then clearing it once it's all done
<@nirik:matrix.scrye.com>
16:23:51
I'm happy to draft something/review.
<@patrikp:matrix.org>
16:24:06
In the Koji section (when creating release tags) there's this note:
<@patrikp:matrix.org>
16:24:06
`Build fedora-release and fedora-repos packages for Branched release before enabling the Rawhide gating.`
<@patrikp:matrix.org>
16:24:06
<@patrikp:matrix.org>
16:24:06
But then there are no further details or steps, it's just a note. What does this entail?
<@nirik:matrix.scrye.com>
16:26:28
I'm not sure there...
<@jnsamyak:matrix.org>
16:26:34
just do a fedpkg build for them nothing there
<@jnsamyak:matrix.org>
16:26:41
fanvy
<@jnsamyak:matrix.org>
16:27:08
so we need to do a build for branched (f44 in this case) before you run those playbooks
<@nirik:matrix.scrye.com>
16:27:14
There's often gating issues with these because gating is using the old repos/packages to test with or the like...
<@patrikp:matrix.org>
16:27:23
`Once you do the above, gating will be enabled on Rawhide updates under the new release number.`
<@patrikp:matrix.org>
16:27:23
Also there's this note that's in the ABOVE Ansible section, ABOVE the build packages note:
<@patrikp:matrix.org>
16:27:42
So if we followed the SOP in chronological order we'd run into trouble.
<@jnsamyak:matrix.org>
16:27:55
and one the playbooks are ran, they will enable rawhide gating, after which fedpkg build for both rawhide release
<@nirik:matrix.scrye.com>
16:28:08
Oh, I see "To create a rawhide release in bodhi, you need to run:" (but then it talks about making the _branched_ release
<@nirik:matrix.scrye.com>
16:28:34
oh, and we should drop all the container stuff. I thought I had a pr for that. ;(
<@nirik:matrix.scrye.com>
16:29:07
no F44C needs to be made
<@nirik:matrix.scrye.com>
16:29:42
anyhow, I will try and review all the pr's I can see today.
<@patrikp:matrix.org>
16:30:41
Could you please take a look at the SOP too so that if something seems obviously wrong you'll have a mental (or digital) note of it for tomorrow? If it's not too much to ask.
<@nirik:matrix.scrye.com>
16:31:25
definitely!
<@jnsamyak:matrix.org>
16:33:01
okay so signing is in progress
<@jnsamyak:matrix.org>
16:33:02
:D
<@patrikp:matrix.org>
16:33:33
Would mass branching be a good time to also update the attributes for the docs? Or at which point in the process would be a good time? Not sure it's a "step" we have anywhere.
<@patrikp:matrix.org>
16:33:33
https://forge.fedoraproject.org/infra/docs/raw/branch/main/modules/release_guide/pages/_partials/attributes.adoc
<@jnsamyak:matrix.org>
16:34:02
yes have a pr for it today
<@patrikp:matrix.org>
16:34:10
I think this is because the doc uses the {rawhide} attribute but we also have a {rawhide_next} one.
<@jnsamyak:matrix.org>
16:34:21
merge tomorrow 2 hour before or when you get in
<@jnsamyak:matrix.org>
16:34:24
it is alright
<@jnsamyak:matrix.org>
16:34:40
yeah update each one of those by one
<@patrikp:matrix.org>
16:35:18
Should I add a step into the SOP (I would propose one of the last steps) to update the attributes then?
<@patrikp:matrix.org>
16:35:36
If we do it before the branching process starts it'll mess with all of the rendered things in the SOP.
<@jnsamyak:matrix.org>
16:38:45
go ahead with it
<@jnsamyak:matrix.org>
16:39:04
yeah you can add this section on t-1 day of branching
<@patrikp:matrix.org>
16:40:30
So have it merged before and change the relevant sections of the SOP to {branched} and {rawhide} instead of {rawhide} and {rawhide_next}?
<@jnsamyak:matrix.org>
16:41:00
no have a prep pr for it before
<@jnsamyak:matrix.org>
16:41:08
and merge it on branching day
<@jnsamyak:matrix.org>
16:41:12
no extra work
<@patrikp:matrix.org>
16:41:21
Ah, gotcha, that makes sense. 👍️
<@patrikp:matrix.org>
16:44:42
What about the Ansible playbook you wrote Samyak? We'll use it tomorrow and it replaces the entire `dist-git` section in the SOP?
<@jnsamyak:matrix.org>
16:47:57
yeah I put a dry run option on it, and we can do a stg test I added that in a doc with the changes
<@jnsamyak:matrix.org>
16:48:33
I understand that, only motivation is support branching when i'm far :3
<@nirik:matrix.scrye.com>
16:48:49
ok, would be good to do a dry run today then and see how it does. ;)
<@jnsamyak:matrix.org>
16:49:04
thank you 🐥
<@nirik:matrix.scrye.com>
16:49:04
and can it do a non dry-run on staging?
<@jnsamyak:matrix.org>
16:49:14
yes
<@nirik:matrix.scrye.com>
16:49:37
that would be good to do today too... just to make sure it works as desired.
<@jnsamyak:matrix.org>
16:49:46
yeah
<@jnsamyak:matrix.org>
16:52:13
off topic: i never let anyone drive my car, but I hired a driver today so i can work but I guess I like this treatment too, should not get used to it tho lol
<@nirik:matrix.scrye.com>
16:52:23
so, can someone do those runs?
<@nirik:matrix.scrye.com>
16:52:28
nice. :)
<@jnsamyak:matrix.org>
16:54:04
I cant promise :/
<@jnsamyak:matrix.org>
16:54:23
atleast not today cantry tomorrow morning
<@jnsamyak:matrix.org>
16:54:35
(my indian morning)
<@nirik:matrix.scrye.com>
16:54:47
well, I can look when I review the script I suppose.
<@patrikp:matrix.org>
16:56:14
Time check.
<@patrikp:matrix.org>
16:56:33
!topic Choose next chair.
<@patrikp:matrix.org>
16:56:33
!info Next chair February 9th: ?
<@patrikp:matrix.org>
16:56:45
I can take next week too...
<@patrikp:matrix.org>
16:57:01
Unless someone else really wants it?
<@jnsamyak:matrix.org>
16:57:42
go ahead
<@jnsamyak:matrix.org>
16:57:55
thanks for running today as well sir!
<@patrikp:matrix.org>
16:57:58
!info Next chair February 9th: Patrik
<@jnsamyak:matrix.org>
16:58:03
good questions :D
<@patrikp:matrix.org>
16:59:39
Well, have a good rest of the day everyone.
<@nirik:matrix.scrye.com>
16:59:54
thanks patrikp!
<@patrikp:matrix.org>
16:59:59
!endmeeting
<@patrikp:matrix.org>
16:59:59
!info Thank you all for coming!