14:00:17 #startmeeting releaseteam 14:00:18 Meeting started Fri Aug 19 14:00:17 2016 UTC and is due to finish in 60 minutes. The chair is dhellmann. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:21 The meeting name has been set to 'releaseteam' 14:00:48 courtesy ping: ttx, dims, tonyb, stevemar, fungi 14:00:56 hey-o 14:01:15 howdy 14:01:39 I see ttx left his regrets in a PM 14:01:48 so, looks like it's just us tody 14:01:58 automation status 14:02:05 he doesn't know what he's missing 14:02:07 oops 14:02:11 #topic automation status 14:02:24 given how little sleep I got last night, this should be an interesting meeting 14:02:29 hah 14:02:48 fungi: what's the word on the launchpad lib setup? I know there have been some fires to fight since last week 14:03:08 #link https://review.openstack.org/356666 Add LP creds and launchpadlib to signing job node 14:03:22 \o/ 14:03:26 that and its dependency ought to get you access to tweak bugs at release 14:03:44 ok, nice 14:03:58 #link https://review.openstack.org/353692 Set up HTTPS for releases.openstack.org site 14:04:25 that's a dependency for the documentation of the key fingerprint, which i haven't finished writing yet 14:05:12 i don't think i have any other updates 14:05:26 and yeah, fires 14:05:40 iirc, the tagging part of the job did work but it didn't test updating requirements by submitting a patch, so we have one more aspect to test after the launchpad stuff is working 14:05:59 sounds right 14:06:04 given where we are in the release cycle, I'm a bit reluctant to start changing the release process 14:06:09 we have time to think about that, though 14:06:57 makes sense 14:07:12 when it works for tagging and launchpad, we could turn it on for the server projects, since we'll be in a freeze for libraries and requirements 14:07:22 it's taken me longer to get to some of this than i anticipated 14:07:31 still getting the hang of this ptl thing 14:07:44 heh, yeah, lots of little details that constantly change 14:08:28 it seems like we might make it for server projects this cycle, and we're pretty likely to make it for first milestone next cycle, so a bit later than hoped but still not bad 14:08:37 we're making progress on it, so I'm happy 14:09:00 moving on 14:09:01 #topic availability for tagging during lib freeze next week 14:09:22 ttx and I will both be on the road at openstack east next week 14:09:40 dhellmann: i'll join you on wednesday there :) 14:09:58 stevemar : nice! 14:10:07 I'll be actively monitoring requests for releases, but I expect delays 14:10:34 I was hoping to catch up with dims on whether he was coming. I'll get in touch after the meeting 14:10:57 #topic summit space needs 14:11:06 we typically have 1 fishbowl session and 1 meetup session for the release team 14:11:25 I think the meetup session is our more productive time, and the fishbowl is our chance to talk about major new plans 14:11:41 I don't think we have any major plans for ocata, so I'm not sure we need to have that session 14:11:43 thoughts? 14:12:23 sounds fine--expect me to attend 14:12:24 how was the attendance at meetup and fb last summit? 14:12:59 the meetup had a mix of requirements and release folks. all the right people were in the room at some point, though maybe not the the whole time. 14:13:05 it went well, so I definitely want to keep that 14:13:10 ++ 14:13:20 it's our chance to put together the long planning list we work from for the entire cycle 14:13:28 yeah, for meetup overlap with infra, just send word when/where i'm needed 14:13:41 the fishbowl was well-attended, but not by many liaisons or ptls, irrc 14:13:43 worked out pretty well in austin anyway 14:14:15 fungi : yeah, we're all only going to have friday afternoon so we'll have to coordinate more tightly, either start with or finish with anything we need to overlap on 14:14:18 the fishbowl had a lot of cross-project and horizontal team folks 14:14:28 yeah, that's true 14:14:42 but yeah, not much representation from the vertical teams 14:15:09 which, unforunately, is where most of the communication breakdown happens too 14:15:35 I'll run it past ttx and dims to see what they think, we have time to decide. 14:15:44 it might be best to keep it and keep trying to communicate that way 14:16:17 maybe some more creative scheduling can drive more representation into the room 14:16:25 like overlap with all boring sessions ;) 14:16:48 fungi : would it make sense to ask for a work session to handle any infra overlap? it might be easier to schedule that way. 14:17:15 i'd be fine with that. happy to put it as an infra session too if desired 14:17:35 i agree it would make coordination easier 14:17:57 ok, let's plan on doing that one way or the other to ensure we have time to wrap things up 14:18:04 wfm 14:18:57 cool 14:18:58 #topic proposed ocata schedule 14:19:03 #link https://review.openstack.org/#/c/357214 14:19:09 that's up as an fyi, dates are not firm yet 14:20:06 tonyb pointed out that I started from the wrong week, so I need to look at that again 14:20:14 the *end* dates are closer to right than the start dates 14:20:43 #topic open discussion 14:20:47 that's all I had for this week 14:20:57 has anything else come up that we need to cover? 14:21:44 ok, taking silence for "no", I think we can call the meeting 14:21:54 thank you fungi & stevemar 14:22:14 thanks, i'm just here spectating :) 14:22:32 heh 14:22:44 get back to work, then! 14:22:49 #endmeeting