<@patrikp:matrix.org>
16:02:53
!startmeeting RELENG (2024-10-21)
<@meetbot:fedora.im>
16:02:55
Meeting started at 2024-10-21 16:02:53 UTC
<@meetbot:fedora.im>
16:02:55
The Meeting name is 'RELENG (2024-10-21)'
<@patrikp:matrix.org>
16:03:03
!info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.
<@patrikp:matrix.org>
16:03:03
!chair nirik jnsamyak patrikp
<@patrikp:matrix.org>
16:03:03
!meetingname releng
<@patrikp:matrix.org>
16:03:03
!info Meeting is 60 minutes MAX. At the end of 60, it stops.
<@meetbot:fedora.im>
16:03:04
The Meeting Name is now releng
<@patrikp:matrix.org>
16:03:19
Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?
<@patrikp:matrix.org>
16:03:19
!topic Init process.
<@smilner:fedora.im>
16:03:28
!hi
<@zodbot:fedora.im>
16:03:30
None (smilner)
<@nirik:matrix.scrye.com>
16:05:34
morning
<@nirik:matrix.scrye.com>
16:06:59
We are trying to get things lined up to do a RC for f41
<@nirik:matrix.scrye.com>
16:07:12
We tried this weekend, but hit a compose issue (which should since be solved)
<@nirik:matrix.scrye.com>
16:07:32
The go / nogo is thursday, so we need a rc asap if there's enough time to test.
<@patrikp:matrix.org>
16:08:24
I'm following along in the blocker review channel. 👍️
<@nirik:matrix.scrye.com>
16:09:20
yeah... happening now in #blocker-review:fedoraproject.org
<@patrikp:matrix.org>
16:10:30
OK, if that's all for the init we can move on to scheduled actions...
<@patrikp:matrix.org>
16:10:38
!info Here we list/discuss anything about items that are due to be done in the next week.
<@patrikp:matrix.org>
16:10:38
!topic Scheduled actions coming up in the next week.
<@patrikp:matrix.org>
16:10:38
!link https://fedorapeople.org/groups/schedule/f-41/f-41-releng-tasks.html
<@nirik:matrix.scrye.com>
16:11:59
just the pushing stable updates, making rc's, then a bunch of stuff if we are 'go'
<@nirik:matrix.scrye.com>
16:13:39
Oh, I noticed we need to update the final rc doc
<@patrikp:matrix.org>
16:13:59
!info F41 Go / No-Go meeting is happening on Thursday, Oct 24th.
<@nirik:matrix.scrye.com>
16:14:25
https://docs.fedoraproject.org/en-US/infra/release_guide/beta_RC_compose/ was updated, but not https://docs.fedoraproject.org/en-US/infra/release_guide/final_RC_compose/
<@nirik:matrix.scrye.com>
16:17:55
I don't think there's anything else schedule wise.
<@patrikp:matrix.org>
16:18:34
Is that just the way the script is run? The argument without underscore.
<@patrikp:matrix.org>
16:18:40
I could take a look.
<@nirik:matrix.scrye.com>
16:23:52
I think we added the 'make a config with this python script' and the way you call the scripts are different.
<@nirik:matrix.scrye.com>
16:24:33
sudo ./release-candidate.sh 41 RC-1.2
<@nirik:matrix.scrye.com>
16:25:02
and... might be we should redirect the output out so we have that in case we need it? sudo ./release-candidate.sh 41 RC-1.2 >& 41-RC-1.1.out or something
<@nirik:matrix.scrye.com>
16:30:29
So, without jnsamyak around, should we close early? Or was there other items we wanted to discuss?
<@patrikp:matrix.org>
16:31:24
I wanted to ask about the DST changes. I don't think India has that at all. When would you prefer to have it? (e.g. overlap with other meetings...)
<@patrikp:matrix.org>
16:31:24
Either way works for me.
<@patrikp:matrix.org>
16:31:43
I would very much appreciate the government *not* changing my clock twice a year.
<@nirik:matrix.scrye.com>
16:33:17
Yeah, I hate DST, but... let me see. I have a meeting that ends 30min before right now.
<@nirik:matrix.scrye.com>
16:33:35
so, if we stay UTC time, I will have to move that meeting.
<@nirik:matrix.scrye.com>
16:33:48
If we move, I can keep it. I guess I can find out what we want to do with that other meeting first
<@patrikp:matrix.org>
16:34:29
Alright, so I'll keep it as is for now.
<@patrikp:matrix.org>
16:34:42
I think that's it then.
<@patrikp:matrix.org>
16:34:44
!endmeeting
<@patrikp:matrix.org>
16:34:44
!info Thank you all for coming!