15:31:06 #startmeeting releaseteam 15:31:07 Meeting started Wed Jul 12 15:31:06 2017 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:31:08 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:31:11 The meeting name has been set to 'releaseteam' 15:31:14 dhellmann, dims: o/ 15:31:17 o/ 15:31:21 fungi : o/ 15:31:23 Let's try to fit in 30min 15:31:35 Ping list: dims, fungi, tonyb, stevemar, lbragstad 15:31:51 although the unusual time is likely to mess up with attendance today 15:32:08 #topic Organize next week work 15:32:23 So I'm traveling to Asia all week, being in planes every other day 15:32:31 which will mess up with my availability to do things 15:32:39 I'll be around 15:32:50 I can keep an eye on library releases 15:32:52 We have a number of tasks noted on the tracking doc 15:33:10 I think you can probably cover for all of them ? 15:33:26 * dhellmann looks 15:33:28 oh, right. the meeting moved for this week 15:33:35 I could probably do the two patches 15:34:04 yeah, I can do those 15:34:19 the others, I mean 15:34:31 OK, let's do that 15:34:43 you could do the patches this week, really 15:34:45 Any question re: next week ? 15:34:49 o/ 15:34:54 yes, will try to :) 15:35:24 oh, and I think there were 2 patches before because I messed it up that time but they're the same file so you only need 1 15:35:31 ok 15:35:45 #topic Prepare to force releases for: instack and glance-store 15:35:54 We have two non-client libs that haven't released in Pike yet 15:36:05 For which we may have to force a release on master HEAD 15:36:17 as mentioned in the last countdown email 15:36:23 (I will repeat it again this week) 15:36:23 I'm surprised by instack 15:36:31 Might be a mismatch 15:36:38 yeah 15:36:56 All I know is they have an empty file in openstack/releases deliverables/pike 15:37:00 o/ sorry was afk 15:37:27 ttx: maybe talk to EmilienM about it? 15:37:41 dhellmann: yeah, although my overlap with him is limited those days 15:37:43 I assume the glance-store situation is lack of team members watching 15:37:49 so better if you or dims ask it 15:37:51 ok, I'll try to raise him 15:38:10 guess we could ping a Glance team member. Or flaper87 15:38:28 (re: glance-store Pike release before next week deadline) 15:38:30 or jokke_ 15:38:59 Keep me posted if the situation changes, so taht I don't shame them in tomorrow's relkease countdown email 15:39:15 ok 15:39:23 #topic Blurb to add to the countdown email about "Please complete doc migration work" 15:39:24 hello 15:39:33 #undo 15:39:34 Removing item from minutes: #topic Blurb to add to the countdown email about "Please complete doc migration work" 15:39:49 hi, EmilienM, we were just talking about the fact that instack hasn't released yet this cycle, and last week is the last chance to do so 15:39:56 EmilienM: instack next week 15:40:03 I'm doing it this week 15:40:07 ok, great 15:40:09 EmilienM : great, thanks 15:40:12 even today in fact 15:40:25 I also need to check with my team - instack is deprecated and we plan to remove it 15:40:32 thx for the reminder 15:40:55 very little has changed in glance_store (http://stackalytics.com/?module=glance_store&metric=commits), but definitely enough for a fresh cut 15:41:02 #topic Blurb to add to the countdown email about "Please complete doc migration work" 15:41:21 dhellmann: you mentioned that I should talk about that in next countdown email 15:41:33 If you have a paragraph I could add, I'll take it 15:41:47 I suspect the situation evolves contanstly :) 15:41:48 ok, I'll send you something 15:41:51 constantly 15:42:15 we decided to send a separate email to point out some of the repos that haven't been started, so we may not need it in the release email 15:42:27 I'll likely send the email at the end of my day on Thursday (off Friday) 15:42:43 ok, just let me know if you want me to mention anything about it 15:42:52 ok 15:42:53 #topic Queens Release management PTL candidates ? 15:43:21 Elections are coming up, I'm fine rotating if anyone feels up to take the hat 15:43:35 "feels like taking the hat" sounds better 15:43:58 I anticipate needing time to continue the docs work, so I won't be running, but I'll still be on the team 15:44:32 ttx : dhellmann : i am still trying to figure out how much workload will be on the internal side for new employer.. 15:44:37 heh. pass the hat 15:44:48 I'm fine doing it again. I think dims is busy enough and may have to cover for requirements if nobody shows up there :P 15:45:04 y, requirements i can handle :) 15:45:06 ok 15:45:31 OK, let's say I'll do it for Queens, with an eye on passing the baton for R 15:45:55 (assuming there are no other candidates) 15:46:00 smcginnis any interest in the release work? 15:46:12 * dhellmann watches for a dark horse candidate 15:46:29 dims: I'm game. 15:46:48 smcginnis: aren't you knee-deep in cinder ? 15:46:54 cool smcginnis ! 15:47:28 maybe he wants to pass the hat too 15:47:36 ttx: The water level comes and goes. It's manageable. 15:47:45 fungi: ;) 15:47:50 By all means if you feel like you can cover it all, I'm more than happy to help you in the job 15:48:17 It's not as if dhellmanna nd me would go anywhere 15:48:23 and dims 15:48:39 I never intended to be Cinder PTL as long as I have been, but it's not too bad until someone else steps up. 15:48:57 ++ smcginnis 15:49:10 sure, we'd be here to support 15:49:11 Job is mostly about sending reminders according to the process, holding the meetings, and then take up the work that nobody else takes 15:49:32 Not too scary. 15:49:39 (and of course some release request reveiwing) 15:50:14 Even less scary knowing that dhellmann, dims and myself will be very much around. Actually more available having someone holding the PTLship 15:51:22 ++ ttx 15:51:29 And teh more people know the process the better 15:51:39 Yeah, seems like there would be good support available. 15:51:55 plus, we wrote instructions! 15:52:08 Either way, I'd definitely like to be more involved in the process to be able to help more. 15:52:20 ever evolving instructions 15:52:25 dhellmann: Documentation?! Amazing. :) 15:52:32 dhellmann has automated all the stuff too! :) 15:52:48 smcginnis : yep, see the process.rst file in the releases repo 15:52:51 which we have a probable update to we can discuss in #openstack-release once the meeting wraps 15:52:54 PROCESS.rst 15:53:07 yes, I forgot it's a shouty filename 15:53:11 :) 15:53:19 because it's a shouty PROCESS 15:53:19 #link http://git.openstack.org/cgit/openstack/releases/tree/PROCESS.rst 15:53:32 perhaps it's a fortran process 15:53:38 I was typing very hard that day. 15:53:41 #topic Open discussion 15:54:43 safe travels ttx 15:55:00 smcginnis: noticed that the `tox -e aclmanager -- groups post_release ...` step seems to have been missed for ocata 15:55:11 smcginnis : seriously, take a look through the file and let us know if there are any questions 15:55:27 at least according to http://git.openstack.org/cgit/openstack/releases/tree/PROCESS.rst#n299 that should have put the gerrit groups right for stable branch maintainers 15:55:28 hmm 15:55:39 fungi: I just run the prerelease step 15:55:43 dhellmann: Will do, I have it on my list to actually focus some time on this afternoon now. 15:55:51 for all repos, or just cinder? (I saw the comment in #openstack-release) 15:55:57 ttx: oh, so that's a stable maint task? 15:56:11 dhellmann: cinder looks consistent with, e.g., nova 15:56:13 well, it might have been the previous PTL's responsibility 15:56:17 heh 15:56:25 that slacker couldn't wait to be done with the release 15:56:30 Hah 15:56:32 aclmanager sets the members of the $project-release-branch group in gerrit 15:57:04 yeah, https://review.openstack.org/#/admin/groups/nova-release-branch for example 15:57:06 Post-release that group needs to contain $project-stable-maint 15:57:16 still just the release managers and nova-release in therwe 15:57:21 Pre-release that group needs to contain $project-release 15:57:25 We are at pre-release stage now 15:57:27 so they're the only ones allowed to approve stable/ocata changes for now 15:57:33 Oh 15:57:34 ttx: this is for the ocata branch 15:57:39 That's because we need to approve... 15:57:43 https://review.openstack.org/482951 15:57:45 first 15:57:55 I did both steps at the same time 15:57:56 yep, i saw that show up in my review queue today and have started looking at it 15:58:01 aha 15:58:02 aha! race condition ;) 15:58:15 so yes we should approve that ASAP 15:58:19 Isn't that supposed to flip before the next release gets going too far? 15:58:21 so it's only been broken for a few hours. mystery solved 15:58:41 smcginnis: actually that group is supposed to be used only for stable/pike 15:58:54 https://review.openstack.org/482951 swwitches it to stable/pike 15:59:02 but that hasn't merged yet 15:59:11 and yet I updated the group members 15:59:16 was just proposed earlier today 15:59:17 ttx: So as soon as Ocata was final, we switch to stable/pike. In preparation for the next release even though it doesn't exist yet? 15:59:33 let's switch to openstack-release 15:59:36 smcginnis: yep, gerrit is fine having acls that refer to nonexistent refs 15:59:39 htere is another meeting starting now here 15:59:47 thanks ttx! 15:59:49 do we have that step out of order in the process? 15:59:49 this needs a rather lengthy explanation 15:59:53 no 16:00:01 #endmeeting