14:01:01 #startmeeting releaseteam 14:01:01 Meeting started Fri Dec 10 14:01:01 2021 UTC and is due to finish in 60 minutes. The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:01 The meeting name has been set to 'releaseteam' 14:01:11 Ping list: hberaud ttx armstrong 14:01:13 o/ 14:01:14 o/ 14:01:28 \o/ 14:01:59 the time flies... 14:02:22 it's already 3pm 14:02:29 ttx will be late a few mins as he mentioned an ~hour ago 14:02:36 no problem 14:02:49 hberaud: well, and december :) almost yoga-milestone-2 :) 14:02:55 I was just thinking it was 1 or 2pm 14:02:57 :) 14:03:00 : 14:03:01 :] 14:03:09 #link https://etherpad.opendev.org/p/yoga-relmgt-tracking 14:03:12 yeah 14:03:27 so we are at line 116 14:04:16 #topic Review task completion 14:04:28 so the only task was: 14:04:44 Prepare Xena cycle trailing, deadline is next week 14:04:59 I've sent the reminder mail ( http://lists.openstack.org/pipermail/openstack-discuss/2021-December/026194.html ) 14:05:25 and actually we didn't need to propose another patches 14:05:53 as the former trailing-xena branch cut patches (with releases) were still open: 14:06:03 yep 14:06:05 https://review.opendev.org/q/topic:trailing-xena 14:07:06 and next week is the deadline for trailing-xena releases, if i'm not mistaken 14:07:37 yes 14:07:45 the 16 14:08:05 so these should be merged next week until 16th of December 14:08:14 yes 14:08:33 anything to add here? 14:08:37 nope 14:08:47 cool, thanks 14:09:00 yw 14:09:03 then next topic 14:09:11 #topic Skipping next 3 meetings? 14:09:18 +1 14:09:45 Anyway I won't be online between the 20 and the 3 of january 14:09:50 since that will be holiday period i think this is fair 14:10:02 o/ 14:10:06 o/ 14:10:20 yeah I think if we assign tasks in advance we should be fine 14:10:21 I'll be also on PTO, but will read mails and check patches time to time 14:10:24 ttx: o/ 14:11:13 ok, I see no objections 14:12:06 i'll still be around if there are problems, feel free to reach out 14:12:18 #agreed Skip meetings for week R-15, R-14 and R-13 14:13:04 fungi: good, thanks! be careful what you offer, we might need your help :) 14:13:14 :) 14:14:08 #info next meeting is R-12, 7th of January 14:14:25 #topic Assign R-15 and R-13/R-12 tasks 14:14:53 next week task is: 14:15:01 Review any remaining trailing project exceptions 14:15:21 i've added 'all' to it, hope it's not a problem o:) 14:15:32 :thumbsup: 14:16:09 then the next one is from tasks of week R-13 14:16:18 Ahead of MembershipFreeze, run governance_consistency.py 14:16:33 oh, i see ttx added himself there \o/ 14:16:36 thanks 14:16:53 all covered now 14:17:20 sweet, thanks to all \o/ 14:17:24 hm 14:17:37 Where are the task for milestone 2? 14:17:46 s/tasks 14:18:07 hberaud: do we miss something? 14:18:11 they have been trimmed a bit 14:18:14 let me check 14:18:15 but they are there 14:18:49 No it's ok sorry 14:18:54 ttx is right 14:19:02 i see only those: https://releases.openstack.org/reference/process.html#milestone-2 14:19:19 1 2 3 match, the description in truncated 14:19:24 is* 14:19:24 I was thinking that more tasks were there 14:19:32 yes 14:19:57 Pierre Riteau proposed openstack/releases master: Release cloudkitty 13.0.1 for victoria https://review.opendev.org/c/openstack/releases/+/821410 14:20:06 my bad 14:20:11 we all should refer to the process doc instead 14:20:14 maybe "subtask" were added separately in the past? 14:20:28 no, probably just a copypaste error 14:20:37 I was expecting more primary tasks 14:20:55 Pierre Riteau proposed openstack/releases master: Release cloudkitty 14.0.1 for wallaby https://review.opendev.org/c/openstack/releases/+/821411 14:21:40 should i add any task to the tracking pad? 14:21:46 no it's ok 14:22:04 until the root task is there it's ok 14:22:27 s/until/while/ 14:23:12 hberaud: ok, cool. of course if it's more that you volunteered for, then I can take over things 14:23:22 just let me know 14:24:10 anything else regarding this topic? 14:24:17 I think it's ok and you are on PTO monday and tuesday so let us help you :) 14:24:43 nope 14:24:57 hberaud: ack :) 14:26:05 #topic Review week R-13's countdown email content (could be done at R-13 week meeting?) 14:26:21 well, let's review it now since we agreed to skip R-13 o:) 14:27:17 but R-12's mail can be reviewed in 1st week of January 14:27:27 on the meeting 14:27:55 for now, please review: 14:28:05 #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 14:30:45 that "Changes proposing those deliverables for inclusion in Yoga have been 14:30:47 posted 14:30:55 " part assumes there are governance inconsistencies 14:31:17 but I guess people can ignore it 14:32:26 I updated the wording so that it works in all cases 14:32:49 LGTM now :) 14:32:50 I see, thanks! 14:32:59 LGTM 14:33:09 Also added a happy new year 14:33:16 I'll send it 30th or 31st of December :) 14:33:19 it's my non-robot side 14:33:26 ttx: :D 14:33:35 even better :] 14:33:38 even robots can be cheerful 14:33:55 indeed :) 14:34:08 there must be a gif for that 14:34:37 * for everything :] 14:34:41 https://giphy.com/gifs/HannahtheSpanner-robot-dance-dancing-approximating-happiness-1pA2SJ1g6amgbDSFdZ 14:35:20 :) 14:36:00 hopefully it won't be to much happy 14:36:18 more like ol' bob from the black hole 14:37:19 lol 14:37:36 :) 14:37:44 ok, i guess we can go to the last topic 14:37:51 #topic Open Discussion 14:39:19 we seem to have recently acquired an inefficiency in updating zuul's persistent configuration state on project branch creation 14:40:23 it's not particularly noticeable on one or a handful of new branch events, but when all of openstackansible got new branches added earlier this week, or when starlingx added a new branch to all of their repos yesterday, it left the ci system running basically no jobs for a few hours 14:40:58 it shouldn't act that way of course, and it's on our radar, just wanted to give you a heads up 14:41:07 ack 14:41:41 yeah, i noticed that, and suspected that openstack-ansible's branch creation has to do something with it 14:41:54 and if you're about to merge a change which adds lots of new branches, maybe give us a heads up 14:42:15 hopefully we'll have it fixed soon 14:42:25 fungi: ack, thanks for the info, we'll try to remember that 14:43:06 though i guess we are not expecting now any other 'mass branch creation' patch 14:43:34 probably not until rc time, but just in case 14:43:51 yepp, thanks, noted! 14:45:28 #action in case a change which adds lots of new branches is about to merge -> give heads up to infra team 14:45:36 and added here as well ^^^ 14:46:11 thanks 14:46:24 fungi: ++ 14:46:38 anything else? 14:47:27 branch creation will start at R-6 14:47:41 s/branches 14:48:07 so 3-4 weeks before RC 14:48:44 else nope nothing on my end 14:49:09 hberaud: yes, around rc1 patches, right? 14:49:37 nope around final library rlease deadline 14:49:49 oh, branching for libs 14:49:52 oh, i see, sorry 14:49:56 np 14:50:00 yeah, i didn't think about that 14:50:10 well, hopefully it'll be fixed by then anyway 14:50:33 it will happen in 10 weeks 14:50:51 so we are a bit large 14:50:56 ok, i'll search for that in the tracking page and maybe add a note there 14:51:56 okay, if there's nothing else, then let's close the meeting 14:52:15 thanks everyone for joining! o/ 14:52:24 #endmeeting