17:00:05 #startmeeting releaseteam 17:00:05 Meeting started Thu Feb 11 17:00:05 2021 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:10 The meeting name has been set to 'releaseteam' 17:00:11 #link https://etherpad.opendev.org/p/wallaby-relmgt-tracking Agenda 17:00:16 Ping list: ttx armstrong elod, damani 17:00:19 o/ 17:00:26 o/ 17:00:26 o/ 17:00:29 We're way down on line 324 now. 17:00:35 Will just wait a couple minutes for folks. 17:00:41 hi 17:03:15 Ok let's go 17:03:22 #topic Review task completion 17:03:32 Generate a list of intermediary-released service deliverables that have not done a release in this cycle yet. => Done 17:03:39 Only swift met the conditions => https://review.opendev.org/c/openstack/releases/+/774682 17:04:27 And vitrage-dashboard but they proposed new releases so I think we can abandon => https://review.opendev.org/c/openstack/releases/+/774683 17:04:35 Thanks armstrong 17:04:36 I'd say it's unlikely that they will change (swift) 17:04:58 since they have always been in the release-as-needed model 17:05:08 No idea, I'll see that after the countdown email that will speak about 17:05:38 Let's wait a bit about for feedback from them 17:05:51 Next task 17:06:01 Start a ML thread about recent release failures with tripleo deliverables on ussuri => Done thanks ttx 17:06:10 However you said that we need to reenqueue os-collect-config 11.0.2 and tripleo-ipsec 9.3.1 (or release 11.0.3 and 9.3.2 on stable/ussuri) 17:06:33 right? 17:06:52 Do you want to handle that point? 17:07:34 I'll leave choice to fungi 17:07:44 (between reenqueuing and rereleasing) 17:08:00 ok 17:08:11 not sure how easy it is to get those refs 17:09:19 I would argue that releasing 11.0.3 and 9.3.2 is more straightforward 17:09:57 well, we can do it, but that means 11.0.2 and 9.3.1 are nowhere to be found 17:10:08 Exact 17:10:09 so it's suboptimal compared to reenqueuing 17:10:15 Yes 17:11:41 Well I added this point to the next week tasks I think we can continue for now. Let's wait a bit for fungi's feedback 17:11:56 We'll update the task accordingly 17:12:15 yep, sorry, also on a conference call, catching up 17:12:20 np 17:12:47 what was the failure condition? 17:13:03 tags got pushed but pypi uploads didn't happen? 17:13:11 Good question, I don't really remember 17:13:47 Tag was not pushed 17:13:57 tag-release job failed before that 17:14:13 That's the post job that runs on a openstack/releases merge 17:14:15 I wonder why I can't retrieve the point on our previous agenda 17:14:22 #link http://lists.openstack.org/pipermail/openstack-discuss/2021-January/020112.html 17:14:33 that's a message i had saved to look into, but have been swamped 17:14:54 So I'd say the ref that needs reenqueing in that commit on openstack/releases 17:15:08 which should retrigger the post jobs 17:15:38 IIRC It was due to a lack of stable branches 17:16:17 yeah we did fix the stable branch situation, but of course that did not retrigger those post jobs 17:16:26 Yes exact 17:16:58 So I think that reenqueuing could work now 17:17:08 willing to give that a shot 17:17:27 Thanks 17:17:41 so reenqueue those two openstack/releases changes into the release-post pipeline? 17:17:59 Hm yes 17:18:10 should be able to do that once this call ends 17:18:52 Worth trying 17:20:12 I think we can continue, anything else about this point? 17:20:19 nope 17:21:17 I leave the next week task to be sure to not forget that 17:21:30 #topic Socialize `test-release-openstack` nodeset switch to focal 17:22:17 Just a heads up about a recent change merged yesterday and related to our `test-release-openstack` 17:22:37 nodeset have been switched to focal 17:22:52 what is the expected impact? 17:23:08 a number of the release jobs themselves are already using an ubuntu-focal nodeset anyway, right? 17:23:17 I don't expect issue as all our jobs are already on focal, but worth to mention it during the meeting 17:23:25 Yes 17:23:38 AFAIK it was the last one on bionic 17:23:53 https://opendev.org/openstack/project-config/commit/3310a349a4ecf8187f242b9a8fe7d62465f3e083 17:24:00 yeah, it's just that opendev is behind on scheduling a default nodeset switch from ubuntu-bionic to ubuntu-focal 17:24:12 i want to start pushing on that in the next week 17:24:16 np 17:24:25 focal's already almost a year old, we should have done it sooner 17:24:57 but setting it explicitly in jobs now is a good way to find out whether they'll break too 17:25:11 Yes 17:25:57 So if you observe strange behavior then remember that topic 17:26:13 I think that's all for this point 17:27:06 #topic Onboarding Elod 17:27:37 elod: thing promised thing due https://giphy.com/gifs/mlb-alds-2018-3Mb5hvWOLe8hq6gZHc 17:27:43 Onboarding going on here? 17:27:55 Welcome on board elod 17:27:57 :D 17:28:03 oh hahaha 17:29:00 Now I need to figure it how to give you the ACLs :) 17:29:01 thx :) I'll work on doing useful reviews :) 17:29:22 ttx: any idea ^ 17:30:03 https://review.opendev.org/admin/groups/5c75219bf2ace95cdea009c82df26ca199e04d59,members 17:30:34 I guess we can do a bit of cleanup too 17:30:43 Yes 17:30:49 Thanks for the link 17:31:07 removing inactive members... although I'd keep Doug around since he still does reno reviews 17:31:31 Elod you are now in the list let me know if that work for you => https://review.opendev.org/admin/groups/5c75219bf2ace95cdea009c82df26ca199e04d59,members 17:31:47 ok that should work 17:32:28 evrardjp had officialized is departure during last cycle 17:32:30 hberaud: i have the +2, so it works \o/ 17:32:38 \o/ 17:33:38 I updated Jean Philippe 17:33:56 ttx: any idea about Kendall? 17:34:31 AFAIK she is more or less still active 17:34:43 She has been focusing on her TC vice-chair role 17:35:28 I'd ask her if she plans to take up core reviews again in the future, or if we can downgrade her to mere +1 17:35:39 ack 17:36:00 Then for now I think we are ok with the cleanup 17:36:18 WFY? 17:37:02 yes 17:37:08 Ok move on 17:37:11 #topic Review countdown email contents 17:37:16 https://etherpad.opendev.org/p/relmgmt-weekly-emails 17:38:38 I didn't speak about vitra-dashboard as they already gave us a response about cycle-with-rc 17:38:38 hmm, that sounds a bit aggressive 17:38:50 " In absence of answer by the end of R-10 week we'll consider 17:38:52 that the switch to cycle-with-rc is preferable. 17:38:54 " 17:39:08 I'm not sure we can make that switch without any team feedback 17:39:25 Ok so we need to upgrade our doc 17:39:33 too 17:39:37 Let me try to make it a bit sweeter 17:39:44 Feel free 17:43:02 ok taht sounds a bit less definitive 17:43:10 Definitelly 17:43:23 Otherwise looks good 17:43:36 I'll propose a patch for your doc to reflect that 17:43:39 maybe we could say that we'll approve the Xena release schedule by DATE? 17:44:14 Yes 17:44:32 Deadline is next week, exact? 17:44:53 "Make sure the next development series name has been added to the data/series_status.yaml file." 17:45:00 Looks like yes 17:45:50 Yeah I agree we don't need to speak about 24w 17:46:01 ok done 17:46:10 Awesome, I'll send it tomorrow 17:46:44 #topic Assign R-8 tasks 17:47:02 done 17:47:12 everything is already assigned 17:47:31 #topic Open floor 17:47:45 Anything else to discuss today? 17:47:53 no 17:48:12 nothing from me either 17:48:54 nothing 17:49:13 OK, thanks everyone. Almost there! 17:49:37 Thanks hberaud ! 17:50:01 #endmeeting