16:00:13 #startmeeting releaseteam 16:00:14 Meeting started Thu May 7 16:00:13 2020 UTC and is due to finish in 60 minutes. The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:17 The meeting name has been set to 'releaseteam' 16:00:18 Ping list: ttx armstrong diablo_rojo, diablo_rojo_phon 16:00:27 #link https://etherpad.opendev.org/p/ussuri-relmgt-tracking Agenda 16:00:36 o/ 16:01:20 o/ 16:01:49 #topic Review week tasks completion 16:01:59 Processing remaining stable branches. 16:02:03 o/ 16:02:09 I believe that's all complete. 16:02:25 * ttx checks 16:02:34 Next, notify documentation team. 16:02:51 Some nice notes in the etherpad for that. Looks like evrardjp and team got everything in place. 16:03:04 "Test the release process" 16:03:25 o/ 16:03:28 Patch is up. You can go ahead and approve that whenever hberaud. 16:03:34 Thanks for the docs updates for those things too. 16:04:12 you're welcome, I currently prepare other similar updates 16:04:15 And for the next of getting final RCs for anyone that has merged things other than translations and CI things. 16:04:25 #link https://review.opendev.org/#/q/topic:r1-final-rc-deadline+(status:open+OR+status:merged)) Final RCs 16:05:53 re:stable, we seem to be missing one: patrole 16:06:07 (all the other missing are cycle-trailing) 16:06:35 Isn't patrole like devstack and not branched? 16:06:35 hmm 16:06:39 stable-branch-type: none 16:06:47 OK, good. 16:06:54 probably should not be reported by list-deliverables --no-stable-branch --series ussuri --cycle-based-no-trailing 16:06:54 yeah, patrole is branchless like tempest 16:07:33 ttx: I think I had noticed that before and never had time to dig into why/how it should be excluded from there. 16:07:37 * ttx adds to backlog 16:07:43 We don't get tempest in the list, so not sure what's different. 16:07:52 (at the bottom of the etherpad) 16:07:53 #topic Assign next week tasks 16:07:58 ttx: Thanks! 16:08:17 First one is really a reminder for all of us. 16:08:36 Nothing should really be happening until the final tagging unless it's a critical thing to release. 16:09:04 ttx, diablo_rojo: Any word on coordination for a press release? 16:09:21 smcginnis: Press release is scheduled at 10am CT 16:09:23 15 UTC 16:09:42 So "On release day, approve the final release patch created earlier." should happen early. 16:09:52 We have a community call at 16UTC iirc 16:09:59 err 14UTC 16:10:29 smcginnis: I can approve it in my morning if you want 16:10:33 Yeah 14 UTC 16:10:35 So maybe 12UTC would be a good target? 16:10:40 assuming you close the previous day with a +2 16:10:56 ttx: I'll put you're name down for the task, but will probably be watching. 16:11:32 Anyone want to take the check for missing-releases? 16:11:42 done 16:11:43 Thanks hberaud 16:11:57 I will update the releases.o.o info. 16:12:15 Which includes setting default series in the data file. 16:12:19 I can run missing-releases if you want... or did hberaud volunteer? 16:12:30 I'm volunteer 16:12:32 He did 16:12:33 ok 16:12:44 And I will send out the announcements. 16:14:11 #topic Review countdown email 16:14:20 Hmm, I don't remember if I staged the next week. 16:14:30 #link https://etherpad.opendev.org/p/relmgmt-weekly-emails 16:14:36 Guess I did. 16:15:27 Not too much to say since this is the release week. 16:15:33 smcginnis: email content implies that we process all those last-RCs before its' sent 16:15:46 so maybe wait until late Friday to send it :) 16:16:11 Made a note. 16:16:26 so we need to get an ack on those ASAP 16:16:33 or just abandon them if not 16:16:59 I think there were only a couple that had important looking bugfixes. 16:17:05 Most were just good to have translations. 16:17:23 Not to discount any work the translations team has done, but just saying in relative importance. 16:17:33 OK would be good to document that in the review, and chase down those with significant stuff 16:18:36 I'll add a comment on those starting from bottom 16:18:42 Thanks! 16:18:49 we could until wednesday before drop those who stayed unmerged and with importance 16:18:59 s/with/without/ 16:19:04 We need to way before Wednesday. 16:19:18 Today is the deadline for a reason. 16:19:25 ok 16:19:55 #topic PTG or not PTG 16:20:37 we are already late for signing up 16:21:07 we could sign up by booking at last minute though 16:21:19 Which was the plan right. Easier for us to fit in where there's time left after everything else is settled. 16:21:19 Just won;t appear on the published schedule 16:21:29 and will have limited solutions 16:21:44 diablo_rojo: Have the ethercalc link handy? 16:21:49 smcginnis, yep 16:21:51 one sec 16:22:03 https://ethercalc.openstack.org/126u8ek25noy 16:22:15 #link https://ethercalc.openstack.org/126u8ek25noy PTG Ethercalc Signup 16:22:31 smcginnis, also need to do the survey once that is done 16:22:35 * diablo_rojo grabs that link too 16:23:15 #link https://openstackfoundation.formstack.com/forms/june2020_virtual_ptg_survey PTG Survey 16:23:45 What do folks think of June 1 in the 13-14UTC time slot? 16:24:30 Or 21-22, but I know that's getting late for EU. 16:24:38 Not like any of us are going anywhere. 16:24:57 June 1 works, was waiting for the TC pick 16:24:58 I'd obviously prefer the 21-22 16:25:32 Particularly since I should attend the Interop stuff. 16:25:33 21UTC works for me too 16:25:55 Or 16-17 on June 2 looks like it could work well and be a better timeslot for most. 16:26:20 Works for me. 16:26:25 +1 for 13-14 or 16-17 16:26:50 I think June 2 16-17 would be my preference, but I can make any of these work. 16:27:37 ok how about we wait for the TC pick to choose between those 16:27:44 should come soonish 16:28:07 ttx: Any idea when that is planned to be decided? 16:28:33 smcginnis, I saw the poll go out yesterday and responded. 16:28:36 diablo_rojo probably knows better 16:29:11 Looks like we've had 7 members respond so far? 16:29:29 I suppose they are looking at the same times? 16:29:49 smcginnis, yeah kinda 16:30:03 #link https://doodle.com/poll/3ywuywu825hu7v23 TC PTG Poll 16:30:27 All the times (but I think filtered on what mnaser could do?) basically. 16:30:52 diablo_rojo: those are all the times based on availablities :) 16:31:02 mnaser, ohhhhh that makes sense. 16:31:04 some blocks had "rooms" blocked for all times 16:31:33 mnaser, got it. okay, my bad :) 16:31:46 OK, we can wait a bit then and pick our time based on what the TC goes with. 16:32:08 #topic Open Floor 16:32:13 Anything else to discuss today? 16:32:28 Nothing from me. 16:32:41 +1 16:32:41 nope, almost done extarcting significant changes from the RC requests 16:33:57 OK, let's wrap it up then. 16:34:03 Thanks everyone! 16:34:09 #endmeeting