<@amedvede:fedora.im>
16:01:29
!startmeeting RELENG (2025-12-08)
<@meetbot:fedora.im>
16:01:30
Meeting started at 2025-12-08 16:01:29 UTC
<@meetbot:fedora.im>
16:01:30
The Meeting name is 'RELENG (2025-12-08)'
<@amedvede:fedora.im>
16:01:36
!meetingname releng
<@meetbot:fedora.im>
16:01:36
The Meeting Name is now releng
<@amedvede:fedora.im>
16:01:42
!chair nirik jnsamyak patrikp amedvede
<@amedvede:fedora.im>
16:01:47
!info Meeting is 60 minutes MAX. At the end of 60, it STOPS.
<@amedvede:fedora.im>
16:01:51
!info Agenda is at https://hackmd.io/vm6biLBcTYKtkQUH5kQkmw.
<@amedvede:fedora.im>
16:02:10
Lets start with init
<@amedvede:fedora.im>
16:02:12
!topic Init process.
<@amedvede:fedora.im>
16:02:18
Do we have anything for the init? Any blockers/tasks/issues/requests/features that need releng intervention?
<@patrikp:matrix.org>
16:02:38
Hello.
<@jnsamyak:matrix.org>
16:03:18
Nothing - EOL is going to happen next week, adam said he sent out emails for this, if not I'll check those, and send one tomorrow
<@nirik:matrix.scrye.com>
16:03:34
morning
<@jnsamyak:matrix.org>
16:03:40
Migration is under progress - pungi-fedora is moved to new forge.
<@nirik:matrix.scrye.com>
16:03:54
I do not think he sent the announcement email... he only updated bugs
<@jnsamyak:matrix.org>
16:04:24
oh he said on discussion post that he took care of it
<@amedvede:fedora.im>
16:04:52
compose-tracker and failed-composes will be migrated soon too, I prepared everything, tomorrow will send announcement email
<@jnsamyak:matrix.org>
16:04:53
i might have missed or read it wrong, in that case, I'll send out the annoucement today for next week
<@amedvede:fedora.im>
16:05:38
there will be need to create few variables in ansible private repo
<@nirik:matrix.scrye.com>
16:06:02
I don't see the email announcement.
<@jnsamyak:matrix.org>
16:06:31
Please send out annoucement emails prior, we need to give community time to adjust those peices
<@jnsamyak:matrix.org>
16:06:48
for eol?
<@nirik:matrix.scrye.com>
16:07:26
yes, for f41 eol.
<@amedvede:fedora.im>
16:07:28
sure, I'll sent after the meeting then
<@jnsamyak:matrix.org>
16:08:48
I'll send those out today, iam reading the discussion post new comments, i see you are right, he update bzs one
<@jnsamyak:matrix.org>
16:09:03
you will have eol mail soon in your moderator list, post meeting
<@amedvede:fedora.im>
16:09:51
anything else for init?
<@nirik:matrix.scrye.com>
16:11:18
nothing here
<@amedvede:fedora.im>
16:11:43
okay, lets move on then
<@amedvede:fedora.im>
16:11:52
!topic Scheduled actions coming up in the next week.
<@amedvede:fedora.im>
16:11:57
!info Here we list/discuss anything about items that are due to be done in the next week.
<@amedvede:fedora.im>
16:12:01
!link https://fedorapeople.org/groups/schedule/f-43/f-43-releng-tasks.html
<@amedvede:fedora.im>
16:12:06
!link https://fedorapeople.org/groups/schedule/f-44/f-44-releng-tasks.html
<@amedvede:fedora.im>
16:12:22
as Samyak mentioned EOL for next week
<@amedvede:fedora.im>
16:13:21
I see also `Rawhide starts Fedora Linux 44 development` starting today in calendar
<@nirik:matrix.scrye.com>
16:13:47
huh, not sure what that one means
<@patrikp:matrix.org>
16:13:54
Retire packages with security issues Mon 2025-12-22
<@patrikp:matrix.org>
16:13:54
For the F44 schedule, does anyone have more information on this?
<@patrikp:matrix.org>
16:14:14
That's August 12th, i.e. after mass branching I suppose.
<@nirik:matrix.scrye.com>
16:14:31
Thats a long ago thing that fesco wanted to do... but we never implemented and indeed there's new discussion about what to do about it.
<@amedvede:fedora.im>
16:14:48
me either, but sounds cool
<@patrikp:matrix.org>
16:15:13
It was in August. 2025-08-12
<@amedvede:fedora.im>
16:15:45
oh, those dates are always messing my mind
<@amedvede:fedora.im>
16:16:16
okay, so move to next section?
<@patrikp:matrix.org>
16:17:09
So next planned thing is mass rebuild in early Jan, i.e. right after the holidays?
<@jnsamyak:matrix.org>
16:17:53
yeah
<@amedvede:fedora.im>
16:17:58
it seems like it
<@nirik:matrix.scrye.com>
16:17:58
yeah, and that seems really early
<@patrikp:matrix.org>
16:18:10
I was surprised as well.
<@nirik:matrix.scrye.com>
16:18:15
the last one was a week later
<@jnsamyak:matrix.org>
16:18:43
i have a ticket for it to delay
<@nirik:matrix.scrye.com>
16:18:49
the one before that was 2 weeks later.
<@jnsamyak:matrix.org>
16:18:56
but just fimishing eol email for review, and i can discuss this
<@nirik:matrix.scrye.com>
16:19:04
something possibly to take up with fesco...
<@jnsamyak:matrix.org>
16:19:13
exactly
<@patrikp:matrix.org>
16:19:33
I don't understand how the schedule works. It's generated automatically or created manually by someone? Where do the dates come from?
<@jnsamyak:matrix.org>
16:20:11
it just the timing with the dst change are so bad, I need to reschdule my mornings to night for fesco and releng weekly i think so i can cordinate stuff easily
<@patrikp:matrix.org>
16:21:13
For F46 mass rebuild is scheduled for Jan 20th.
<@nirik:matrix.scrye.com>
16:21:14
it's approved/acks by fesco, but generated by the program managers...
<@nirik:matrix.scrye.com>
16:21:48
it's approved/acks by fesco, but generated by the Fedora Operations Architect
<@amedvede:fedora.im>
16:24:01
so are we wanna to reschedule mass rebuild to later date?
<@nirik:matrix.scrye.com>
16:24:42
https://pagure.io/fedora-pgm/schedule
<@nirik:matrix.scrye.com>
16:25:02
we should ask about it, but we cannot just change it ourselves since it involves moving other things and such
<@jnsamyak:matrix.org>
16:25:22
ready for review: https://hackmd.io/@2se5GAvIQGSWX9IGCuz2Tw/eol41/edit
<@patrikp:matrix.org>
16:26:18
Looks good to me.
<@amedvede:fedora.im>
16:26:22
yeah, but I guess we can modify only 1 date if fesco will be okay with it without moving other stuff
<@nirik:matrix.scrye.com>
16:26:31
Id say "begin planning their upgrade" could be "should upgrade"
<@jnsamyak:matrix.org>
16:26:59
will do that change
<@nirik:matrix.scrye.com>
16:27:08
perhaps. But then there is less time for maintainers post mass rebuild to fix packages.
<@jnsamyak:matrix.org>
16:27:19
also i was talking about that there is an blocker from gcc toolchain people
<@jnsamyak:matrix.org>
16:27:22
for the rebuild
<@jnsamyak:matrix.org>
16:27:37
not that it was happening right after the holidays
<@nirik:matrix.scrye.com>
16:27:41
yeah, they wanted things later...
<@nirik:matrix.scrye.com>
16:27:55
but fesco wanted them eariler... so...
<@nirik:matrix.scrye.com>
16:27:57
¯\\\_(ツ)\_/¯
<@nirik:matrix.scrye.com>
16:28:33
anyhow, that f41 eol looks ok... I'm not sure I would mention the thread / confusion... but i guess it's fine...
<@jnsamyak:matrix.org>
16:29:44
changed, just wanted to put confusion to answer the forth coming questions that what why this was done earlier
<@jnsamyak:matrix.org>
16:29:54
but for announce list, should I remove it?
<@jnsamyak:matrix.org>
16:30:11
I know it goes to some magzine publicly?
<@nirik:matrix.scrye.com>
16:31:07
well, many users probibly don't care how the schedule is made or anything... they just want to know that f41 is going eol...
<@nirik:matrix.scrye.com>
16:31:19
but it could actually draw in some contributors too...
<@jnsamyak:matrix.org>
16:32:52
let me update it then
<@amedvede:fedora.im>
16:34:08
time for next topic?
<@amedvede:fedora.im>
16:34:33
okay I will move on, if anything comes back, we will return to the on open floor
<@amedvede:fedora.im>
16:34:39
!topic Tickets that need attention.
<@amedvede:fedora.im>
16:34:44
!info This is the time where you can bring up RelEng tickets for discussion, for example if there are blockers, etc.
<@amedvede:fedora.im>
16:34:49
!link https://forge.fedoraproject.org/releng/tickets/issues
<@amedvede:fedora.im>
16:36:19
It was cool previously when creation of ticket sent notification to releng channel
<@jnsamyak:matrix.org>
16:36:51
ok https://hackmd.io/s08LXaPdR2KiGlppnPsLcg
<@jnsamyak:matrix.org>
16:37:00
updated
<@amedvede:fedora.im>
16:37:10
I'm not sure how it worked, where the code of matrix bot can be found?
<@jnsamyak:matrix.org>
16:38:08
i think aurelien and michal would be good poc for that
<@amedvede:fedora.im>
16:38:53
also not huge problem but should we address new forge in documentation and variables as `forge` or `forgejo`
<@amedvede:fedora.im>
16:39:03
I'll ask them
<@james:fedora.im>
16:41:11
https://github.com/fedora-infra/maubot-pagure-notifications
<@james:fedora.im>
16:41:30
But AIUI, that'll go away with the move to forgejo
<@jnsamyak:matrix.org>
16:41:40
okay so the eol email is sent
<@james:fedora.im>
16:41:42
As forgejo will do it natively
<@amedvede:fedora.im>
16:42:02
good to hear, thanks for sharing
<@nirik:matrix.scrye.com>
16:42:40
forge has a dedciated bot I think, it's not using the maubot plugin.
<@nirik:matrix.scrye.com>
16:42:45
yeah,., that
<@amedvede:fedora.im>
16:43:13
so for now we will live without notifications until moment of move
<@nirik:matrix.scrye.com>
16:43:32
it can be enabled now. talk to ryan/file a ticket asking for it.
<@nirik:matrix.scrye.com>
16:43:45
if you look in the #fedora-forgejo:fedoraproject.org channel they are using I think...
<@amedvede:fedora.im>
16:44:33
okay, good stuff, let me put on paper to not forget
<@amedvede:fedora.im>
16:47:26
if you have interesting tickets to discuss shoot, while i'm choosing one
<@nirik:matrix.scrye.com>
16:48:33
Oh, I had a question...
<@jnsamyak:matrix.org>
16:48:40
we are almost on time btw, so if you want to do chair after one ticket that's fine too
<@jnsamyak:matrix.org>
16:48:44
shooot
<@nirik:matrix.scrye.com>
16:49:16
in the daily meeting we have in later hours we used to triage releng tickets along with infra ones... should we still do that? and if we just use the same labels we used to use or are different ones needed now?
<@nirik:matrix.scrye.com>
16:49:48
or do you all want to triage things another time? or ?
<@jnsamyak:matrix.org>
16:49:50
so the labels should be same, but with new scrum set
<@jnsamyak:matrix.org>
16:50:02
we need to add points to that
<@jnsamyak:matrix.org>
16:50:24
low -> 1
<@jnsamyak:matrix.org>
16:50:24
med -> 3, 5
<@jnsamyak:matrix.org>
16:50:24
high -> 13 or so
<@jnsamyak:matrix.org>
16:50:34
that's an addition
<@nirik:matrix.scrye.com>
16:51:00
so, we also need to set a point value? in addition to the low/med/high ?
<@jnsamyak:matrix.org>
16:51:17
we nneed point value for sure
<@amedvede:fedora.im>
16:51:23
maybe we can get rid of old ones like med high low and exchange it with low - 1 point
<@jnsamyak:matrix.org>
16:51:27
we can think of droping low/mwd/high
<@amedvede:fedora.im>
16:51:39
so community and we noth know what to expect
<@jnsamyak:matrix.org>
16:51:49
but want to keep those for community but i would get backlash for havng so many tags lol
<@amedvede:fedora.im>
16:51:49
so community and we both know what to expect
<@nirik:matrix.scrye.com>
16:51:52
I think ryan made some global labels... but I am also not sure how the points syncs/works.
<@jnsamyak:matrix.org>
16:52:14
wait let me tell you quickly
<@nirik:matrix.scrye.com>
16:52:39
the releng repo has a vast sea of tags. ;(
<@nirik:matrix.scrye.com>
16:52:49
sorry 'labels' now
<@amedvede:fedora.im>
16:52:53
https://docs.google.com/presentation/d/1nyJ8RgSvzlRrRWXpjjZgr-F_RIgNuVNc62ufUR2fIEE/edit?slide=id.p#slide=id.p
<@amedvede:fedora.im>
16:53:16
here is doc describing how we should mark those points now
<@jnsamyak:matrix.org>
16:53:56
so let's start by dropping med high low labels with points
<@jnsamyak:matrix.org>
16:54:06
for trouble and gain
<@nirik:matrix.scrye.com>
16:54:37
we should have something public about it... a google doc is a bad look for the community.
<@jnsamyak:matrix.org>
16:54:44
there are already self explanatory pointers for it
<@jnsamyak:matrix.org>
16:54:51
the labels are there
<@jnsamyak:matrix.org>
16:54:57
publicly defined
<@jnsamyak:matrix.org>
16:55:00
and written
<@jnsamyak:matrix.org>
16:55:05
https://forge.fedoraproject.org/releng/tickets/labels
<@nirik:matrix.scrye.com>
16:55:53
ok, thats better
<@jnsamyak:matrix.org>
16:56:24
I'm planningto refine the not used ones from the tracker
<@jnsamyak:matrix.org>
16:56:32
but when i get some free cyles
<@jnsamyak:matrix.org>
16:56:35
but when i get some free cylces
<@nirik:matrix.scrye.com>
16:56:57
ok, so, should we try and trigae these daily? or since none of you all are there, should we leave that for you to do sometime?
<@amedvede:fedora.im>
16:56:58
so now we should mark ticket with two lables at same time? like low-trouble and points 1 at the same time?
<@nirik:matrix.scrye.com>
16:57:24
I'd drop/not do the low/med/high anymore, just the points...
<@nirik:matrix.scrye.com>
16:58:09
or perhaps we should still do priority?
<@jnsamyak:matrix.org>
16:58:33
I say leave it, we can do these as part of sprint planning we have, but i dont think there is a need to have it triaged daily, but i like the PRIORITY ones to be there.
<@nirik:matrix.scrye.com>
16:58:35
ie, where possible we should try and use the org level labels that every project will have
<@jnsamyak:matrix.org>
16:58:37
exactly
<@jnsamyak:matrix.org>
16:58:47
yeah
<@nirik:matrix.scrye.com>
16:59:15
ok, but I warn you.... if you don't keep up on triage it can get bad/big backlog. ;(
<@nirik:matrix.scrye.com>
16:59:21
also we are over 100 tickets again there. ;(
<@patrikp:matrix.org>
16:59:54
They just don't stop coming.
<@jnsamyak:matrix.org>
17:00:04
yeah i was on pto for a WEEK and boom it was back to 100 I need some cycles to look at what's going on
<@nirik:matrix.scrye.com>
17:00:24
yeah, busy busy busy
<@jnsamyak:matrix.org>
17:00:26
also as much as i hated pagure, it became an eye comfort
<@jnsamyak:matrix.org>
17:00:32
new forge is i'm adjusting
<@amedvede:fedora.im>
17:00:42
ticket number reminds me my wight loss way xd
<@patrikp:matrix.org>
17:00:42
Same here.
<@jnsamyak:matrix.org>
17:00:44
but it's good just need to make it a habit
<@jnsamyak:matrix.org>
17:00:45
:P
<@patrikp:matrix.org>
17:00:58
It doesn't show when a ticket was last modified. :(
<@nirik:matrix.scrye.com>
17:01:09
yeah, I haven't really mentally moved to forge yet. I am sure I will after infra moves. ;)
<@nirik:matrix.scrye.com>
17:01:29
https://forge.fedoraproject.org/releng/tickets/issues?q=&type=all&sort=leastupdate&state=open&labels=&milestone=0&project=0&assignee=0&poster=0 ?
<@patrikp:matrix.org>
17:01:31
By the way, time check. I can chair next week.
<@amedvede:fedora.im>
17:01:49
okay, I'll put your name in md file
<@nirik:matrix.scrye.com>
17:01:50
sort -> least recently updated?
<@amedvede:fedora.im>
17:02:01
yeah, we over time
<@amedvede:fedora.im>
17:02:08
thanks for comming
<@patrikp:matrix.org>
17:02:12
Yes, but when you just take a look at the unsorted page I really liked it when the frontend showed "Modified 10 hours ago"
<@amedvede:fedora.im>
17:02:25
!topic Choose next chair.
<@amedvede:fedora.im>
17:02:44
!info Next chair December 15th: Patrik
<@nirik:matrix.scrye.com>
17:02:55
ah, right... we could ask for it upstream
<@jnsamyak:matrix.org>
17:03:15
lots of things to doo
<@amedvede:fedora.im>
17:03:20
!info Thank you all for coming!
<@jnsamyak:matrix.org>
17:03:33
nirik: just a reminder for eol annoucement being in moderator list
<@amedvede:fedora.im>
17:03:39
next year promising to be busy one
<@amedvede:fedora.im>
17:03:47
!endmeeting