fedora_infrastructure_ops_daily_standup_meeting
LOGS
18:00:03 <nirik> #startmeeting Fedora Infrastructure Ops Daily Standup Meeting
18:00:03 <zodbot> Meeting started Tue Oct 26 18:00:03 2021 UTC.
18:00:03 <zodbot> This meeting is logged and archived in a public location.
18:00:03 <zodbot> The chair is nirik. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
18:00:03 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:03 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:03 <nirik> #chair mboddu nirik pingou mobrien nb
18:00:03 <zodbot> Current chairs: mboddu mobrien nb nirik pingou
18:00:03 <nirik> #meetingname fedora_infrastructure_ops_daily_standup_meeting
18:00:03 <nirik> #info meeting is 30 minutes MAX. At the end of 30, its stops
18:00:03 <zodbot> The meeting name has been set to 'fedora_infrastructure_ops_daily_standup_meeting'
18:00:03 <nirik> #info agenda is at https://board.net/p/fedora-infra-daily
18:00:04 <nirik> #info reminder: speak up if you want to work on a ticket!
18:00:06 <nirik> #topic Tickets needing review
18:00:08 <nirik> #info https://pagure.io/fedora-infrastructure/issues?status=Open&priority=1
18:00:34 <nirik> just one infra one:
18:00:40 <nirik> .ticket 10295
18:00:41 <zodbot> nirik: Issue #10295: Please create a mailing list for sysadmin-openshift users - fedora-infrastructure - Pagure.io - https://pagure.io/fedora-infrastructure/issue/10295
18:00:52 <nirik> med/med/ops and I asked some questions on it already.
18:01:09 <mboddu> Here here
18:01:24 * nirik just modified it.
18:01:29 <nirik> hey mboddu any releng ones today?
18:01:40 <mboddu> Nope
18:02:13 <nirik> cool.
18:02:21 <nirik> #topic Upcoming work / planning
18:02:40 <nirik> I'm just treading water this week. ;) will try and file some more after freeze pr's
18:03:13 <nirik> and clear some more tickets.
18:03:33 <nirik> hopefully we have our final rc, but time will tell
18:04:12 <nirik> #topic Discussion / AOB
18:04:37 <mboddu> nirik: Any update on moving our s390x to z15?
18:04:39 <nirik> anything folks would like to discuss? any issues, pr's, good movies, ?
18:04:56 <nirik> mboddu: I have not seen any update on it. I can try asking around.
18:05:08 <mboddu> nirik: Thanks that would be helpful
18:05:21 <pmoura> I have one question
18:05:34 <pmoura> Im working on this one
18:05:47 <pmoura> .releng 10354
18:05:48 <zodbot> pmoura: Issue #10354: create epel-next-release-latest-8.noarch.rpm symlink - releng - Pagure.io - https://pagure.io/releng/issue/10354
18:06:12 <nb> .hi
18:06:13 <zodbot> nb: nb 'Nick Bebout' <nick@bebout.net>
18:06:17 <nirik> mboddu: asked internally, will let you know what I find out.
18:06:33 <mboddu> Thanks nirik
18:06:39 <eddiejennings> <-- nothing new to add.  Been quite busy at work and outside of work the last few days
18:06:53 * mboddu waits for pmoura questions
18:07:22 <pmoura> should i update the function update_epel_release_latest or write a new? I intend to update it and right now Im writing tests to be sure I wont break it
18:07:54 <mboddu> pmoura: Update the existing one
18:08:01 <pmoura> ok, thanks
18:08:27 <nirik> I'd say it's up to you... whatever makes the most sense. If it can re-use more from the old one I'd update that...
18:09:56 <pmoura> I think it can be reused I got that question just because the name of it, it says latest and the link symlink will be "next"
18:10:55 <nirik> ah yeah, confusing mix of terms there. :)
18:11:14 <mboddu> Yeah, but I think using the existing one makes more sense to me
18:12:32 * nirik nods
18:12:43 <nirik> ok, anything else from anyone, or shall we call it a standup? :)
18:13:20 <mboddu> Nothing from me
18:13:47 <nirik> ok, thanks for coming everyone!
18:13:50 <nirik> #endmeeting