14:01:30 <elodilles> #startmeeting releaseteam
14:01:30 <opendevmeet> Meeting started Fri Jan 12 14:01:30 2024 UTC and is due to finish in 60 minutes.  The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:01:30 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:01:30 <opendevmeet> The meeting name has been set to 'releaseteam'
14:01:34 <hberaud> o/
14:01:37 <elodilles> Ping list: elod
14:01:45 <elodilles> o/
14:01:50 <elodilles> #link https://etherpad.opendev.org/p/caracal-relmgt-tracking
14:02:10 <elodilles> we are at line 188
14:02:36 <elodilles> ttx is on PTO, so we don't need to wait for him
14:03:05 <elodilles> #topic Review task completion
14:03:20 <elodilles> 1st task was: 'Follow up with Magnum team re: magnum-capi-helm-charts presence in Caracal release (elod)'
14:03:35 <elodilles> i've pinged the team on IRC and they discussed it on their weekly meeting and decided that the deliverable is not yet ready to be part of the release
14:03:50 <hberaud> ack
14:03:59 <hberaud> thx
14:04:00 <elodilles> maybe next cycle :)
14:04:03 <elodilles> we will see
14:04:17 <elodilles> 2nd task: 'Follow up with TC regarding tripleo "independent" deliverables and whether we should make them release-model:abandoned (fungi)'
14:04:32 <elodilles> i saw that fungi dropped this to TC meeting
14:04:43 <frickler> will be retired: https://review.opendev.org/c/openstack/governance/+/905145
14:04:48 <elodilles> and gmann proposed the patch:
14:04:52 <elodilles> #link https://review.opendev.org/c/openstack/releases/+/905147
14:05:07 <elodilles> frickler: ACK, thanks for the info
14:05:46 <elodilles> so as soon as the governance patch has merged, we can review & merge the patch in releases repo
14:06:07 <frickler> both DPLs seem to have acked the governance patch already, so next up will be emptying the repos
14:06:22 <elodilles> +1
14:06:28 <elodilles> sounds good
14:06:56 <elodilles> anything else to add?
14:07:51 <elodilles> OK, let's move on to the next task then
14:08:08 <elodilles> 3rd task was: 'Generate release requests for all cycle-with-intermediary libraries which had changes, but did not release since milestone-1. (elod)'
14:08:18 <elodilles> and i've generated the patches:
14:08:27 <elodilles> #link https://review.opendev.org/q/topic:caracal-milestone-2
14:08:50 <elodilles> half of them have merged already,
14:08:55 <hberaud> will +W the remaining patches after the meeting
14:09:11 <elodilles> hberaud: thanks in advance o/
14:09:15 <hberaud> np
14:09:42 <elodilles> for some the only somewhat relevant content is the python classifier update,
14:09:57 <hberaud> ok
14:10:04 <elodilles> (dropping py36, py37 and adding py310, py311)
14:10:16 <elodilles> but maybe it's better to release them anyway
14:10:21 <hberaud> np
14:10:44 <elodilles> and there are no exceptions left,
14:10:49 <hberaud> ack
14:11:21 <elodilles> teams who signalled that need an update, already updated their release patch and those are released already
14:11:29 <elodilles> so I think we are OK
14:11:45 <hberaud> ack
14:11:59 <elodilles> 4th task: 'To catch if there are acl issues in newly created repositories, run tools/aclissues.py for review. (elod)'
14:12:10 <elodilles> i've run the script,
14:12:15 <elodilles> no ACL issues found by script
14:12:21 <hberaud> nice
14:12:52 <elodilles> yepp, it was a bit suspicious now that the ironic repos ACLs didn't printed any warning ;)
14:13:04 <elodilles> thanks to the fix from the last cycle :)
14:13:11 <hberaud> \o/
14:13:13 <elodilles> the output was too empty :)
14:13:18 <hberaud> :)
14:13:39 <elodilles> OK, the tasks are covered, let's move on!
14:13:47 <elodilles> #topic Assign R-11 tasks
14:13:57 <elodilles> and this is done :)
14:14:10 <hberaud> thanks elodilles
14:14:16 <elodilles> np :)
14:14:30 <elodilles> as I said we don't have milestone-2 exceptions
14:15:01 <elodilles> (of course, if any team wants to add a late release, then we can process that...)
14:15:41 <hberaud> wfm
14:15:53 <elodilles> and i'll try to figure out a schedule, and ask for reviews 1st from the team then from PTLs on mailing list
14:16:07 <elodilles> * release cycle schedule
14:16:20 <elodilles> * for 2024.2 'D'
14:16:47 <hberaud> ack
14:17:02 <elodilles> (btw i will reach out to the Foundation whether they have the name already. I haven't seen a mail yet)
14:17:16 <frickler> voting ends today
14:17:25 <hberaud> I see the vote
14:17:42 <elodilles> ah, good, exciting :)
14:17:53 <elodilles> then we'll see :)
14:18:15 <elodilles> next topic then \o/
14:18:25 <elodilles> #topic Review countdown email
14:18:39 <elodilles> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
14:18:56 <elodilles> please review ^^^
14:19:39 <frickler> "$other-upcoming-event" is intentional?
14:20:04 <elodilles> nope, that was a leftover :)
14:20:09 <elodilles> removed
14:20:41 <elodilles> maybe it's too early anyway, to advertise any event
14:20:54 <hberaud> may we can also add the final release in the "upcoming deadlines"...
14:21:11 <elodilles> yepp, let's do that. adding it in a minute
14:21:22 <frickler> well one could mention that the date for the next ptg has been announced, but might be a bit offtopic
14:22:10 <hberaud> we could announce the PTG date in the coming weeks within the upcoming deadlines
14:22:24 <elodilles> frickler: we usually add the PTG there, so it's not off-topic at all
14:22:53 <elodilles> i thought maybe we are too early for that but you are right, let's add it
14:23:22 <elodilles> any of you has the exact date in front of you? o:)
14:23:29 <hberaud> nope
14:23:33 <frickler> 8.4. - 12.4.
14:24:00 <frickler> I remember because I was puzzled that the days are the same as for the current week
14:24:10 <elodilles> :)
14:24:11 <hberaud> virtual?
14:24:23 <frickler> but that's because we have Feb 29 this year
14:24:26 <frickler> virtual, yes
14:24:44 <elodilles> yepp, leap year
14:25:09 <hberaud> LGTM
14:25:20 <frickler> https://openinfra.dev/ptg/ if you want to link to it
14:25:21 <elodilles> what was it? it was said that we don't use the word 'virtual' anymore?
14:25:41 <hberaud> ok
14:25:44 <frickler> well the above site does use it
14:25:50 <elodilles> ahh, but there it is, so then let's use it :)
14:26:36 <frickler> cool, ack
14:26:50 <elodilles> something like that
14:26:58 <hberaud> LGTM
14:27:18 <elodilles> thanks i'll send it later today
14:27:26 <hberaud> thanks
14:27:26 <elodilles> last topic then:
14:27:35 <elodilles> #topic Open Discussion
14:27:44 <frickler> I have two questions
14:27:51 <elodilles> I have one topic after you :)
14:27:59 <elodilles> so, shoot :)
14:28:34 <frickler> a) the TC has marked four projects as inactive, iiuc that means they will not be part of the release, but they are still listed in deliverables. what action needs to be taken there?
14:29:02 <elodilles> frickler: oh, good topic!
14:29:25 <elodilles> if they are inactive then i guess we should not relese them, right?
14:29:37 <frickler> that's my understanding, yes
14:29:38 <hberaud> tag them abandoned? https://releases.openstack.org/reference/release_models.html#abandoned
14:29:44 <elodilles> which are the 4 projects?
14:30:03 <frickler> monasca, sahara, freezer, solum
14:30:14 <hberaud> and I think they will be ignored by our tooling
14:30:37 <frickler> governance/reference/emerging-technology-and-inactive-projects.rst
14:30:48 <elodilles> 'abandoned' are for cycle independent deliverables,
14:31:02 <frickler> I think we wanted to wait one cycle before actually retiring
14:31:03 <elodilles> so I think we have to remove them from deliverables/caracal/*
14:31:05 <hberaud> nope
14:31:15 <hberaud> I think they are for all deliverables
14:31:44 <hberaud> and as said in the doc they are ignored by the tooling at the next series creation
14:32:04 <elodilles> hmmm, cool
14:32:33 <hberaud> at least that's what I understand
14:32:33 <elodilles> OK, then patches needs to be created with the new flag as 'abandoned'
14:33:35 <hberaud> we can also remove files if no release exists for this series, that also work...
14:33:48 <elodilles> i'll propose then patches against the four projects' deliverables and ask you to review it
14:34:15 <elodilles> let me add a task for next week
14:34:36 <elodilles> to not to forget :)
14:35:30 <elodilles> there
14:35:35 <frickler> did a quick check and they all don't have releases this cycle yet
14:36:07 <elodilles> (i think one of our former task should have caught this, but probably they weren't marked inactive at that time?)
14:36:41 <elodilles> frickler: yepp, i'm pretty sure that not even any patches were merged in these repos recently...
14:36:48 <frickler> some were marked pretty recently
14:37:16 <frickler> but it would be good to know when your task was happening
14:37:28 <frickler> so we (TC) can notify you about late changes
14:37:35 <hberaud> https://github.com/openstack/releases/commit/50a23bb308fa57e45ccc3562290103d635e9409f
14:37:46 <hberaud> I think we can simply remove the file ^
14:37:55 <elodilles> before Milestone-2 we have tasks that checks things against governance repo
14:38:27 <hberaud> files
14:39:09 <elodilles> hberaud: ACK, i'll double-check before proposing the patches
14:39:14 <hberaud> ok
14:39:48 <frickler> ok, so that's covered then I guess
14:40:06 <frickler> b) might be actually the same as your topic: unmaintained tooling
14:40:06 <elodilles> frickler: i also waited for that to happen (to mark those deliverables as inactive/retired) as we struggle with them for some cycles already
14:40:50 <elodilles> frickler: yepp, i wanted to point to the same topic :)
14:40:55 <frickler> elodilles: yes, I know, and I'm glad that there was consensus now in the TC to take this step
14:41:17 <frickler> so I saw your patches, which need reviews, is that all that is missing currently?
14:41:54 <elodilles> frickler: yepp, life will be easier for us, and those who needs those repos anyhow, maybe now realise that something needs to be done
14:42:17 <elodilles> frickler: yepp, i think we can move on with the patches:
14:42:21 <elodilles> https://review.opendev.org/q/topic:%22relmgt-unmaintained-state%22
14:42:55 <hberaud> will review them after the meeting
14:43:18 <elodilles> maybe early next week we can merge them if you haven't find any issue or missing things
14:43:23 <frickler> ok, I already started looking, but I don't have too much experience with the tools
14:43:34 <elodilles> the last two patch will test the tagging and branch cutting
14:43:53 <frickler> maybe I should start from the end, then ;)
14:44:35 <elodilles> i meant the patches against release-test repo o:)
14:44:44 <elodilles> but that's easy to start with ;)
14:44:53 <frickler> anyway that answers what I had in mind, thx
14:45:29 <elodilles> if anything comes up during testing then we need to fix them anyway
14:45:54 <elodilles> so, fingers crossed
14:46:48 <elodilles> OK
14:46:59 <elodilles> looking forward to the tesing early next week :)
14:47:11 <elodilles> any other topic for today?
14:50:32 <elodilles> i hear silence :) so let's close the meeting then!
14:50:53 <elodilles> thanks hberaud frickler for participating o/
14:50:59 <elodilles> #endmeeting