13:00:18 <ttx> #startmeeting releaseteam
13:00:18 <opendevmeet> Meeting started Fri Jun 14 13:00:18 2024 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:00:18 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
13:00:18 <opendevmeet> The meeting name has been set to 'releaseteam'
13:00:32 <ttx> Ping list: release-team elod
13:00:55 <elodilles> o/
13:01:00 <ttx> Our agenda is at https://etherpad.opendev.org/p/dalmatian-relmgt-tracking down to line 160 or so
13:01:06 <frickler> \o
13:02:03 <ttx> #topic Review task completion
13:02:33 <ttx> *  Propose patches to release trailing deliverables (hberaud)
13:02:52 <ttx> Looks like this was done at https://review.opendev.org/q/topic:%22caracal-trailing-branch-cut%22
13:03:20 <frickler> those at least are all merged, yes
13:03:25 <hberaud> o/
13:03:34 <ttx> -     Review any remaining trailing project exceptions (all)
13:03:50 <frickler> osa is still struggling
13:04:04 <hberaud> we still have https://review.opendev.org/q/topic:%22caracal-trailing-final%22
13:04:19 <hberaud> at least https://review.opendev.org/c/openstack/releases/+/921502
13:04:56 <frickler> they need an rc3 for that, which needs https://review.opendev.org/c/openstack/openstack-ansible/+/921999 , which is failing CI
13:05:09 <hberaud> yes
13:05:22 <ttx> OK so we are still tracking that
13:05:28 <elodilles> +1
13:05:43 <frickler> but noonedeadpunk is aware and working 24x7 to get this resolved (or so I assume ;)
13:06:05 <hberaud> do we want to abandon 921502 while this rc3 is not there?
13:06:32 <frickler> could just be rebased then?
13:06:35 <hberaud> yes
13:06:45 <noonedeadpunk> Yeah, I'll rebase
13:06:54 <hberaud> noonedeadpunk: thanks
13:06:55 <elodilles> thx noonedeadpunk o/
13:07:00 <ttx> - Send the weekly email content ("Between Milestone-1 and Milestone-2") (ttx)
13:07:04 <ttx> This will be done in a minute
13:07:28 <ttx> #topic Assign R-14 week tasks
13:07:38 <ttx> They were all assigned, thank you all
13:07:56 <ttx> #topic Review countdown email for week R-15
13:08:08 <ttx> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails
13:09:12 <frickler> do we want to mention something about the late osa release there (not to shame, but maybe people are waiting and not aware of the issues)?
13:10:16 <frickler> or rather do a dedicated mail? maybe by noonedeadpunk?
13:11:09 <noonedeadpunk> well....
13:11:50 <elodilles> (hmmm, we don't have 'Membership-freeze' at the schedule, only its description)
13:11:51 <noonedeadpunk> this kinda makes sense from one perspective, but then also we're publishing RCs
13:12:50 <fungi> maybe an update from an osa representative that release candidates are available to try out but final release is delayed slightly?
13:12:58 <noonedeadpunk> Like - if we can have a exact date when release will take place - email would make more sense
13:13:05 <frickler> "will happen in next month" sounds wrong to me, is "will happen next month" better?
13:13:19 <frickler> (L4)
13:13:28 <noonedeadpunk> and also we're not going to accept any more changes to the final release
13:13:44 <ttx> frickler: fixed
13:14:06 <noonedeadpunk> But I can come up with the email
13:14:27 <ttx> yeah that would be great
13:14:29 <noonedeadpunk> Just right now we're waiting for SHA bump to pass CI which will be the last thing
13:14:34 <ttx> ant other comment on the email?
13:14:37 <ttx> any*
13:14:50 <elodilles> mail LGTM
13:15:28 <ttx> Alright will send shortly after meeting
13:15:31 <frickler> +1
13:15:48 <ttx> #topic Open Discussion
13:16:00 <ttx> Yielding the floor to frickler
13:16:24 <frickler> yes, I took the liberty to add some backlog stuff
13:16:36 <ttx> Now is a good time!
13:16:37 <frickler> 1)  EOLing of feature branches
13:16:50 <frickler> #link https://review.opendev.org/c/openstack/releases/+/917788
13:17:01 <frickler> #link https://review.opendev.org/c/openstack/releases/+/917781
13:17:33 <frickler> I -1d both, but no more feedback after that
13:17:44 <fungi> are those "failed" feature branches which were never merged back to master?
13:18:28 <frickler> would have to ask timburke about that
13:18:53 <frickler> but good point, maybe they can be deleted without tagging if they are actually obsolete
13:19:21 <frickler> and a branch from juno most likely would fit that
13:19:48 <frickler> I can followup with tim and then we can discuss this again another time if needed
13:20:32 <frickler> 2) zed-last tempest plugins
13:20:33 <fungi> yeah, the branch names for those features aren't familiar to me, but good hygiene for feature branches which got merged eventually would be to delete the branches once they're done
13:21:02 <frickler> I think we already decided to override the missing ptl-approvals, any volunteer to actually do that?
13:21:16 <ttx> Will do
13:21:19 <fungi> i think we maybe didn't delete feature branches originally because gerrit couldn't delegate branch deletion by pattern
13:21:31 <fungi> but now it can
13:22:10 <elodilles> i've started to reviewing them, but haven't finished with all the patches yet
13:22:15 <frickler> fungi: anyway, I would also volunteer to do the deletions if needed, tagging would be more work
13:23:10 <frickler> elodilles: ok, I can try to join in next week
13:23:20 <fungi> tagging a feature branch before deletion *might* make sense for features which got abandoned, but i'm skeptical. the changes are still in gerrit either way
13:24:09 <frickler> ack, would need to check for open changes and abandon those, though, good point
13:24:14 <frickler> 3) fix for aclissues.py
13:24:28 <frickler> #link https://review.opendev.org/c/openstack/releases/+/919928
13:24:36 <frickler> just needs another review I think
13:24:53 <ttx> yes please
13:25:13 <ttx> (I did push PTL+1 on every zed-last patch)
13:25:36 <frickler> ttx: thx
13:25:38 <ttx> Now updating inactivity scorecard
13:25:38 <frickler> 4) whitebox-tempest-plugin release + tag fixup
13:25:45 <frickler> https://review.opendev.org/c/openstack/releases/+/915751
13:26:05 <frickler> there was some discussion there about the multiple tags being added to the deliverables file
13:26:23 <frickler> but I think it should be fine as noted in the comment, so also only waiting for another review
13:27:01 <elodilles> are 0.0.1 and 0.0.2 existing tags?
13:27:05 <frickler> yes
13:27:24 <elodilles> OK, i guess then it would be OK.
13:27:47 <elodilles> i just wasn't sure whether our tooling could handle 3 releases on top of each other
13:28:03 <elodilles> but then it's technically 1 new tagging+release
13:28:09 <frickler> exactly
13:28:41 <frickler> I'd hope the validation script would complain otherwise
13:28:59 <elodilles> i hope the same :)
13:29:35 <frickler> and that's it from me, giving up the floor if someone else has a topic?
13:30:00 <elodilles> +2+W'd
13:30:19 <frickler> thx
13:31:34 <ttx> no other topic from me
13:31:40 <elodilles> neither from me
13:31:53 <ttx> Alright then...
13:31:59 <ttx> #endmeeting