14:01:26 #startmeeting releaseteam 14:01:27 Meeting started Fri Aug 26 14:01:26 2016 UTC and is due to finish in 60 minutes. The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:28 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:30 The meeting name has been set to 'releaseteam' 14:01:39 courtesy ping: ttx, dims, fungi 14:02:00 thanks 14:02:34 with ttx at the ops summit I don't know if we'll see him today 14:02:56 #topic automation status 14:03:41 i went ahead and self-approved the launchpadlib changes a few minutes ago... simply wasn't able to get any core reviewers interested in looking them over 14:03:49 ok 14:04:03 I'll make a note to run some tests again next week then 14:04:11 #link https://review.openstack.org/356665 and its parent change 14:04:59 i'll give you a heads up once they merge and i confirm the file/package are peesent on the job node 14:05:01 present 14:05:24 sounds good. I'm not likely to get to the tests today, so there's no rush 14:05:31 I've put it on the task list for next week 14:05:41 cool 14:05:45 anything else on the automation? 14:05:56 as for the remaining documentation changes, haven't finished those yet. been a hectic week 14:06:35 and no, nothing else on my end 14:06:36 yeah, I can imagine 14:06:39 k 14:06:41 #topic release countdown checkup 14:07:04 I had planned to ask about whether we're ready to branch non-client libs, but I think I'll just send a reminder email and create the branches on monday 14:07:46 I've copied our tasks from http://git.openstack.org/cgit/openstack/releases/tree/PROCESS.rst into the tracking etherpad on the weeks where I think they need to go 14:07:51 it would be good to have some confirmation of that 14:08:15 I'll get ttx and dims to look over it, but if you have a spare minute fungi your input on the timing would be good too 14:08:36 sure, having a look now 14:09:10 and I've set up a release tracking dashboard like we used last cycle 14:09:11 #link https://docs.google.com/spreadsheets/d/1wy_YgMQ1MowE9Loztn6QAsMGOfVkVsqIQVdcIdrHAtI/edit#gid=2082157708 14:09:33 hrm, not finding the etherpad easily in my browser history 14:09:39 #link https://etherpad.openstack.org/p/newton-relmgt-tracking 14:09:42 thanks 14:09:49 sorry, I should have posted that at the start because that's where the agenda is 14:10:04 yep, you usually do... i was about to go look in old meeting logs 14:10:51 so the copied content is in the r-5 section? 14:11:12 it's under the "tasks" items on r-5 through the end of the cycle, in the week where I think we need to do it 14:11:21 ahh, yep, just realized that 14:13:31 all of those look good to me 14:13:38 * fungi is a slow reader 14:13:45 good, thanks 14:13:59 i can't think of anything that's obviously missing there 14:14:17 I'm sure we'll uncover anything not obvious :-) 14:14:45 also, i'm not going to be around for week r+1 (the week after the release) but expect that won't be too busy 14:15:01 I need to check with ttx to make sure the gerrit acl work is done -- I think we're just waiting to make sure all of the teams have the right members in their release groups 14:15:15 fungi : noted 14:15:38 also most of the infra team will be sequestered during week r-2, but i'll still be around 14:15:40 * dhellmann needs to plan some pto in there too 14:16:04 sequestered? mid-cycle? 14:16:11 "mid" sure ;) 14:16:26 i've been referring to it as a "late-cycle sprint" 14:16:33 heh 14:17:12 it's a joint thing with the qa team, near frankfurt, so most of them will be busy and on european time 14:17:36 but i'm sitting this one out and will be around normal times if something comes up 14:18:09 ok, good to know, thanks 14:18:31 #topic summit space needs 14:18:42 I went ahead and asked for a work session so we can schedule the time to talk about wrapping up the automation 14:19:03 I also asked for a fishbowl, as a communication opportunity, but indicated that if we were out of space for them we could give that up 14:19:22 and I asked for a meetup room on Friday, since that's usually our most productive time 14:19:23 makes sense 14:19:50 I figured putting the work session in our "track" would let you make full use of your allocation for infra topics 14:20:28 appreciated. this time we're going mostly with workrooms i think 14:20:45 makes sense 14:20:48 we'll see how the allocations shake out anyway 14:21:14 right, I'm not sure how many rooms there even ar 14:21:15 are 14:21:28 ok, that's all I had for the formal agenda 14:21:32 #topic open discussion 14:21:48 is there anything else we need to be talking about at this point in the schedule? 14:22:33 i've got nothing 14:22:45 k, let's close it then 14:22:48 fungi : thanks! 14:22:53 any time! 14:22:57 #endmeeting