15:00:42 <jednorozec> #startmeeting RELENG (2021-10-05)
15:00:42 <zodbot> Meeting started Tue Oct  5 15:00:42 2021 UTC.
15:00:42 <zodbot> This meeting is logged and archived in a public location.
15:00:42 <zodbot> The chair is jednorozec. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:00:42 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:42 <zodbot> The meeting name has been set to 'releng_(2021-10-05)'
15:00:43 <jednorozec> #meetingname releng
15:00:43 <zodbot> The meeting name has been set to 'releng'
15:00:43 <jednorozec> #chair nirik sharkcz pbrobinson pingou mboddu dustymabe ksinny jednorozec
15:00:43 <zodbot> Current chairs: dustymabe jednorozec ksinny mboddu nirik pbrobinson pingou sharkcz
15:00:49 <mboddu> Hello
15:00:49 <jednorozec> #topic init process
15:00:55 <nirik> morning
15:00:57 <jednorozec> Hellou
15:00:58 <mboddu> .hello mohanboddu
15:00:59 <zodbot> mboddu: Something blew up, please try again
15:01:02 <zodbot> mboddu: An error has occurred and has been logged. Please contact this bot's administrator for more information.
15:01:03 <pmoura> hello
15:07:44 <jednorozec> mboddu, thanks for sending out the final freeze notice
15:07:51 <mboddu> jednorozec: no problem
15:09:13 <jednorozec> #topic Fedora 35 final freeze
15:09:31 <jednorozec> we are in the final freeze now so only packages with FBR are included in new composes
15:10:04 * nirik will be sending the infra freeze notice out after meetings this morning
15:11:06 <jednorozec> release day is 2021-10-19
15:11:23 <jednorozec> freeze will be lifted after the release
15:11:40 <jednorozec> lets move on to the tickets
15:11:48 <jednorozec> .releng 10326
15:11:49 <zodbot> jednorozec: Issue #10326: turn off fm-releng bot notifications in #fedora-releng - releng - Pagure.io - https://pagure.io/releng/issue/10326
15:13:11 <jednorozec> So I was first absolutely against it, but today I have missed a important message on the channel because of the bot
15:13:41 <nirik> so, perhaps this could be replaced for interested folks with personal notification settings?
15:14:47 <nirik> ha, notifs still has rules for 'mash started'
15:15:27 <jednorozec> well, yes but I also think that messages from pungi.compose.status.change topic are relevant for releng channel
15:17:03 <mboddu> If its just aesthetics, I would prefer to leave them in there as they are super useful (for me at the least)
15:18:13 <jednorozec> mboddu, all of the messages?
15:20:03 <jednorozec> I personally dont need  topic pagure.pull-request.comment.added
15:20:14 <jednorozec> and by short look it makes a lot of buzz
15:20:29 <jednorozec> because we are working so hard :)
15:20:59 <nirik> pr's and commits for fedora-pungi are a lot of it.
15:21:04 <nirik> but also upstream pungi
15:21:47 <mboddu> Not all of them, definitely compose related things and maybe releng, pungi-fedora, comps and kickstarts repo
15:21:56 <nirik> and comps and kickstarts I guess
15:22:36 <jednorozec> I dont know about the repo messages
15:23:11 <jednorozec> I can see the reason for it, but on the other hand they make a lot of noise on the channel
15:23:45 <mboddu> I can be swayed for repo related things, but I definitely like the compose notifications
15:23:50 <nirik> one thought was to move them all to another bot channel and interested folks could join there.
15:24:04 <jednorozec> compose info is really important
15:24:26 <mboddu> All notifications in one channel or releng notifications to say #fedora-releng-notifications?
15:24:40 <nirik> I wish there was a way to only show failed composes
15:25:09 <nirik> mboddu: right... something like that...
15:25:16 <jednorozec> well if we move it all to different channel we did not solve anything
15:25:18 <mboddu> If all of them going to one channel, then its not super useful, unless the user can configure it per channel
15:25:23 <jednorozec> the noise is just in another channel
15:26:06 <jednorozec> I really like compose info in #releng and think it is important to have it there
15:26:10 <mboddu> jednorozec: Maybe move them to notification channel for now and then filter the unnecessary stuff
15:26:26 <nirik> jednorozec: sure we did. only those people who specifically want the noise join that channel.
15:27:00 <jednorozec> but I dont want noise and want notifications :)
15:27:09 <nirik> I think the thought is that bot noise drowns out users and actual discussion... but I am not sure how true that is for releng
15:28:31 <nirik> it's easy to get notifs to pm you those too.
15:28:31 <nirik> (at least I think so)
15:28:44 <jednorozec> it is not
15:28:50 <jednorozec> they are late or never
15:29:01 <nirik> some of the events are musing:
15:29:10 <nirik> amusing.
15:29:18 <nirik> "New errata about updates being mashed "
15:29:32 <jednorozec> heh
15:30:52 <nirik> yeah, true, it has been delayed/unreliable.
15:30:53 <mboddu> So, leave the compose related stuff in releng channel and push the other notifications to bot channel?
15:31:11 <jednorozec> +!
15:31:13 <jednorozec> +1
15:31:53 <mboddu> For now, we can start with this, and if people are not using the bot channel a lot and/or if people are complaining about the compose notifs in releng channel, we can revisit, wdayt?
15:32:01 <nirik> note that this will take a freeze break or waiting until after freeze
15:32:16 <nirik> so, perhaps we just punt and revisit after freeze?
15:33:18 <jednorozec> do we have after freeze tag?
15:33:28 <jednorozec> nope
15:33:45 <nirik> unfrozen? (at least in infra tracker)
15:35:05 <jednorozec> I made it with desc. revisit after the freeze
15:35:55 <nirik> and I see that notifs is stuck again. kicking it.
15:39:09 <jednorozec> commented and tagged
15:39:54 <jednorozec> #topic new Bodhi release in staging
15:40:20 <jednorozec> SO we have deployed latest and greatest bodhi in staging
15:40:40 <jednorozec> if you have time test it before we test it in production
15:40:40 <nirik> Might need another release to pick up all the fixes wanted tho?
15:40:51 <jednorozec> I dont think so
15:40:59 * jednorozec checks
15:41:27 <jednorozec> ok there are 2 new PR's
15:41:34 <nirik> I thought there was something that wasn't even implemented.
15:42:02 <jednorozec> Maybe but there was a list of tickets that was urgent
15:42:06 <jednorozec> most of it landed
15:42:09 <nirik> but I have not looked closely at all.
15:43:14 <jednorozec> But the point last week was mostly to actually lear how to do it
15:43:14 <mboddu> I need to check it as well, I wanted a fix for one of the signing issues
15:43:56 <jednorozec> And as always there are some steps in the release process that we can simplify
15:44:21 * nirik nods.
15:44:55 <nirik> is this needed in prod before final? updaing bodhi in freeze is a bit nerve wracking...
15:45:40 <jednorozec> I am not sure
15:45:44 <jednorozec> preferably not
15:47:16 <jednorozec> I dont have anything else for today
15:47:26 <nirik> yeah, if we can avoid it until after freeze that might be nice.
15:47:40 <mboddu> I have couple of stuff for open floor
15:47:47 <jednorozec> #topic Open Floor
15:47:54 <jednorozec> mboddu, stage is yours
15:47:56 * nirik had one FYI item
15:48:43 <mboddu> nirik: Go ahead
15:49:25 <nirik> just FYI, I updated libmodulemd on mbs* and bodhi-backend01 to allow for 'new format' modules to compose/work... shouldn't be any doom, but just wanted to note it.
15:50:03 <nirik> https://pagure.io/fedora-infrastructure/issue/10249 has details
15:50:20 <Southern_Gentlem> my question if people do not want the bot traffic why not in your client ignore the bot
15:50:47 <mboddu> We want some stuff that bot notifies
15:50:47 <Southern_Gentlem> that way for the people that want that traffic can see it
15:51:07 <mboddu> But some people dont want all of it and some people want some of it
15:52:53 <jednorozec> working notification service would solve a lot of this
15:52:58 <Southern_Gentlem> til someone has time to split the traffic to other bots leave it alone
15:53:06 <nirik> jednorozec: we can dream. :)
15:53:14 <mboddu> So, my updates
15:53:36 <mboddu> 1. I will be OOO for the remaining day
15:54:07 <mboddu> 2. RelEng freeze hasn't started at 14:00 UTC exactly, as there was an issue with the failed f35 compose
15:54:45 * nirik has another meeting in 5m
15:55:18 <mboddu> 3. With that, https://pagure.io/fedora-infra/ansible/pull-request/821 I will merge it now and will run the playbook in a min
15:55:38 <mboddu> 4. I will be on PTO next Monday and maybe Tuesday too
15:56:11 <jednorozec> mboddu, so what about this do we get it in before freeze? https://pagure.io/pungi-fedora/pull-request/1053
15:57:53 <mboddu> jednorozec: I will leave it as is, since the related build is not stable anyway, there might be a FE for it and then we can merge when the builds goes to stable
15:58:21 <nirik> +1
15:58:24 <jednorozec> ack
15:58:29 <nirik> we should land it, but only after thats stable
15:59:35 <jednorozec> thanks for the updates
16:00:36 <jednorozec> OS if that is all I will close this meeting
16:00:41 <jednorozec> *So
16:00:45 <nirik> thanks jednorozec
16:00:46 <mboddu> Nothing from me
16:00:49 <mboddu> Thanks jednorozec
16:00:52 <jednorozec> #endmeeting\