15:00:13 #startmeeting releaseteam 15:00:14 Meeting started Fri May 19 15:00:13 2017 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:18 The meeting name has been set to 'releaseteam' 15:00:19 Ping list: dhellmann, dims, fungi, tonyb, stevemar, lbragstad 15:00:30 o/ 15:00:37 * dhellmann is on another call, will be here shortly 15:00:47 hey there 15:01:09 #link https://etherpad.openstack.org/p/pike-relmgt-tracking 15:01:12 Agenda ^ 15:01:27 scroll down to R-15 15:01:46 #topic Boston Forum outcomes 15:02:15 First, was great seeing you all last week. Any lesson / thing we need to do from what we learnt at Summit ? 15:02:56 we didn't have much related to the release team last week, which let me focus on some other themes 15:03:13 I noted brainstorming binary releases options, but taht's well under way 15:03:26 yeah, that thread got out of control pretty quickly 15:03:30 o/ 15:03:43 yeah, i felt like the new format was a great opportunity for efforts like release management to give feedback rather than receive it 15:04:10 Still think we need to adapt to that binary-friendly world, but I would say we need to take the time 15:04:12 sessions at the design summit tended to be the other way around 15:04:17 (i.e. not now) 15:04:22 did we get any bites from folks on the onboarding front? (sorry i mssed that) 15:04:39 dims: that session is when we connected with Caleb 15:05:00 ack on binary-friendly world ttx, golang deliverables will need them too 15:05:04 so that was useful, at least for that. Otherwise nobody joined the team as a result of that session yet 15:05:04 ttx : ah cool 15:05:07 the joint onboarding was nice, but yeah most interest seemed to be cross-community outreach 15:05:52 ok, if nothing else, let's move on to next topic 15:05:52 true 15:06:02 #topic Follow-up with TC on lack of goals answers 15:06:26 A large number of teams failed to fill their goals answers by the deadline 15:06:40 Not sure what we should do at relmgt team level about that, beyond just raising the miss 15:06:56 So the next step seems to live at TC level 15:07:01 yeah, I see that as a TC project, so we should address it there 15:07:13 yep, not enough carrots or sticks... 15:07:42 It seems to point to the process friction 15:08:00 more than to any specific work being too hard to accomplish 15:08:10 i.e. the same teams missed updating both goals 15:08:43 could be 15:08:53 anyway, that means we need to discuss it at TC level. Raise a ML thread ? Wait for office hours to be set up ? 15:09:32 some of the teams are the ones that are regularly less engaged; some have drastically reduced staff now 15:10:01 maybe a ML thread to get the TC discussion started? 15:10:31 ok, I can do that -- although my absence at end of next week means you might need to step in that thread 15:10:41 ok 15:10:55 d'oh, yep i need to update the open goals for infra to say they don't apply i guess 15:11:36 #action ttx to raise thread next week on goals answers 15:11:42 i wonder if lack of updates are mostly from teams who forget they still need to do that when the goals aren't applicable to them 15:11:56 #topic Need for a TC resolution stating something to the effect that projects that wish to be considered part of the openstack release should have their deliverables listed on releases.o.o 15:11:58 it's likely true for some 15:12:00 mouthful 15:12:23 I was wondering if we still want to do that formalkly, or just assume that's the case 15:12:31 ttx : which teams are missing? 15:12:37 after all we define what "the release" is 15:12:52 I think fuel was missing at one point, but I don't know if that's even an issue any more 15:13:02 most of the others were "independent" projects, I thought 15:13:21 We have enough things in the fire at the moment so we might want to move that to backlog 15:13:24 which aren't part of the release anyway, since they aren't on the cycle 15:13:28 yeah 15:13:36 I'm much more interested in resolving the goals process issues 15:13:46 #info answer is no pressing need 15:14:00 OK, I'll update the plan quickly 15:14:48 #topic Heads-up on ttx's availability around milestones 15:15:17 So... I committed to a number of travels and realized a bit after the fact that those were not great weeks for me to travel 15:15:44 Like on pike-2 week I'll be traveling Tue-Fri 15:16:06 Then on pike-3 week I'll be traveling Mon-Wed 15:16:17 are you trying to one-up me? :-) 15:16:20 and be away all the week before 15:16:40 Those are weeks where I work, but I know that my productivity will be limited 15:16:56 Especially those weeks around Pike-3 I'll be in China 15:16:57 i'll be around both weeks pike-2 milestone and pike-3 milestone as of this moment ttx dhellmann 15:17:11 so I have no idea how well that will work 15:17:18 ah openstack china day 15:17:19 (probably poorly) 15:17:22 ttx: I think dims and I can handle reviews. Will you be able to handle the reminder emails, or should we do that? 15:17:33 let me see 15:17:50 I can do all reminder emails for pike-2, no problem 15:18:21 The one on R-6 week, can probably get it done as well. 15:18:25 fyi, i am travelling last 3 weeks of june 15:18:37 I mean, I can still get work done, but won't be as much on IRC 15:18:58 ok 15:19:24 dims: can you fill in your availability in "Team availability notes" in https://etherpad.openstack.org/p/pike-relmgt-tracking ? 15:19:35 dhellmann: any planned absence between now and pike-3 ? 15:20:01 I have no plans to travel for a while. I might end up doing a short vacation trip, but nothing big until after the release. 15:20:31 at least nothing right now, but I'll let you know if that changes 15:20:52 ok, looks like there will always be at least two of us on deck 15:21:42 I'll try to be more careful in the future 15:22:20 #topic Skip meeting next week ? 15:22:36 I'll be off on Thursday-Friday next week (holiday) 15:22:55 so I was thinking we should skip meeting, and discuss on channel ad-hoc 15:23:12 yeah, we don't have a lot going on so that seems like a good idea 15:23:51 ++ 15:23:58 I'll try to get my pike-2 stuff done next week(s). It's likely that I'll have to defer the Storyboard stuff to Pike-3 15:24:19 I have some of the remaining python 3 work queued up for review 15:24:25 fungi, if you could put https://review.openstack.org/465739 on your list that would help 15:24:27 lots of things on top of that pile 15:24:39 #topic Open discussion 15:24:41 once that's done, I'll look at the branching support for devstack 15:24:58 dhellmann: starred, thanks for the heads up 15:25:56 anything else ? 15:26:14 nothing from me 15:26:26 Alright then, have a great weekend 15:26:31 #endmeeting