14:00:04 #startmeeting releaseteam 14:00:04 Meeting started Fri Nov 17 14:00:04 2023 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:04 The meeting name has been set to 'releaseteam' 14:00:10 Ping list: elod 14:00:28 we are now at line 73 https://etherpad.opendev.org/p/caracal-relmgt-tracking 14:01:16 o/ 14:02:16 let's go 14:02:25 #topic Review task completion 14:02:33 1) Ensure that all trailing projects have been branched for the previous series. 14:02:40 only remains trailing deliverables 14:02:50 so I think this task is ok 14:03:27 the task says we should propose branching patches 14:03:55 you sent an email last week about trailing deliverables and the deadline is in 1 month 14:03:58 though we have time until the trailing release 14:04:05 yepp 14:04:10 so this is why I didn't proposed patches 14:04:33 i don't remember whether they usually propose RC patches, or directly release 14:04:49 IIRC some propose RC 14:05:13 depending on the type of the deliverable 14:05:41 I don't think cinderlib will propose a RC 14:05:58 yepp, that is a cwi deliverable 14:06:04 yes 14:06:08 OK 14:06:15 let's just wait then :) 14:06:16 2) Propose autoreleases for cycle-with-intermediary libraries which did not release since the previous release. 14:06:31 https://review.opendev.org/q/topic:caracal-milestone-1 14:07:17 I don't think we should force a release for deliverables without PTL responses 14:07:18 ~half have merged already \o/ 14:07:58 hmm, don't we do that for Milestone-1 release? :-o 14:08:26 the process says: "On the Friday, merge patches that did not get any feedback from PTL or release liaison. Discuss standing -1s to see if they should be granted an exception and wait until next week." 14:08:31 IIRC usually M1 is more a conveniance milestone that a deadline milestone 14:08:42 https://releases.openstack.org/reference/process.html#milestone-1 14:09:02 ok 14:09:06 then... 14:09:12 yeah, it is true, that not mandatory, but where there are any change, maybe better to release 14:09:28 (* any functional change) 14:09:49 WFM 14:09:56 let me push the button 14:10:13 i've reviewed the patches without response and i think they are all OK to release 14:10:39 i did not find any patch which shouldn't be released (e.g. no functional changes) 14:10:52 ok 14:10:55 hberaud: +1 14:11:07 I'll +W them at the end of our meeting 14:11:25 ++ 14:11:33 thanks for proposing the patches o/ 14:11:33 3) To catch if there are acl issues in newly created repositories, run tools/aclissues.py to detect potential leftovers in Gerrit ACLs... 14:11:37 np 14:12:06 so, as with previous series, only ironic deliverables are listed by the acl tooling, I think we can safely ignore them as ironic because they are surely related to project-config changes similar to https://opendev.org/openstack/project-config/commit 14:12:16 thoughts? 14:12:34 that reminds me: 14:12:46 ttx has a patch that we should review: https://review.opendev.org/c/openstack/releases/+/899585 14:12:50 o:) 14:13:29 nevertheless, the task LGTM 14:13:31 indeed 14:13:55 ok, then next topic 14:14:01 #topic Agree on future meeting skips... 14:14:38 So, you propose to skip R-19, isn't? 14:15:18 wasn't me, but we can skip if there's nothing to discuss there :) 14:15:41 ttx: ^? 14:16:34 skips LGTM 14:17:12 ok to skip R-18,17,15,14 14:17:43 #topic Assign R-19 week tasks 14:18:15 well, we don't have any milestone-1 exception 14:18:25 so we are ready with the task o:) 14:18:31 anyone volunteer to chair the next meeting? 14:18:41 which one is the next then? 14:19:01 next week, as we have things to assign for next next weeks 14:19:12 IIUC 14:19:41 or we assign all the things now 14:19:54 and we also skip next week, as you want 14:19:59 let's do that! 14:21:30 OK, so which is the next meeting then? o:) 14:21:40 R-13 14:21:43 maybe we could have a short meeting @ R-18 14:21:46 Jan 1-5 14:21:51 uh, wrong timing 14:21:55 as you want 14:21:55 i can chair that 14:21:59 ok 14:22:04 Hi! 14:22:11 yo ttx 14:22:19 hi ttx o/ 14:22:34 so next meeting is in 2 weeks 14:22:36 Yeah I was proposing we skip some of the next meetings, but since then /someone/ did add tasks :) 14:22:38 dst changes claim another victim 14:22:49 lol 14:22:50 :D 14:23:09 thanks elodilles 14:23:15 np o/ 14:23:37 I think we are now good with our agenda 14:23:44 \o/ 14:24:17 OK with skippnig R-17 and R-15 14:24:42 +1 14:24:50 and R-19 14:25:05 +1 14:25:13 +1 14:25:34 and the next milestone is at R-12 14:25:39 also OK with R-14 14:25:41 ack 14:26:24 and the agenda seems sync with our process until M2 14:26:35 yeah i filled it out 14:26:44 after that point we have to fulfil the next weeks 14:26:45 (except trailing stuff that someone else added 14:27:08 ok 14:27:13 yeah it was missing, so i added it o:) 14:27:44 then I think we move on 14:27:46 Took over a task from you. If you want me to chair one of the upcoming meetings lmk 14:27:56 ack 14:28:06 s/can/ 14:28:32 #topic Review countdown email 14:28:44 https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:28:51 ttx: R-13 is free o:) 14:29:22 we should notice that no goal page is available (as with bobcat, antelope, etc) should we update the template of this email? 14:29:28 Looks good to me! 14:29:48 (to drop the goal section) 14:30:03 hberaud: yes, i remember that that changed some time ago 14:30:31 ok, then I'll propose a patch 14:30:41 +1 14:31:06 about the mail: i've fixed some nits & LGTM 14:31:44 thanks elodilles 14:31:55 np 14:32:50 sent 14:33:02 ~o~ 14:33:15 #topic Open Discussion 14:33:17 you presumably saw the notice from opendevstatus scroll by a few minutes ago, but just a reminder, gerrit is being upgraded shortly (15:30 utc), not that you generally approve release requests on fridays anyway 14:33:36 well 14:33:45 ok 14:33:50 Caracal-1 patches are on the queue to +W 14:34:01 so we should not +W them then 14:34:04 hberaud: ^^^ 14:34:19 ack 14:34:52 anything else? 14:34:56 i can do that after the gerrit upgrade, or on Monday then. which do we prefer? 14:35:15 as you want... 14:35:33 after the upgrade... 14:35:38 +1 14:35:51 thanks fungi for notifying us 14:36:04 yw 14:36:11 maybe 1 thing to mention: 14:36:27 about the new unmaintained process 14:36:46 i've volunteered to implement some automation for the transition 14:37:17 so such patches might arrive on your gerrit inbox o:) 14:37:27 let me know if you need some help 14:37:42 hberaud: ack, thanks in advance! 14:38:13 that's all from me for now 14:38:17 then I think we are done 14:38:23 ++ 14:38:27 thanks everyone 14:38:33 thanks hberaud o/ 14:38:34 #endmeeting