14:00:01 #startmeeting releaseteam 14:00:01 Meeting started Fri Jan 19 14:00:01 2024 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:01 The meeting name has been set to 'releaseteam' 14:00:08 o/ 14:00:13 Ping list: elod frickler 14:00:19 https://etherpad.opendev.org/p/caracal-relmgt-tracking 14:00:29 meet you at line 208 ^ 14:00:32 o/ 14:00:44 #topic Review task completion 14:00:48 \o 14:00:54 Review any remaining milestone-2 exceptions 14:01:03 https://review.opendev.org/q/topic:caracal-milestone-2 14:01:08 everything is done 14:01:21 2) Plan the next release cycle schedule, thanks elodilles 14:01:34 https://review.opendev.org/c/openstack/releases/+/906050 ttx and myself sent comments 14:01:43 elodilles: Do you want to add something? 14:01:47 I think the 6-7-8 version is a strong contender 14:01:54 yep 14:01:56 Let's see if it passes the community test 14:02:23 thanks for the reviews o/ 14:02:40 maybe we can share it via the release countdown mail? 14:02:48 good idea 14:02:48 or should i send a separate mail? 14:02:58 but we have no mail this weel 14:03:00 week 14:03:11 ok, then i'll send a mail :D 14:03:11 separate mail it is! 14:03:15 :) 14:03:23 easy as that 14:03:25 thanks elodilles 14:03:53 np :) 14:03:59 3) create patches with 'abandoned' flag against monasca, sahara, freezer and solum 14:04:27 https://review.opendev.org/q/topic:relmgt-inactive-projects 14:04:44 will double check these patches after the meeting 14:05:19 i think this is the right way: to remove them (and not mark them as abandoned) 14:05:24 thanks again elodilles 14:05:27 np 14:05:30 yes 14:05:47 next topic 14:05:52 #topic Assign R-10 tasks 14:06:21 everything is no assigned 14:06:44 #topic Open Discussion 14:06:49 s/no/now 14:07:20 I marked meeting in two weeks as skipped 14:07:28 We have a question from rosmaita 14:07:34 ttx: +1 sounds good 14:07:40 He is not around 14:07:44 (won;t be around and it seemed not necessary) 14:08:28 Where have you seen that? There => https://review.opendev.org/c/openstack/project-team-guide/+/897505 ? 14:08:51 (it seemed not necessary) 14:09:06 I was talking about the meeting in two weeks 14:09:17 ok 14:09:42 iiuc the idea about the p-t-g patch was just for (some of) you to review as a sanity check 14:10:25 though also there are deep links from the releases site which may need fixing when that merges? 14:11:31 ah, yes, maybe someone can check that, too. I also made a mental note that the linked tempest doc about stable branch handling will need updating 14:11:44 reading 14:12:04 at first skim it's only linking to the maintenance-phases target which i don't think is changing, so probably fine 14:12:56 maybe some changes are required there https://releases.openstack.org/reference/using.html#tools-list-eol-stale-branches-sh 14:13:03 and surely elsewhere 14:13:36 hberaud: yepp, thanks for mentioning it, i'm planning to propose update to that ^^^ 14:14:26 some related question from me would be, now that the tooling changes have been merged and (mostly?) tested, how does your schedule look like for actually moving yoga to unmaintained? do you have some idea about that yet? in the etherpad I see that the umaintaining of zed is also drawing nearer 14:14:30 good find, i only looked at the main page 14:16:01 frickler: i can propose now EOM tagging for all the yoga deliverables and add unmaintained/ from that point, 14:16:23 one question is that should we do it via a single huge patch, 14:16:35 or propose them per team? 14:16:51 I'd suggest by team 14:17:01 a single patch would avoid having discussions with each team 14:17:07 hberaud: i also tend to that direction 14:17:27 is there actually team feedback involved? 14:17:58 but also it would likely make management like abandoning changes easier to do it in peaces, so I'm not objecting this 14:18:08 pieces even 14:18:16 frickler: yes, that's why i was thinking on it, though it would have a bigger impact on zuul as it would start massive amount of tagging and branch cutting 14:18:37 * frickler loves stress testing zuul ;) 14:18:40 :D 14:19:03 IMO it would be more easier to manage this topic by piece 14:19:09 well, i'm sure zuul could handle that :) 14:20:02 anyway, if the planned schedule more or less is "right now", I'm happy with that 14:21:06 frickler: yes, we can do that right away, though the branch deletion script needs an update before we can use it with EOM tags 14:22:00 anyway, I'll propose then yoga-eom tagging patches per team as a next step 14:22:07 is there some automation for abandoning patches btw.? it might be friendly to abandon them with a note that they can be reproposed against unmaintained/yoga if needed 14:22:13 is that OK? ^^^ 14:22:31 fine for me 14:22:56 i know that some folks has a nice script for that 14:23:05 though i don't have that script 14:23:27 but would you expect projects to do that or is that a release team task? 14:24:34 I know there is some script in the neutron repo for auto-abandoning old reviews, one might be able to adopt that 14:25:26 (I quickly checked, less than 150 patches are open against 'project:^openstack/.* branch:stable/yoga') 14:25:52 frickler: i can do it 14:26:01 saying "less than" sounds like you consider that to be manageable manually? ;) 14:26:19 i'll look for the script 14:26:23 of course :D 14:26:55 tools/abandon_old_reviews.sh in openstack/neutron 14:27:07 ahh, there it is! 14:27:08 thanks :) 14:27:24 i'll taylor that to our case then :) 14:29:13 Anything else. 14:29:14 ? 14:29:53 nothing else from me for now 14:30:07 then I think we are done 14:30:11 thanks everyone 14:30:23 #endmeeting