16:00:23 <jednorozec> #startmeeting RELENG (2023-08-15)
16:00:23 <zodbot> Meeting started Tue Aug 15 16:00:23 2023 UTC.
16:00:23 <zodbot> This meeting is logged and archived in a public location.
16:00:23 <zodbot> The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:00:23 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:23 <zodbot> The meeting name has been set to 'releng_(2023-08-15)'
16:00:23 <jednorozec> #meetingname releng
16:00:23 <zodbot> The meeting name has been set to 'releng'
16:00:23 <jednorozec> #chair nirik sharkcz pbrobinson phsmoura dustymabe jednorozec
16:00:23 <jednorozec> #topic init process
16:00:23 <zodbot> Current chairs: dustymabe jednorozec nirik pbrobinson phsmoura sharkcz
16:00:47 <nirik> morning
16:01:44 <patrikp> Good evening.
16:02:15 * jednorozec is happy the evening is finally here\
16:02:26 <jednorozec> 33C in shade today
16:02:36 <nirik> another super hot day starting here
16:03:14 <jednorozec> is there any estimate for how long the heat dome will be around you?
16:03:46 <samyak> hello folks!!!! :3
16:03:53 <nirik> just the next few days... already today will be cooler...
16:04:06 <nirik> yesterday i think we hit 40C
16:04:39 <nirik> todays only supposed to get to 34ish?
16:05:01 <samyak> 35-40 is my normal I'm waiting to melt but o well it just bring sweat
16:05:44 * jednorozec is melting while reading 35 and normal in one sentence
16:05:48 <nirik> I don't know if I could take that all the time. ;)
16:06:59 <jednorozec> ok lets start with hte agenda
16:07:59 <jednorozec> #topic mass branching mayhem
16:08:17 * samyak hides
16:08:50 * jednorozec pulls samyak out of the hole by leg
16:08:52 <jednorozec> so
16:09:02 <jednorozec> we have collected some of what went wrong https://hackmd.io/@jednorozec/HkIy8Ebh2/edit
16:09:16 <nirik> I think things went better this time. ;)
16:09:24 <jednorozec> I do really thing most of that happened because we started late
16:09:27 <nirik> but we can still make it even better
16:09:35 <jednorozec> yeah it was better ;)
16:09:40 <nirik> yeah, that did not help at all
16:10:02 <jednorozec> so I do think we should pospone the whole day If it happens next time
16:10:09 <jednorozec> can we do that?
16:10:17 <nirik> yeah. +1
16:10:27 <samyak> +1 to that idea considering timezones management also
16:10:31 <jednorozec> if QA raises flag, we should start next day 10:30 UTC or simillar time
16:11:07 <jednorozec> because, anyhow qa ended up with compose the day after. If we start soon enough QA will have compose ready in NA time
16:11:23 <jednorozec> if everything works, as it usually does not :D
16:11:28 <nirik> for the doc, perhaps we can put a check nect to each thing, and address them one by one and check them off... ie, 'added to doc' or 'in checklist' or whatever
16:12:11 <jednorozec> yeah, I can do that. But those forgoten commits or branches actually are already in the docs
16:12:54 <nirik> It would help me to see a list and know what has merged,  etc
16:13:08 <jednorozec> most of what went wrong is, that is whay I think most of it is because of the time and the SOP was not formatted in a nice way
16:13:11 <jednorozec> sure
16:13:16 <nirik> also... perhaps some things could be done the day before....
16:13:27 <jednorozec> let me update it, btw there is also the checkbox that samyak is working on
16:13:35 <jednorozec> https://hackmd.io/nUcHYCxdQJmRdTj8jaEF0g
16:13:47 <nirik> I mean, if its on a new branch it should be fine to push it before we use it
16:14:00 <samyak> yep; issue is here: https://pagure.io/releng/issue/11607 in case folks want to check on
16:14:10 <jednorozec> sad thing is they were done day before, some of the PRs
16:14:17 <jednorozec> and that was also a bit of a problem
16:14:17 <nirik> another random idea: could we make a check script?
16:14:40 <jednorozec> so
16:15:11 <jednorozec> my idea is html_js dashboard that will use public api and ^^ checklist
16:15:19 <jednorozec> to show us what is the state
16:15:23 <jednorozec> and what we are missing
16:15:41 <nirik> sure. I don't think it needs to be fancy...
16:15:45 <jednorozec> nope
16:16:01 <jednorozec> but its the easiest way to just generate html and host it on fedorapeople
16:16:02 <samyak> one more thing I discussed this with jednorozec was: To open a tracker like we have for Mass Rebuild on releng and put up a checklist here which people can mark on and others/reviewers can also see the items for a double check
16:16:06 <nirik> theres so many moving parts. ;)
16:16:19 <nirik> +1
16:17:14 <samyak> > my idea is html_js dashboard that will use public api and ^^ checklist
16:17:14 <samyak> This sounds interesting, I can help and see what we can come up with
16:17:30 <jednorozec> well first things first
16:17:45 <jednorozec> update the docs and do fancy stuff later :)
16:17:50 <samyak> :P
16:18:32 <nirik> yes.
16:20:06 <jednorozec> anything else regarding branching?
16:20:43 <nirik> I also have on my list to do some docs for the signing part
16:21:07 <nirik> and I might see if we can get robosign to do it someday
16:21:36 <jednorozec> yeah if you can document the resigning that will be nice
16:21:52 <nirik> its super hacky. ;)
16:23:10 <jednorozec> ok
16:23:12 <jednorozec> moving on\
16:23:20 <jednorozec> #topic Tickets
16:24:21 <jednorozec> .releng 11596
16:24:22 <zodbot> jednorozec: Issue #11596: RFE: No koji builds during mass branching and updates-testing enablement - releng - Pagure.io - https://pagure.io/releng/issue/11596
16:24:44 <jednorozec> so are we going to do the same thing as this time? and close this or something else?
16:26:24 <nirik> I think we need to test in stg.... but I think we don't want serveroffline
16:26:33 <nirik> we just want lockdown
16:26:56 <jednorozec> well i didnt set it last time
16:27:01 <jednorozec> and it went offline anyways
16:27:27 <jednorozec> ok so leave that open and track it there
16:27:33 <jednorozec> I can play with the settings
16:27:51 <nirik> or... perhaps we need to talk to koji folks.
16:28:01 <nirik> ask for a mode like we want...
16:28:14 <nirik> where everything is viewable, but no new builds except by admins
16:29:14 <jednorozec> yeah, it maybe even have something like that?
16:29:34 <jednorozec> I dint look into it that much just at the options that are in our config
16:29:57 <nirik> I thought just lockdown would do it, but seems not.
16:30:40 <nirik> "      If Lockout is True, the server will report a ServerOffline fault for most non-admin requests."
16:30:52 <nirik> so, yeah, we want something new.
16:31:04 <jednorozec> yup
16:31:39 <jednorozec> so next steps are contacting koji people
16:31:50 <jednorozec> will leave that ticket opened
16:31:57 <jednorozec> .releng 11117
16:31:58 <zodbot> jednorozec: Issue #11117: Useless comps files in Modular repository - releng - Pagure.io - https://pagure.io/releng/issue/11117
16:32:05 <jednorozec> that seems like somethig we can close
16:32:46 <nirik> +1
16:34:49 <jednorozec> .releng 11431
16:34:50 <zodbot> jednorozec: Issue #11431: On new package repository creation add a gitignore with *.src.rpm - releng - Pagure.io - https://pagure.io/releng/issue/11431
16:35:15 <jednorozec> no answer from the requester for 3 months should we just close it?
16:35:30 <nirik> +1
16:37:58 <jednorozec> .releng 9266
16:37:59 <zodbot> jednorozec: Issue #9266: prune EOL content from OSTree repos - releng - Pagure.io - https://pagure.io/releng/issue/9266
16:38:08 <jednorozec> there is a prune script now is it?
16:39:34 <nirik> yeah, we should ask dusty if we can close this now. I think it's done.
16:40:37 <jednorozec> pinged
16:40:39 <jednorozec> we will see
16:41:14 <jednorozec> the dog is extra loud, I have to go and check brb
16:41:50 <nirik> hopefully it's nothing. ;)
16:46:52 <jednorozec> well neighbours dog got to our garden and was chasing ducks
16:47:09 <jednorozec> I dont know how she does that we have a new fence
16:47:15 <jednorozec> anyhow
16:47:50 <samyak> :3
16:48:31 <nirik> dog magic. ;)
16:48:44 <nirik> I had just a few items...
16:48:54 <jednorozec> go on
16:49:23 <nirik> First, I adjusted oz config on builders to use more cpus... looks like it shaves 15-20min off nightly composes. ;)
16:50:02 <nirik> Next, in one week is beta freeze start and bodhi enablement... are we all ready for that?
16:50:38 <jednorozec> so
16:50:42 <nirik> sorry, I mean "Bodhi updates-testing activation point"
16:50:45 <jednorozec> we did the last one based on the new docs
16:50:56 <jednorozec> and it worked out I think
16:51:13 <nirik> yeah, the 'frozen' state worked ok after a few issues were fixed.
16:51:56 <jednorozec> so as with branching I would like to have the PR the day before event ready for review
16:52:27 <jednorozec> bodhi activation is simpler but there is enough space for mistakes
16:52:29 <nirik> I'd be happy to have it later this week if possible. ;) I don't think there's too much to this tho
16:52:38 <jednorozec> nope
16:52:54 <nirik> and perhaps we should do a ticket to track/coordinate?
16:53:50 <nirik> https://docs.fedoraproject.org/en-US/infra/release_guide/sop_bodhi_activation/
16:53:56 <nirik> we can nuke the 'modular' part. ;)
16:53:57 <jednorozec> https://docs.fedoraproject.org/en-US/infra/release_guide/beta_freeze/
16:54:12 <jednorozec> oh I thought we already did patrikp was working on that
16:54:45 <jednorozec> ok there is PR but it was not updated for some time
16:54:47 <nirik> might not be merged yet
16:54:52 <patrikp> Yeah, I still have an open PR.
16:55:19 <jednorozec> can you remove all references on modularity?
16:55:25 <jednorozec> the PR only removes one page
16:55:30 <patrikp> Yes.
16:55:41 <nirik> +1
16:56:20 <nirik> last thing I had was if we could do the bugzilla move from rawhide->39 thing... https://docs.fedoraproject.org/en-US/program_management/pgm_guide/sop/branch/
16:56:30 <jednorozec> do we really need tracking ticket for the bodhi activation?
16:56:42 <jednorozec> it really should be just few operations and one PR for ansible
16:56:44 <nirik> naw... just a thought. we don't have to
16:57:00 <jednorozec> nirik, yes i got through the docs
16:57:19 <jednorozec> samyak, is on PTO utill tmrw so my plan is to go through it with guys tmrw
16:57:37 <jednorozec> there si some interesting stuff about how things are tracked in BZ
16:57:47 <nirik> sounds good. just wanted to make sure it got handled. You will need to add a date constraint to it...
16:57:58 <jednorozec> yeah
16:58:05 <nirik> and IMHO, do the moves as releng user instead of personal, but I guess thats up to you
16:58:47 <nirik> and perhaps we could switch to using the bugzilla cli for this (seems easier than web interface to me, but I guess thats up to whoever gets to do it next time)
16:58:49 <jednorozec> ohh I was going to use releng
16:59:02 <jednorozec> I dont really want that many notifications in my inbox
16:59:04 <jednorozec> ever again
16:59:12 <samyak> hhahaha
16:59:18 * jednorozec branched scls back in the days with his email
16:59:26 <jednorozec> bad idea
16:59:39 <nirik> I long ago unset the 'cc me on bugs when I change them' thing
16:59:41 <samyak> nirik saved me last time when i was doing something like that on bz
16:59:53 <samyak> oh no rip to inbox
17:00:22 <jednorozec> well you cant really do that as rhel package maintainer nirik
17:00:26 <nirik> yeah, you also get the fun 'hey you changed this bug 10 years ago, you must know this obscure thing about that package right?'
17:00:50 <jednorozec> ohhh i had the *luck* to maintain nodejs
17:01:02 <nirik> sure you can. by default it adds you to cc if you add a comment or change a bug, but you can set it so you have to manually check the box to do that.
17:01:41 <jednorozec> and that was how I lost half of the notifications when started with scls :D
17:01:44 <nirik> anyhow, just wanted to make sure it was all handled.
17:01:48 <jednorozec> sure
17:01:52 <nirik> thats all I had
17:02:03 <jednorozec> and we are over the time
17:02:07 <jednorozec> thank you all
17:02:12 <jednorozec> #endmeeting