14:00:00 #startmeeting releaseteam 14:00:00 Meeting started Fri Aug 20 14:00:00 2021 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:00 The meeting name has been set to 'releaseteam' 14:00:05 Ping list: elodilles armstrong 14:00:14 We're way down on line 272 now. 14:00:16 o/ 14:00:28 #link https://etherpad.opendev.org/p/xena-relmgt-tracking 14:00:33 o/ 14:00:35 Will just wait a couple minutes for folks. 14:02:04 #topic Review task completion 14:02:33 1) Propose autoreleases for cycle-with-intermediary libraries => https://review.opendev.org/q/topic:%22xena-final-non-client-libs%22+(status:open%20OR%20status:merged) 14:02:48 Almost all patches are now merged 14:03:32 We'll rediscuss about the final non-client libs in a bit 14:04:01 2) Make sure the next development series name has been added to the data/series_status.yaml file => Done ttx merged the patch last Monday 14:04:31 Also I just sent a fix about yoga's schedule => https://review.opendev.org/c/openstack/releases/+/805376 14:05:00 3) Update the feature list and allowed stable branch names in devstack-gate for the new stable branch. 14:05:06 o/ 14:05:11 elodilles: The floor is yours 14:05:31 this task is actually not needed anymore 14:05:42 Ok 14:05:43 as devstack-gate is now phased out 14:06:13 the patch has merged that removed it from the process 14:06:16 Your update is now merged => https://review.opendev.org/c/openstack/releases/+/803774 14:06:20 Thanks 14:06:27 no problem :) 14:06:46 #topic Non-client lib freeze is now two weeks before feature freeze?? 14:06:56 ttx: You're right 14:07:11 yeah, i was surprised checking the schedule, and then realized Wallaby was not like that 14:07:28 the patch for yoga will fix the same error 14:08:00 I was like.. library freeze already?? and then "how come we could skip next week's meeting? Ususally we can't" 14:08:14 I think I inverted oslo's feature freeze and the final freeze 14:08:18 No biggie but the weekly emails might be off in messaging 14:08:32 Yeah 14:08:39 Like we may have announced the wrong dates, or not given enough notice 14:08:54 so it might be good to post somethign about it 14:09:04 (in the next weekly) 14:09:15 I'll do that 14:09:23 Let's transform the email with that 14:10:44 #topic Assign R-5 tasks, prep countdown contents and skip next week meeting? 14:10:50 sorry 14:10:58 #topic Review countdown email contents 14:11:08 #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:14:02 elodilles: yoga 14:15:28 ttx: 19 14:15:57 hberaud: ohh, sorry, i thought we talk about features that cannot be included to this cycle (xena) - due to missing the deadline 14:16:07 np 14:16:28 hmmm why are we saying next week is Cena-3? It's in two weeks 14:16:49 "This coming week is the deadline for client libraries" -- no it's not 14:16:55 elodilles: "and defer features that won't make it to the $next-series cycle." 14:16:56 looks like the wrong template 14:17:16 I used this one https://releases.openstack.org/reference/process.html#r-6-week-final-library-release-deadline 14:17:39 yeah the trick is this week is r-7, not r-6 14:17:39 ttx: As I proposed the final non-client lib 14:18:06 so saying "next week is r-5" on r-7 is weird 14:18:07 ok then let's use the R-7 14:18:17 it's ok for you? 14:18:33 is that the one you sent last week? 14:18:38 yes 14:18:46 checking 14:18:51 But I transformed it 14:19:24 ok yes we shoudl reuse r-7 and reword it a bit 14:19:24 to adapt to the sliding of "final non-client" 14:19:28 ok 14:22:20 haha, edit war 14:24:00 lol 14:24:26 Well, sorry for the confusing I decided to readapt email to the given schedule 14:24:32 s/email/emails 14:24:53 yeah we might want to edit the Xena schedule and fix it 14:25:03 I think that now we are good as the trick was between R-7 and R-6 14:25:05 yes 14:25:32 Better one week early than one week late 14:25:54 We probably need to move some tasks around 14:26:08 on the relmgt-tracking 14:26:30 also for those not branched we might consider re-releasing some libs 14:26:58 Hervé Beraud proposed openstack/releases master: fix xena's schedule https://review.opendev.org/c/openstack/releases/+/805394 14:27:13 here is the xena update ^ 14:27:28 lgtm 14:27:33 thanks 14:27:58 So I'm now wondering re: process tasks 14:28:06 we likely skipped R-7 tasks and used R-6 14:28:59 let me check 14:29:04 ah no, looks like we did R-7 tasks on R-8 14:29:29 Well, I personnaly did those R-7 tasks 14:29:57 I notified the infra team about the signing keys 14:30:14 ok so for R-6 tasks there is not much left to do 14:30:34 I'd say we should be open to re-releasing some libs as need be 14:30:39 I checked the python runtimes and templates with the TC, everything is now merged 14:30:45 speaking of keys, i'll need to refigure the key attestation process, skk keyservers have all been taken down in recent months and the domain goes nowhere now 14:30:46 Agree 14:31:02 er, sks i mean 14:31:02 (agree with with re-releasing some libs) 14:31:30 I think we need to keep the next meeting just in case 14:31:46 yes 14:31:59 there are now no widely-available openpgp keyservers which publish third-party signatures (though openpgp.org has some ideas on how they might go about doing that safely, caff-style) 14:32:00 fungi: ack 14:32:19 Thanks for the heads up 14:33:25 Well I think we can goes on to the next topic 14:33:29 #topic Yoga 14:34:00 Just to socialize this point, I won't be candidate for Y => http://lists.openstack.org/pipermail/openstack-discuss/2021-August/024158.html 14:34:14 thanks for your service, sir! 14:34:38 My pleasure, thank you all for all your helps 14:34:53 yepp, thanks for the hard work so far! o:) 14:35:05 Thanks :) 14:35:10 Thanks to you our process is now nearly foolproof 14:35:34 lol 14:35:34 you documented all the diffs and added all the missing things 14:35:50 And interverted all the weeks :) 14:36:09 Just one question 14:36:14 shows that human oversight is still needed :) 14:36:23 :) 14:36:25 Do we want to run a PTG? 14:36:36 I'd say that depends on the new PTL 14:36:44 +1 14:36:48 and how much change they intend to drive 14:37:10 If it's a copy-paste cycle I' 14:37:19 d say it's not /necessary/ to have one 14:37:25 Ok then let's put this topic aside 14:37:46 elodilles: considering taking the torch? 14:38:51 ttx, well, we discussed it with hberaud a bit, and I'm not confident + a bit busy :/ 14:39:25 You'd be great elodilles! 14:39:35 I think hberaud and I can step up a bit and help you in the first year. I'm very confident you can do it 14:39:37 smcginnis: :D thanks :) 14:39:49 Not confident and a bit busy is actually one of the prerequisites. 14:39:56 lol 14:40:04 :) 14:40:09 +1 from my side if you need help 14:40:12 Combined with no process changes on Yeti it could be a calm first cycle 14:40:49 ok, I will think about this :) 14:41:04 Thanks 14:41:12 Back to A will be fun when things will start breaking all over, but you can pass it on to someone else by then :) 14:41:18 is there a deadline until decision needs to be made? 14:41:46 August 24 14:41:56 coming in quick :) 14:41:59 :D that's pretty close :D 14:42:22 "No rush they said" 14:42:25 lol 14:42:29 :D 14:42:47 happy to answer questions in PM if you have any sensitive ones. 14:42:58 +1 14:43:03 ttx: thanks in advance! 14:43:36 #topic Open Floor 14:43:48 Anything else to discuss today? 14:43:54 no 14:44:14 nothing from me either 14:46:03 Ok thanks everyone, see you next week! 14:46:08 #endmeeting