14:01:08 #startmeeting releaseteam 14:01:08 Meeting started Fri Mar 25 14:01:08 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:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:08 The meeting name has been set to 'releaseteam' 14:01:15 Ping list: hberaud ttx armstrong damani 14:01:17 o/ 14:01:25 #link https://etherpad.opendev.org/p/yoga-relmgt-tracking 14:01:56 we are at line 392 waaaay down 14:02:03 o/ 14:02:06 o/ 14:02:26 hi 14:02:43 o/ 14:05:09 good to see so many of you :) let's start with the 1st topic 14:05:21 #topic Review task completion 14:05:33 1st task was: 14:05:37 'Process any remaining stable branching exception.' 14:05:58 done 14:06:07 empty list 14:06:11 \o/ 14:06:14 thanks hberaud 14:06:20 next task: 14:06:33 'Process any remaining tempest patches exception.' 14:06:50 https://review.opendev.org/q/topic:yoga-tp-latest+status:open 14:07:05 we have here two tempest plugin still open 14:07:06 so only monasca remains here... 14:07:26 the ironic part only needs another +2 14:07:34 hberaud: yes, the other needs a 2nd +2+W only :] 14:07:54 However I didn't get replies from the monasca team... 14:07:58 hopefully monasca will be PTL-approved soon as well 14:08:30 Also I didn't find the patches that they spoke about in their comments 14:08:39 should we set a deadline there? 14:08:49 I'd say yes 14:09:12 hmm how about we approve it now 14:09:20 +1 14:09:23 * ttx checks 14:09:36 o/ 14:09:52 I think we enough waited 14:09:58 armstrong: o/ 14:10:16 the hash is still the tip of the branch 14:10:24 yeah they can do a 2.5.0 at the last minute but we need one now 14:10:25 cool 14:10:36 so fire 14:10:39 just approved ironic 14:11:16 and +2ed monasca 14:12:22 and +2+W'd monasca 14:12:43 thanks 14:12:57 next task: 14:13:08 'Notify the documentation (Technical Writing SIG - https://wiki.openstack.org/wiki/Documentation) team that it should be safe to apply their process to create the new release series landing pages for docs.openstack.org.' 14:13:13 this was on me 14:13:35 unfortunately this was an issue last time as well 14:13:55 as there is no active member of the team anymore 14:14:10 as I tracked down TC took over the responsibility 14:14:46 stephenfin might be willing? 14:15:27 what i found is that these are the patches that we need: https://review.opendev.org/q/project:openstack/openstack-manuals+topic:yoga 14:16:22 anyway, i planned to propose these patches for zed today but ran out of time before the meeting :/ sorry :/ 14:16:30 i'll do that after the meeting 14:16:37 and ping the TC as well 14:17:34 fungi: i don't know whether stephenfin is around, besides he said last occasion that he stepped down from documentation SIG 14:17:38 i think it's fine as long as we have them before release day 14:17:49 ttx: ++ 14:18:09 yeah, he's still been pitching in here and there, i agree it's a long shot 14:18:53 reaching out to the tc about it is definitely the next step anwyay 14:18:57 anyway, it's on my TODO :) 14:19:09 fungi: ++ 14:19:53 ok, next task then: 14:20:07 'On the day before the deadline for final release candidates, propose last-minute RCs where needed.' 14:20:17 https://review.opendev.org/q/topic:yoga-final-rc 14:20:26 hberaud proposed the patches ^^^ 14:20:31 sahara is left 14:20:37 Martin Kopec proposed openstack/releases master: Release os-testr 3.0.0 https://review.opendev.org/c/openstack/releases/+/835197 14:20:50 those without response should be abandoned 14:21:09 then we can abandon 14:21:10 I was actually wondering 14:21:18 02235e6c Update TOX_CONSTRAINTS_FILE for stable/yoga 14:21:21 9bbf339e Update .gitreview for stable/yoga 14:21:27 Those look like things we kinda need to have 14:21:28 and after the final release, a stable release can be made if necessary 14:21:34 but I'm surprised they did not make it to rc1 14:22:04 ttx: why we need them? 14:22:09 ttx: .gitreview and TOX_CONSTRAINTS are generated after the stable/yoga cut, 14:22:17 ah 14:22:18 I think those can be ignored 14:22:24 which is usually together with RC1 14:22:32 I selected sahara because a fix was landed 14:22:34 ha right 14:22:43 ok then abandon agree 14:22:47 but I ingored all the other deliverables with just this kind of patch 14:23:02 Merged openstack/releases master: Release ironic-tempest-plugin for Yoga https://review.opendev.org/c/openstack/releases/+/833576 14:23:05 Merged openstack/releases master: Release monasca-tempest-plugin for Yoga https://review.opendev.org/c/openstack/releases/+/833585 14:23:07 WFM 14:24:09 I remember that some projects had problems when these patches were not released, but to tell the truth these are the patches that quite many projects don't release at all after their final release is out 14:24:52 yes this can raise issue on the long time 14:25:08 so as hberaud says: we have multiple deliverables that have only this changes after RC1 and usually there weren't RC2 for them in the past 14:25:12 afaik :] 14:25:35 anyway, for now I think it's OK to abandon it 14:25:41 yes 14:25:51 +1 14:25:55 and sahara can decide to do stable release after March 30th 14:26:25 yes 14:27:06 done 14:27:13 i've abandoned it 14:27:53 so this task is also done \o/ 14:28:39 the next tasks are the countdown email review and... 14:28:43 ... After the email is sent, use propose-final-releases to tag the existing most recent release candidates as the final release for projects using the cycle-with-rc model 14:28:56 so I'll do that after the meeting :) 14:29:05 yeah those are Friday tasks :) 14:29:29 any comment questions for the completed tasks? 14:29:38 ttx: exactly :] 14:30:15 if no, then let's continue with the next topic: 14:30:27 #topic Assign R+0 week tasks 14:30:36 I'd say it's an "all" task list 14:30:39 this is an exciting one :) 14:30:42 with elodilles in the driver seat 14:30:55 I just separated review guidelines from tasks 14:30:56 ttx: ack 14:31:30 yepp, please stick to the guidlines for the next week :) 14:31:32 hberaud: you won;t be around right 14:31:40 good question 14:31:46 I'm not yet fully sure 14:31:55 OK I'll be around in support 14:31:56 I prefered to say that I'll be away 14:32:07 but maybe I'll be there too 14:32:15 I'll confirm monday 14:32:24 Might have a few hour-long breaks as I navigate other things, but fully available in the morning 14:32:32 hberaud: ack 14:32:40 i plan to be on hand for the release activities in case anything infrastructure-related comes up, though i have an appointment to get to afterward and will likely disappear around 15:30 utc 14:32:57 fungi: how early can we start? 14:33:05 fungi: thanks in advance 14:33:25 the critical is I'd say Wednesday and release timing :) 14:33:53 i can start as early as folks want 14:34:00 Trying to remember when the approval button needs to be pressed, IIRC it was around 12UTC 14:34:08 or 11:30UTC 14:34:29 i'll be awake by then for sure 14:34:45 so that it's fully done long before 15UTC 14:35:09 yeah, everything should be started well before 15UTC as I remember 14:35:14 OK let's plan to all be around at 1130UTC for the go/nogo 14:35:45 elodilles: that's 13:30 CEST with the time change next week 14:36:07 sounds good to me 14:36:20 ttx: yes-yes, DST is in the way as well :) 14:37:11 I'll be around all day so that shouldn't be a problem :) 14:37:38 hberaud: if you have any interesting thing in your mind that is good to remember regarding the release then please ping me with it :) 14:38:02 ack 14:38:08 Just confirmed that 15UTC is good 14:38:17 ttx: ack, thanks! 14:38:26 normally every useful info are in our process 14:38:39 hberaud: that's true :) 14:40:30 good, so everything is agreed then 14:40:36 ++ 14:40:37 anything else to mention? 14:40:43 nope 14:41:09 then let's move on to the next topic 14:41:16 #topic Review countdown email contents 14:41:24 #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:41:33 please review ^^^^ 14:42:10 in the template there was 'we would appreciate having an ack from each team before we 14:42:15 approve it on the 16th' 14:42:25 i guess that should be 30th 14:42:27 hmmm 14:42:31 or maybe 29th? 14:43:06 30th 14:43:13 we approve it on the 30th 14:43:34 ok, then it's good as it is \o/ 14:45:09 all good 14:45:13 LGTM 14:45:15 Did a few changes 14:45:26 (like new URL for PTGbot) 14:45:27 ttx: saw that, thanks! 14:45:55 OK 14:46:01 then last topic: 14:46:19 #topic Open Discussion 14:46:35 I was wondering if we needed a meeting next week 14:46:47 We could do the release postmortem at PTG 14:46:52 +1 14:46:58 and not sure we need to prep for PTG that much 14:47:08 ttx: sounds good to me 14:47:19 btw, PTG etherpad is there: 14:47:23 #link https://etherpad.opendev.org/p/april2022-ptg-rel-mgt 14:47:33 Cool will copy topics over 14:47:34 I only added the template yet 14:47:43 ttx: cool, thanks! 14:47:54 i saw that you started to collect things in the tracking page 14:49:15 feel free to add there topics if you have one 14:49:36 anything else that we forgot? 14:50:42 or any other topic? :) 14:51:27 nothing here 14:52:20 nope 14:52:23 i got nuthin' 14:52:24 prometheanfire: thanks for the requirements freeze lift mail! 14:52:28 #link http://lists.openstack.org/pipermail/openstack-discuss/2022-March/027834.html 14:52:31 \o/ 14:53:26 good. if nothing left for today, then let's close the meeting! 14:53:42 thanks everyone for the help & participation! 14:54:05 #endmeeting