14:00:26 #startmeeting releaseteam 14:00:26 Meeting started Fri Feb 18 14:00:26 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:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:26 The meeting name has been set to 'releaseteam' 14:00:34 Ping list: hberaud ttx armstrong damani 14:00:36 o/ 14:00:50 #link https://etherpad.opendev.org/p/yoga-relmgt-tracking 14:01:06 o/ 14:01:40 we are at line 270 14:05:04 hmm. we have a bit less number of participants so far, that i've expected 14:05:37 i'm around, just very quiet 14:05:45 fungi: o/ 14:05:56 ok, let's start 14:06:14 #topic Review task completion 14:06:31 1st task: "Check with the Technical Committee to make sure Python runtimes have been determined for the next development cycle and that Zuul job templates have been created to include those runtimes." 14:06:45 it was on hberaud and damani 14:07:07 so I'll check with them later 14:07:15 i haven't seen any changes proposed for zen python runtimes 14:07:42 you mean Zed :) 14:07:47 but yes :) 14:07:49 zero 14:07:56 :] 14:07:58 and yoga is definitely the last listed on the pti page 14:08:54 anyway, i'll add it to next week tasks again 14:09:01 just to not forget about this 14:09:27 next task: 14:09:35 "Follow-up task: Make sure the next development series name has been added to the data/series_status.yaml file (elod)" 14:10:07 i've added to the proposed schedule patch: https://review.opendev.org/c/openstack/releases/+/824489/5/ 14:10:48 i wanted to ask whether we can merge this, but let's wait with this question till next week 14:11:32 #action Review and merge if possible: https://review.opendev.org/c/openstack/releases/+/824489/5/ 14:11:42 next task then: 14:11:54 "Propose autoreleases for cycle-with-intermediary libraries (excluding client libraries) which had commits that have not been included in a release. (damani, elod)" 14:12:19 we did that with damani, patches are here: https://review.opendev.org/q/topic:yoga-final-non-client-libs 14:12:59 most of the patches have been merged, 14:13:17 there are some -1's, 14:13:42 and some open patches without responses 14:13:57 since deadline is today, i'll merge them after the meeting 14:14:22 except the ones with -1 14:14:59 what about those without PTL approve? 14:15:15 armstrong: we need to force merge them 14:15:27 as it is stated in the commit message 14:16:23 ok 14:16:35 we are done with this weeks tasks 14:16:54 #topic Assign R-5 week tasks 14:19:29 I'll add my name to the tasks, but feel free to add yours as well if you can do some of them 14:20:50 ok 14:21:02 thanks, let's move on 14:21:07 I will add my name beside yours 14:21:19 armstrong: ++ 14:21:36 #topic Review countdown email contents 14:22:09 #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:22:39 please review, and let me know if you've found any mistake ^^^ 14:29:17 the email LGTM! 14:29:30 thanks armstrong o/ 14:29:32 :) 14:29:41 let's go to the next topic then 14:29:48 #topic Removing TC tags framework 14:29:57 #link http://lists.openstack.org/pipermail/openstack-discuss/2022-February/thread.html#27214 14:30:02 so we just have one week from the RC deadline to final release? 14:30:42 armstrong: exactly. 1 week only. 14:30:52 i mean 14:31:09 ok thanks elodilles 14:31:21 RC1 deadline: March 10th, 2022 14:31:30 Final RC deadline: March 24th, 2022 14:31:42 then 1 week: Final Yoga release: March 30th, 2022 14:31:54 yeah, there's more than one "rc deadline" so don't get confused 14:32:10 yepp 14:32:33 so, about the topic: 14:32:45 the rc1 deadline is the date by which projects need an rc1 tag, the final rc deadline is the last date projects are allowed to request subsequent rc tags after rc1 14:33:32 if they need another. yes. :) 14:34:49 so, about the tag removal: as the linked mail shows TC decided to get rid of the repo tags 14:35:04 like stable:follows-policy, and others 14:35:33 in our code we use ^^^ tag (to show some banner) 14:36:35 ttx said and I wrote too (to the mailing list) that we can drop this 14:37:25 I've propesed a small patch already (but got the comment that we need further cleanups as repo.tags are used other places as well) 14:38:42 I don't see any problem with that, but wanted to double check with the team, whether anyone sees any problem we could face by removing the tags 14:39:40 hberaud ttx : ping me if something comes to your mind that could be problem for us with this ^^^ 14:40:53 i'll update the proposed patch, or rather create a follow up patch, and we will see 14:41:21 i think that it about this topic 14:41:23 i'm doing similar removal work for the vulnerability:managed tag, and will be following up with the foundation webdev folks about any changes needed to the software lists on the www site 14:41:46 right now some of those governance tags result in specific things being included in the project list 14:44:28 to tell you the truth i don't know all the tags and where they are used. I've seen that project pages there are things triggered by the tags, but that's all :) 14:45:21 #topic Open Discussion 14:45:52 anything to mention here? 14:46:44 i've got the zed cycle artifact signing key generated, should have a change pushed shortly to record what it will be 14:47:03 but obviously we won't put it into use by the jobs until after yoga is done 14:47:19 fungi: thanks for the info! 14:47:23 this is just to get the attestation process for the new key bootstrapped 14:47:43 anything regarding that, that we could help with? 14:49:01 reviewing the change once it's up, sure 14:49:10 that'll be the next step anyway 14:49:50 just add me as reviewer and I'll review it! :) thanks! 14:49:56 you bet 14:50:14 :] 14:50:49 any other topic? 14:51:11 nothing from me 14:51:14 nothing from me 14:51:37 OK, thanks, then lets finish the meeting! 14:51:47 thanks elodilles! 14:51:49 thanks fungi and armstrong for joining! o/ 14:51:54 thanks 14:52:08 #endmeeting