14:01:11 <elodilles> #startmeeting releaseteam 14:01:11 <opendevmeet> Meeting started Fri Sep 9 14:01:11 2022 UTC and is due to finish in 60 minutes. The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:11 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:11 <opendevmeet> The meeting name has been set to 'releaseteam' 14:01:20 <elodilles> Ping list: armstrong ttx hberaud diablo_rojo_phone 14:01:22 <hberaud> o/ 14:01:24 <ttx> o/ 14:01:29 <elodilles> #link https://etherpad.opendev.org/p/zed-relmgt-tracking 14:01:42 <elodilles> (sorry, i've lost my windows meanwhile :S) 14:01:59 <elodilles> (browser window :D) 14:02:27 <elodilles> we are waaay down @ L341 14:02:31 <elodilles> o/ 14:02:55 <elodilles> #topic Review task completion 14:03:10 <elodilles> 1st task: 'Process any remaining client library freeze exception. (all)' 14:03:29 <elodilles> we actually did not have exception, and still we had some :/ 14:03:40 <elodilles> due to the broken gates 14:03:55 <elodilles> as deliverables with broken gates probably need another release 14:04:15 <elodilles> and they are: 14:04:17 <ttx> yeah would be a good thing 14:04:21 <elodilles> python-adjutantclient (not released yet in zed!) 14:04:27 <elodilles> python-magnumclient 14:04:32 <elodilles> python-mistralclient 14:04:36 <elodilles> python-saharaclient 14:04:41 <elodilles> python-watcherclient (not released yet in zed!) 14:04:45 <elodilles> python-zaqarclient (not released yet in zed!) 14:05:04 <ttx> Ideally we'd branch on a working point 14:05:05 <elodilles> what I see is that python-magnumclient and python-saharaclient gates are unblocked now 14:05:14 <elodilles> ttx: yepp 14:05:27 <elodilles> so those looks promising 14:05:36 <elodilles> but still need releases 14:05:53 <elodilles> the rest are the interesting ones 14:05:57 <ttx> I don;t think we *have to* but that would be nice, if only so that we can merge the first stable/zed patches 14:06:04 <elodilles> so what should be the way forward with them? 14:06:58 <ttx> elodilles: I think we should look into the failure and see if we can fix it 14:07:13 <ttx> It's a bit late to remove it 14:07:43 <ttx> Maybe we should run those tests also ahead of the membership freeze 14:07:45 <elodilles> ttx: for us the minimum is that the packages can be built i guess 14:08:21 <elodilles> ttx: so, ok, let's try to fix them 14:08:23 <ttx> do you have links to those DNM patches? 14:08:31 <ttx> I'll have a quick look 14:08:38 <elodilles> https://review.opendev.org/q/topic:release-health-check+is:open 14:08:57 <ttx> ok I'll copy the links in the meeting notes and start looking 14:09:07 <elodilles> thanks! 14:09:21 <ttx> we can go back to it at end of meeting 14:09:24 <ttx> during open discussion 14:09:31 <elodilles> ttx: ack 14:09:36 <elodilles> let's continue then 14:09:40 <ttx> Also we should push a release request for the two that are fixed 14:09:54 <elodilles> ttx: i can take that action 14:09:59 <elodilles> will do it after the meeting 14:10:52 <elodilles> 2nd task was: ' Freeze all cycle-based library releases except for release-critical bugs. Independently-released libraries may still be released, but constraint or requirement changes will be held until after the freeze period. (elod)' 14:11:19 <elodilles> this is actually more like a reminder, not a task, if i remember correctly o:) 14:11:38 <ttx> yep 14:11:44 <elodilles> should have been 'all' :) 14:11:45 <elodilles> anyway 14:11:49 <ttx> it's about remembering to not process release requests all over 14:11:50 <elodilles> next task 14:12:19 <elodilles> 3rd task: 'Propose stable/zed branch creation for all client and non-client libraries that had not requested it at freeze time. (hberaud)' 14:12:30 <elodilles> patches were proposed: https://review.opendev.org/q/zed-stable-branches 14:13:00 <elodilles> most of them have been merged 14:13:30 <elodilles> some are without response -> i'll +W them after the meeting 14:13:44 <elodilles> except the ones from the 1st task 14:13:47 <ttx> ++ 14:14:26 <elodilles> 4th task: ' List cycle-with-intermediary deliverables that have not been refreshed in the last 2 months and send a separate email targeted to teams with such old deliverables to remind them to release (if needed) otherwise a probably outdated version will be used for the final release. (elod)' 14:14:38 <elodilles> mail was sent: https://lists.openstack.org/pipermail/openstack-discuss/2022-September/030384.html 14:15:01 <elodilles> unreleased deliverables were filtered as they got a mail last week ( https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030253.html ) 14:15:43 <elodilles> so this task should be covered too i think 14:15:58 <elodilles> as horizon team replied 14:16:26 <elodilles> maybe QA team needs to be pinged as they haven't responded yet 14:17:05 <elodilles> i'll do that 14:17:21 <elodilles> and this was the last task 14:17:42 <elodilles> #topic Assign R-3 tasks 14:18:06 <elodilles> please add your name for those you can cover 14:18:33 <elodilles> i mean... 14:18:39 <elodilles> i've added mine to all o:) 14:19:09 <elodilles> well, again, 14:19:29 <elodilles> i've added 'all' to the 'branching exception' task 14:20:01 <elodilles> and then only one big relevant task was, so that one took 14:20:21 <elodilles> #topic Review countdown email contents 14:20:34 <elodilles> #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:20:37 <elodilles> please review ^^^ 14:22:08 <hberaud> LGTM 14:22:22 <armstrong> +1 14:22:46 <elodilles> thanks! will send it after the meeting 14:22:58 <ttx> Fixed stable/Zed -> stable/zed 14:23:03 <ttx> lgtm now 14:23:12 <elodilles> ttx: thx! 14:23:29 <elodilles> #topic Open Discussion 14:23:44 <ttx> ok so one of the remaining ones had a patch posted (Adjutant) 14:23:44 <elodilles> any topic to raise? 14:23:54 <hberaud> nope 14:23:59 <ttx> I posted a patch for watcherclient since it seemed trivial 14:24:15 <ttx> The other two might need a slightly deeper investigation 14:24:19 <elodilles> ttx: cool \o/ 14:24:23 <ttx> Did those have a PTL candidate? 14:24:35 <ttx> zaqar and mistral 14:24:53 <elodilles> mistral, i'm not sure, 14:25:32 <ttx> https://governance.openstack.org/election/ 14:25:36 <hberaud> apparently not for watcher 14:25:49 <ttx> Zaqar has Hao Wang 14:26:05 <ttx> Mistral, no candidate 14:26:17 <ttx> So I'd reach out through personal email to Hao Wang 14:26:27 <hberaud> well watcher has chen ke 14:26:29 <ttx> so that he looks into the test fail and proposes a patch 14:26:37 <ttx> watcher I think I fixed it 14:26:45 <elodilles> ttx: ++ 14:26:46 <hberaud> ok 14:27:07 <ttx> I'll let one of you do the reachout as I won;t have much time to follow up next week 14:27:24 <elodilles> ttx: ++, i'll do that 14:28:05 <ttx> Re:mistral I might just update the python version and see if there is any remaining issue 14:28:22 <elodilles> ttx: ack, thanks! 14:28:33 <ttx> but I fear there is more to it 14:29:05 <elodilles> to tell you the truth i did not started to fix them because we discussed that project teams should do that o:) 14:29:22 <elodilles> but i can also have a look at them 14:29:26 <elodilles> and we will see 14:29:38 <ttx> yeah they should, and some did 14:30:07 <elodilles> ttx: yepp, fortunately sahara and magnum fixed their gates \o/ 14:30:32 <elodilles> (or at least unblocked) 14:32:13 <elodilles> if nothing more about this, then maybe worth to mention oslo.db 12.1.0 release 14:32:27 <elodilles> the visible things were fixed \o/ 14:32:45 <elodilles> and requirement constraint was bumped 14:32:53 <elodilles> thanks all who worked on it 14:33:20 <elodilles> though i heard rumors that some neutron stadium still seem to be impacted 14:33:25 <ttx> yes thanks for sfinucane for saving the day 14:33:45 <elodilles> yepp \o/ 14:34:38 <elodilles> so just wanted to warn you that unfortunately the issue is still might be around 14:35:44 <ttx> ok I updated the ACTION list for the broken zed gates 14:35:57 <elodilles> i'm planning to propose DNM patches for cycle-with-rc project next Friday to see gate health for them 14:36:45 <ttx> elodilles: maybe we should only do that for those who haven't been refreshed recently 14:37:43 <elodilles> ttx: yepp, you are right. I'll update the script with that, thanks! 14:38:27 <elodilles> ttx: plus thanks for the ACTION list 14:38:38 <elodilles> anything else to discuss? 14:38:54 <ttx> nothing from me 14:39:12 <ttx> gate health should probably be a topic for our ptg 14:39:27 <ttx> not sure DNM patches are a great way of monitoring it 14:39:33 <elodilles> ttx: definitely 14:39:48 <ttx> we could track when was the last commit for all things in the release for example 14:40:10 <elodilles> yepp, that's one thing 14:40:23 <ttx> a leat this time we spotted it earlier 14:40:25 <ttx> least* 14:40:25 <elodilles> though in that case we would miss last minute breaks 14:40:42 <ttx> sure but those breaks were probably there forever 14:40:46 <ttx> like the py36 ones 14:41:17 <ttx> maybe we should push a DNM patch at every milestone if there was no other commit 14:41:24 <elodilles> yepp, those projects that haven't merged any patch since 2021.... probably broken for a long time... 14:42:03 <elodilles> ttx: that's a good idea 14:43:37 <fungi> also good feedback for the tc 14:44:06 <elodilles> fungi: yepp, i did send that time to time :) 14:44:57 <elodilles> i've added the 'Gate Health checks' topic to 'Things to change' section (line 448) 14:45:40 <elodilles> let's collect ideas / topics / things there for the PTG 14:46:24 <elodilles> and we can move them to RelMgmt's PTG etherpad if those will be generated 14:47:08 <ttx> ++ 14:47:24 <ttx> That's all for me. I'm traveling next week so will have limited availability 14:47:39 <ttx> I'll in flight on a flight without wifi at meeting hour next week 14:47:46 <elodilles> ttx: ack, thanks for the heads up, safe travels for you! 14:48:31 <elodilles> okay, if nothing else, then we can close the meeting 14:48:52 <elodilles> thanks everyone for participating! o/ 14:49:00 <hberaud> elodilles: thanks 14:49:03 <elodilles> #endmeeting