14:00:13 #startmeeting releaseteam 14:00:13 Meeting started Thu Jul 27 14:00:13 2023 UTC and is due to finish in 60 minutes. The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:13 The meeting name has been set to 'releaseteam' 14:00:21 Ping list: elodilles armstrong 14:00:30 o/ 14:00:49 note that today we are holding the meeting instead of Friday due to i'll be absent tomorrow 14:00:52 o/ 14:01:03 #link https://etherpad.opendev.org/p/bobcat-relmgt-tracking 14:01:25 we are way down @ L286 14:02:06 ttx is OoO all week, so let's not wait for him 14:02:14 and let's start! 14:02:29 #topic eview R-12 and R-10 task completion 14:02:36 #undo 14:02:36 Removing item from minutes: #topic eview R-12 and R-10 task completion 14:02:40 #topic Review R-12 and R-10 task completion 14:03:11 1st task from R-12: 'Review any remaining milestone-2 exceptions (all)' 14:03:22 #link https://review.opendev.org/q/topic:bobcat-milestone-2+is:open+project:openstack/releases 14:03:47 list is empty so we've processed all patches! 14:03:49 no changes 14:03:55 \o/ 14:03:55 yepp 14:04:23 2nd task from R-12: 'Plan the next release cycle schedule (ttx)' 14:04:41 are you you are on the right week? 14:04:41 #link https://review.opendev.org/c/openstack/releases/+/888942 14:04:47 sure 14:05:31 we are at R-10 14:05:39 hberaud: R-12 week, did i miss something? 14:06:04 ah sorry I missed that we skipped this meeting 14:06:09 my bad 14:06:28 no problem :) we have to review R-12 AND R-10 as well :) 14:06:58 so ttx proposed 2024.1 Caracal release schedule (see above) 14:07:21 btw, we have the name of the new series \o/ 14:07:50 anyway, back to the topic 14:08:12 so the planned schedule is there, and i've sent a mail before the meeting to ML as well: 14:08:17 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-July/034555.html 14:09:12 i guess we need to wait for some responses/reviews and if the schedule is OK to everyone then we can merge it 14:10:12 (we already reviewed it, and for us it looks good) 14:10:33 that's all about the tasks of week R-12 14:10:46 now comes R-10 week's task 14:10:48 s 14:11:15 1st task from R-10: 'Generate a list of intermediary-released service deliverables that have not done a release in this cycle yet and propose release model change for them (hberaud)' 14:11:30 so 14:11:44 from the list 14:12:05 I think only python-openstackclient and swift could be good clients 14:12:08 thoughts? 14:12:55 as I said I don't think we want to move ironic deliverables as they follow their own cadence 14:13:10 and requirements should be ignored 14:13:30 looking at the list of deliverables they are the usual ones (ironic, swift, even the python-openstackclient was there time to time) 14:13:42 yeah 14:13:45 (ironic* deliverables) 14:14:52 so probably we don't need to change any of these to cycle-with-rc 14:15:06 +1 14:15:32 anyway, the countdown mail's topic is mostly about this, so we can rephrase the mail a bit and list these deliverables 14:15:41 is that OK? 14:15:47 LGTM 14:16:04 OK, then let's handle this at the mail review 14:16:12 good 14:16:19 next task then 14:16:39 2nd task from R-10: 'Propose convenience releases for Yoga to ease the transition of Yoga to Extended Maintenance and avoid rush and broken releases when the transition deadline is coming (hberaud)' 14:16:52 patches were proposed: https://review.opendev.org/q/topic:yoga-convenience-before-em 14:16:55 thanks hberaud o/ 14:17:13 thanks the abandons 14:17:16 we got some review from PTLs / release liaisons already \o/ 14:17:42 maybe take these into consideration https://zuul.opendev.org/t/openstack/config-errors?branch=stable%2Fyoga 14:17:45 yepp, as we discussed, I've abandoned those that had no functional changes, hence no need for a release 14:18:45 frickler: oh, yes, those might cause some release-job-failure anyway, so good idea to skip them 14:19:01 if no fixes land for the zuul errors 14:19:25 although those projects cannot have any patches merged anyway 14:20:37 #info yoga convenience release before EM: consider skipping deliverables with zuul config errors: https://zuul.opendev.org/t/openstack/config-errors?branch=stable%2Fyoga 14:20:58 frickler: yepp, gates are clearly broken for them 14:21:21 frickler: i wouldn't be surprised if their master branch was also broken, to be honest... 14:22:40 list of errors for master is a bit shorter 14:23:09 ++ 14:23:28 cinder eol'ing their em branches is also likely to cause a lot of job config errors other projects are going to need to clean up 14:23:39 nevertheless, the yoga release patches are there, so they will get reviews / we need to review them as they got reviews 14:24:22 fungi: good point, the new EM replacement process might have some effect on the yoga transition 14:24:46 sure. on that note, a reminder to keep an eye on (and provide feedback for) the evolving proposal to drop "extended maintenance" if stable branch topics are of interest: #link https://review.opendev.org/888771 14:24:56 i mean, cinder + EM reminded me to the EM process change o:) 14:25:53 fungi: thanks for the link! yes, we need to follow that resolution 14:26:31 anything else to add regarding this task? 14:27:09 nope 14:27:56 ok, next task then: 14:28:17 3rd task from R-10: 'add an independent deliverable file for xstatic-angular-fileupload (see week R-13) (elod)' 14:28:27 #link https://review.opendev.org/c/openstack/releases/+/889385 14:28:33 i've created the patch ^^^ 14:28:47 ack 14:28:57 and Vishal already updated with a release as well 14:29:16 nice 14:29:45 we have to keep an eye on this one as i see some errors in the validator job about missing things 14:30:52 hopefully with the proper hash and yaml format those will be sorted out 14:31:25 and that were all the tasks for R-12 and R-10 14:31:48 #topic Assign R-8 week tasks 14:32:06 actually, I've added myself as meeting chair, 14:32:29 and thus added my name to the tasks as hberaud will be on vacation that week 14:32:59 so all tasks taken 14:33:07 thanks 14:33:13 np 14:33:15 #topic Review countdown email 14:33:22 #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:33:40 OK, so we have to edit this on the fly with the list of deliverables 14:34:51 the link is not necessary 14:35:02 as no patches have been generated 14:35:03 yepp, let me delete it 14:37:04 the next sentence should be updated too 14:39:14 Vishal Manchanda proposed openstack/releases master: Add xstatic-angular-fileupload first release via the releases repo https://review.opendev.org/c/openstack/releases/+/889385 14:40:07 OK, something like that. 14:40:29 is the mail content acceptable? 14:40:36 LGTM 14:41:02 ACK 14:41:10 then I'll send it after the meeting 14:41:22 I think we have to add the teams in the email subject 14:41:48 i don't want to pollute the countdown mail subject with team names, to be honest 14:41:51 [ironic][swift][openstackclient] 14:41:56 Email looks good 14:41:58 as you want 14:42:24 yeah, in the past we sent separate mail with the model change 14:42:43 ok 14:43:37 considering that ironic, swift, and openstacksdk got the same question time to time and they never wanted a model change, i think we don't need to push them 14:43:47 ok 14:43:49 wfm 14:43:55 thanks 14:44:07 #topic Open Discussion 14:44:24 we don't have anything mentioned on the pad 14:44:37 I've nothing on my end 14:45:39 I'll be OOO from friday next week for 3 weeks 14:45:49 fungi's point about the zuul config errors that will come when cinder EOL's all their EM branches (up to xena) is a good warning though 14:45:52 and I'll be fully afk 14:46:17 hberaud: that sounds a nice long summer vacation, enjoy your free time! :) 14:46:25 thanks 14:46:28 mainly just check those early and don't let them take you by surprise later at a less convenient time 14:46:57 fungi: ++ 14:47:07 thanks 14:48:17 it should be "easy" to fix though as instead of the branches -eol tags should be used for cinder repo checkout 14:48:25 (famous last words? o:)) 14:48:38 anyway, we will see 14:49:27 i'll might be also off for some days in august, but i don't have big plans ahead... 14:50:08 okay, if there is no other topic to discuss, then let's not waste our time and let's end the meeting! 14:51:47 thanks everyone for participating & see you in 2 weeks at the usual meating time on Friday 14:00 UTC @ Aug 11th (note that next week's meeting is marked as 'skipped'!) 14:51:53 thanks elodilles 14:51:54 #endmeeting