14:00:03 #startmeeting releaseteam 14:00:03 Meeting started Fri Sep 30 14:00:03 2022 UTC and is due to finish in 60 minutes. The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:03 The meeting name has been set to 'releaseteam' 14:00:05 slurp slurp 14:00:05 Ping list: armstrong ttx hberaud diablo_rojo_phone 14:00:12 o/ 14:00:18 #link https://etherpad.opendev.org/p/zed-relmgt-tracking 14:00:30 and we are almost at the bottom of the page 14:00:46 at line 429 14:00:48 o/ 14:01:32 let's start with the topics! 14:01:38 #topic Review task completion 14:01:57 1st task was: 14:02:08 #info Process any remaining stable branching exception. (all) 14:02:32 everything has branched 14:02:44 even requirements repository as well 14:02:52 so this is done 14:03:06 2nd task was: 14:03:15 #info follow up on oslo.db 12.1.0 related issues (elod) 14:03:40 this was on me, but mostly done by ttx , so thanks for that ttx o/ 14:03:50 ~o~ 14:04:25 #info watcher ec2-api magnum and zun released RCs that fixed their oslo.db 12.1.0 compatibility issues \o/ 14:04:33 I think we ahve all the known ones covered 14:04:57 i think yes 14:05:05 well for the others it's too late 14:05:53 yes. if any was not discovered then they need to fix it after the final release 14:06:23 3rd task: 14:06:33 #info remained from R-2: After all the projects enabled in devstack by default have been branched, we can engage with the QA, I18n and Requirements PTLs to finalize the stable branch setup. (elod) 14:06:44 QA team was pinged, they pushed the necessary patches: https://review.opendev.org/q/topic:qa-zed-release 14:07:07 there is no I18n team, as far as i know 14:07:29 so maybe we should remove this task from the process in the future 14:07:38 * subtask 14:07:38 theer is an I18n sig 14:07:53 ttx: oh, is there? 14:08:01 https://governance.openstack.org/sigs/ 14:08:21 ianychoi is the chair there 14:09:03 hmm, i did not find it in governance repository 14:09:14 only the I18n team in the legacy.yaml 14:09:46 okay, then I'll try to ping them after the meeting 14:10:49 anyway, to continue the subtasks: 14:10:54 requirements stable/zed branch cutting patch proposed: https://review.opendev.org/c/openstack/releases/+/858294 14:11:03 and also merged 14:11:22 now we need: "remind the requirements team to announce that the requirements freeze is lifted from master" 14:11:29 prometheanfire tonyb ^^^ 14:11:42 maybe this is the easiest way :) 14:12:03 elodilles: yeah it is no longer a project team, so it is listed in the governance-sigs repo instead 14:12:21 ttx: oh, ack, thanks 14:12:52 https://opendev.org/openstack/governance-sigs/src/commit/175c615f2df82d52c87e73c87a86a7f84f643394/sigs.yaml#L150 14:13:48 i see. somehow i missed this repo :S 14:14:42 anyway, that's it for this task 14:15:17 4th task: 14:15:25 #info 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 (elod) 14:15:45 for this one there is really no such SIG anymore o:) 14:16:00 nevertheless, i've proposed the necessary changes 14:16:08 just like in previous cycle 14:16:18 https://review.opendev.org/q/topic:www-zed-final 14:16:33 the last one needs to be merged at release day 14:17:10 the duties of the tech writing sig got split up between oslo and the tc 14:17:11 please review them after the meeting ^^^ 14:17:32 ack 14:17:36 fungi: yes, i remember that TC was informed 14:18:27 fungi: stephenfin was doing it (from oslo team) in xena, but he could not continue as far as i remember 14:18:50 right, but oslo adopted openstackdocstheme 14:19:02 so they're the approvers on any changes to that repo at least 14:19:29 fungi: hmmm, ok, then this needs another release process guideline update. i'll propose it 14:19:39 fungi: ack 14:19:51 the other former docs team repos are for the tc to deal with at this point though 14:20:51 ack 14:21:24 fortunately it seems that only those 3 patches are the ones that we should take care of 14:21:47 so not that big issue 14:22:31 specifically oslo has openstackdocstheme, openstack-doc-tools, os-api-ref 14:22:38 (of course, if i don't hide typos in them :S) 14:25:13 i think we can continue to the next task 14:25:37 #info follow up: Ensure that all projects that are publishing release notes have the notes link included in their deliverable file. (elod) 14:25:57 i've proposed another round of reno-links: https://review.opendev.org/c/openstack/releases/+/859690 14:27:13 we can merge this i think as new reno-links will appear in the coming weeks (as they usually does after the release in every cycle) 14:28:07 on the other hand, surprisingly good amount of reno-zed patches merged: https://review.opendev.org/q/topic:reno-zed 14:28:44 so at least we have less missing reno-links than usual (i think) 14:28:58 \o/ 14:29:16 okay, 5th task: 14:29:26 #info On the day before the deadline for final release candidates, propose last-minute RCs where needed (ttx) 14:29:44 ttx: thanks for doing this task! 14:30:07 See https://review.opendev.org/q/topic:last-minute-rcs for RC2s filed to pick up recent changes in stable/zed 14:30:20 (all merged \o/ 14:30:39 tacker has https://review.opendev.org/c/openstack/releases/+/859832 14:30:49 this one was merged, too ^^^ 14:30:57 ttx: anything to add? 14:31:17 nope, all set! 14:31:25 thanks again \o/ 14:31:32 quite happy of how it went 14:31:40 me too :) 14:31:55 so say we all! :) 14:32:51 OK, so, the last 2 tasks (countdown mail + propose-final-releases) tasks are 'after-meeting' tasks 14:32:58 so that was all for now \o/ 14:33:16 let's continue with the next topic 14:33:26 #topic Assign R+0 tasks 14:33:56 first of all we have "Special Review Guidelines!!!" 14:34:21 please follow that during the week 14:34:53 I feel like all of those are (all) 14:35:09 ttx: yepp, just wanted to say that :) 14:35:15 I plan to be around 14:35:29 same thing here 14:35:47 and definitely the same thing for me 14:36:15 as will i 14:36:35 thanks all of you in advance! o/ 14:36:59 okay, so all tasks are taken 14:37:00 though i have a dentist appointment at 15:00 utc, i expect release activities will have mostly wrapped up by then 14:37:33 fungi: oh, good luck with that :S 14:38:04 yepp, at that time hopefully just the mails need to be sent 14:38:28 #topic Review countdown email contents 14:38:43 #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:38:52 please review ^^^ 14:39:59 lgtm 14:41:38 thx, will send it after the meeting (+ will create the final release patch) 14:42:00 #topic Open Discussion 14:42:49 well, i forgot to add here in advance the PTG topic 14:43:21 the PTG page is generated already but I have'nt filled it with content yet: https://etherpad.opendev.org/p/oct2022-ptg-rel-mgt 14:43:37 what I'll do shortly 14:43:50 until that, feel free to add there topics 14:44:22 and of course we don't have yet any scheduled time slot 14:44:27 any preference for that? 14:45:13 hmm 14:45:42 I'd pick I'd pick a 13UTC slot 14:45:55 if it doesn't conflict with openstack-tc, openstack-security or diversity-wg i should be able to make it 14:46:50 If we pick 13utc or 14utc i can any day 14:47:23 what about having it on thursday or friday? 14:47:34 Or we could just take our usual meetign slot time... but then I can't overflow as I have a hard stop at 16utc 14:47:34 13 UTC is fine for me 14:47:52 Thursday is perfect 14:48:25 on Thursday (or Friday) there's TC sessions @ 15 UTC 14:48:30 maybe 14utc so that more people can join 14:48:48 fungi: is 14 UTC OK for you? 14:48:53 isn't that too early? 14:49:07 nah, that's plenty late 14:49:15 cool :) 14:49:33 i'm able to make 13:00 as well if it's preferable 14:49:56 but i don't have anything at either of those times on thursday or friday 14:50:53 there is an operator-hour placeholder at 14 UTC Thursday, is it something you want to participate? 14:51:24 though no teams added yet 14:51:35 I'm good 14:51:40 anyway, for me Thursday 13 or 14 UTC is OK 14:51:41 no, i probably won't be in many (if any) of the operator hours 14:52:14 ok, then Thursday 14 UTC is what we chose 14:52:24 sounds great, thanks 14:52:37 got to run 14:52:38 hberaud: is that OK for you as well? do you planning to be there? 14:52:45 yes 14:53:01 ttx: ack, thanks, see you o/ 14:53:07 hberaud: cool \o/ 14:53:18 if you book it into cactus-ThuB2 then you can use the same room the tc will be using (unless the plan is to use meetpad, in which case it won't matter) 14:53:46 #agreed relmgmt PTG session will be held @ Thursday 14 UTC 14:54:11 anything else to discuss? 14:54:35 (i'll add our time slot to the schedule page after the meeting) 14:56:29 nope 14:56:32 good. the silence signals me, that we don't have any other topic to discuss :) 14:56:49 thanks everyone for participating o/ 14:56:52 elodilles: thank you! 14:56:58 #endmeeting