08:02:16 #startmeeting ptl_sync 08:02:17 Meeting started Tue Sep 23 08:02:16 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:02:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:02:20 #topic Nova 08:02:20 The meeting name has been set to 'ptl_sync' 08:02:25 Hi 08:02:37 ohai 08:02:42 #link https://launchpad.net/nova/+milestone/juno-rc1 08:02:50 Yeah, that 08:02:58 So... where to start? 08:03:03 I'm a bit worried about the unassigned bugs 08:03:16 The curve is not really going down at http://old-wiki.openstack.org/rc/ 08:03:28 mikal: yeah, had that issue a bit ago 08:03:42 Huh, no worse than many other projects though 08:03:44 ttx: so people are adding all sorts they find important-ish, rather than blockers 08:04:11 Yeah, I was trying to review things associated with those bugs and ended up lost spending the last two days fixing a security vulnerability that was release critical 08:04:16 johnthetubaguy: it's tricky because damn LP doesn't prevent anyone from doing that 08:04:18 Because the proposed fix set off my bogo filter 08:04:26 mikal: some of those critical gate bugs are just not likely to get fixed in time, some people were digging 08:04:41 ttx: yeah 08:04:46 Yeah, I feel that critical gate != critical release 08:04:55 They're important 08:05:00 rigth, so they can stay criotical but not be release blockers 08:05:00 Just not important to the release per se 08:05:04 Agreed 08:05:20 just remove the rc1 tag. If they get fixed, all th better, we'll take them 08:05:28 mikal: been chasing some nasty xenapi stabiity bugs that would have been embarrassing not to fix myself 08:05:34 Heh 08:05:35 but if nobody is assigned to them at this point, no point in keeping them in list 08:05:45 ttx: when are we hoping to tag, before thursday I guess? 08:05:47 johnthetubaguy: can you take a pass at untargetting gate bugs which aren't release critical today? 08:06:02 I thought we didn't tag until the rc bug list got to zero? 08:06:08 mikal: yeah, if we want to start drawing up the final list 08:06:09 johnthetubaguy: before Tuesday next week. 08:06:19 "end of month" 08:06:24 ttx: gotcha 08:06:38 but yeah, at least trying this week would be nice 08:07:02 mikal: thing is, people were kinda thinking, we just take the criticals as blockers, the rest are just an "aim" 08:07:03 mikal, johnthetubaguy: would you say the list contains all the true known blockers at this point ? 08:07:37 ttx: all that I am aware of 08:07:42 ttx: "know" is a bit caveat, but yes I think so (minus security ones) 08:07:44 There hasn't been a lot of conversation about it though 08:07:53 The thread on -dev was pretty quiet 08:08:00 Which surprised me to be honest 08:08:43 mikal: I think people just lobbed the tags on 08:08:54 well, target I mean 08:08:54 johnthetubaguy: yeah, that's what I figured in the end 08:08:55 So yeah, as far as bug list is concerned, I would trim it to assigned bugs only, and those that have some chance to make it before end of month 08:09:08 ttx: cools, I can do that 08:09:21 "Dropping as unassigned" seems like a reasonable comment to leave on them 08:09:27 johnthetubaguy: I can do that if you want me to be the bad guy 08:09:28 Would be good to get the security fix worked on though 08:09:37 since fixing before release is always better than after 08:09:40 You're thinking of 1369627? 08:09:46 but we shouldn't block on that 08:09:48 For the security fix? 08:10:11 no. Is 1369627 a security thing? 08:10:12 mikal: yeah, I don't mind, security stuff I probably just need to find people to work on them 08:10:15 Yes, yes it is 08:10:20 There's another I haven't noticed yet? 08:10:37 We're fixing 1369627 by reverting three patches 08:10:46 One done, one approved and in gate, the other needing review 08:10:52 mikal: see pm 08:11:03 johnthetubaguy: if you could review https://review.openstack.org/#/c/123072/ that would be cool 08:11:21 Hmm, you should set "Public security" if it's a security bug 08:11:29 otherwise it will never enter the OSSA realm 08:11:53 although... it's juno-specific ? 08:11:53 Ahhh, I see 08:12:07 Yeah, we've never "released" the bad code 08:12:16 On the other one, that sounds like something we could ask Vishy to look at 08:12:17 so in that case we just need to fix it prerelease 08:12:23 He's been playing there in the last couple of weeks 08:12:34 no need to get the OSSA team on it, no advisory needed 08:12:40 Yeah, I don't know of any CD'ers running rbd, so we should be ok with those guys 08:12:44 mikal: continuous deployment is a bit odd though 08:12:45 as log as we fix it for rc1 08:13:35 For the other one I am emailing Vishy now to ask if he can help 08:13:42 OK, let's trim that list and start burning all targets down. We'll do another checkpoint on Thursday 08:14:03 mikal: did you release a final novaclient ? 08:14:24 Yes, I did 08:14:37 Oh, can we add johnthetubaguy to whatever group gives him access to the security bugs if we havne't already? 08:14:44 That makes sense from his LP wrangling role 08:14:49 mikal: I have access 08:14:58 Oh, cool 08:15:23 mikal: just ended up focusing more on blueprints really 08:15:31 johnthetubaguy: yeah, that's fair 08:15:38 Just at the moment it makes sense to get you access if you don't alrady 08:15:42 Which you do 08:15:42 So ignore me 08:15:54 lol, no problem 08:16:09 so the list, I don't mind trying to trim that after the meeting 08:16:16 ok, so the client looks fine now 08:16:18 That would be cool, thanks 08:16:20 at least all unassigned ones that seem unlikely to make it 08:16:31 questions ? 08:16:47 Not a question, but I am unsure if I will make the release meeting 08:16:50 I am hoping to 08:17:01 But it depends on the school thing which is making me miss the TC meeting ending on time 08:17:04 what are the summit deadlines again, session wise? 08:17:05 So we shall see... 08:17:29 mikal: as far as design summit is concerned, you would get 18 scheduled sessions and a full-day of contributors meetup (instead of 27 sessions) 08:17:39 ttx: ok 08:18:00 johnthetubaguy: I think because we're not using the selection web site for sessions we're a bit more flexible with selection deadlines? 08:18:03 I guess its all decided post PTL election 08:18:05 Or am I confused? 08:18:14 Yeah, definitely new PTL territory 08:18:20 But we can prime the pump for them, so to speak 08:18:41 we just need a schedule 1 or 2 weeks before the thing starts 08:19:00 cools, that makes sense 08:19:05 I am just thinking about specs 08:19:06 but given it's collaboratively discussed now, that may mean start earlier 08:19:27 Well, we already have a brain storming etherpad 08:19:28 ttx: true, give people time to chime in 08:19:33 We just need to start talking about it in meetings more 08:19:43 But I think release should take most of our meeting time at the moment 08:19:45 mikal: ++ 08:19:46 For the next week at least 08:19:58 until RC1 is done, just talk release and RC bugs 08:20:17 after RC1 is done we'll add bugs much more selectively 08:20:20 Yeah, let's not confuse people 08:20:21 if needed 08:20:28 Although we promised to open kilo specs next week 08:20:30 so it's easier to switch minds to kilo 08:20:34 So I need to remember to not forget that as well 08:20:42 good good, sounds perfect 08:20:54 just wanted to make sure we are all on the same page 08:21:02 So yeah, I think we're done here? 08:21:04 Yeah, I think we are 08:21:06 Which is good 08:21:07 yes we are 08:21:11 ttyl! 08:21:19 thanks all 08:21:20 Cool, well thank for both of your time yet again 11:44:35 eglynn: ready when you are 11:44:43 ttx: knock, knock :) ... ready when you are 11:44:46 #topic Ceilometer 11:44:54 #link https://launchpad.net/ceilometer/+milestone/juno-rc1 11:45:14 so fair progress in landing bug fixes 11:45:20 6 bugs left, we might be able to tag before end of week? 11:45:28 well, there are 2 that I'd like to wait on especially 11:45:35 https://bugs.launchpad.net/bugs/1309555 11:45:41 https://bugs.launchpad.net/bugs/1357869 11:46:01 the first has an incomplete fix proposed, needs more testing and a more complete fix 11:46:02 ok, we'll see how it goes 11:46:31 for the second, I've a simple config workaround to fall back on but I'm also experimenting with a more complete fix 11:46:38 OK... On the client release side you did a 1.0.11 11:46:43 OK, so you're preference was EoW for RC1? 11:46:54 yep, I cut 1.0.11 on Monday 11:47:09 slightly delayed by lag in the gate getting the last couple patches merged 11:47:14 My preference is by EoW yes, and before next Tuesday otherwise 11:47:28 #link https://pypi.python.org/pypi/python-ceilometerclient/1.0.11 11:47:33 OK, got it 11:48:24 OK, you seem to be in good shape 11:48:35 I'll sync again on Thursday and see if we can do RC1 before eow 11:48:44 cool, sounds like a plan :) 11:49:28 As far as summit is concerned, you would get 5-6 scheduled sessions, and a full day of contributors meetup 11:49:50 (compare to 10 scheduled sessions in ATL) 11:50:56 OK, obviously I'd prefer 6 to 5 if possible 11:51:26 yeah, my current layout includes 6, but i'm waiting on feedback from some programs 11:51:26 I'd like to accomodate the Monasca folks with a design session on the ceilo track if poss 11:51:56 (I've been chatting with RolandH about opportunities for collaboration) 11:52:16 ok that works 11:52:34 anything to discuss at meeting . Any red flag wrt release ? 11:52:46 nope, no red falg from me 11:52:52 *flags 11:53:37 OK then, talk to you later! 11:53:44 cool, laters 12:14:10 dhellmann: ready when you are 12:14:32 ttx: here 12:14:35 #topic Oslo 12:14:46 Are we all set release-wise ? 12:15:09 yes, we should be set 12:15:18 https://launchpad.net/oslo/+milestone/next-juno 12:15:21 we had one patch release of oslo.db to help stabilize the nova gate, but that's it 12:15:35 This should in theory show all FixReleased at some point 12:15:46 (if we are indeed done) 12:16:06 we never ran the script against the incubator. I can update those by hand. The others I'll move to kilo. 12:16:20 I was holding onto the idea of a pbr release, but I think at this point we should wait for the other releases to finish. 12:16:45 dhellmann: for oslo-incubator, maybe rename next-juno to 2014.2 12:16:51 ok 12:17:10 since that's what we tagged 12:17:39 A few fixes were merged after that in master and should not get FixReleased, though 12:18:05 we count master for the incubator as released, since the important tracking is when the merge happens in the apps 12:18:12 (bug 1372177) 12:18:13 at least that's how I've been treating it 12:18:55 dhellmann: hmm, but those fixes are post-2014.2 tag 12:19:10 so they should not appear FixReleased in 2014.2 12:19:29 ok, that one isn't targeted to the milestone yet, so I'll put it in a kilo milestone 12:20:09 the others were without a bug ref 12:20:21 ? 12:20:23 so that's the only one you could accidentally include 12:20:57 dhellmann: let me explain 12:21:23 if you run the script that turns FixCommitted bugs into FixReleased, you need to do it when you tag, otherwise you may catch bugs that were fixed after the tag ifs applied 12:21:40 here I just checked the merges that happened after the tag to make sure we don't accidentally indlude them in 2104.2 12:21:58 oh, yeah, I was going to just update all of those bugs by hand to avoid that 12:21:59 There are 3 of them 12:22:20 well, actually, 4 12:22:37 https://review.openstack.org/#/c/122377/ references no bug 12:22:54 https://review.openstack.org/#/c/123017/ references 1372177 12:23:19 https://review.openstack.org/#/c/115213/ references no bug 12:23:33 * dhellmann nods 12:24:07 https://review.openstack.org/#/c/121305/ references related bug 1368910 12:24:29 anyway, just me and my damn accuracy :) 12:24:38 I will make sure those bugs are targeted with kilo 12:24:43 s/with/to 12:25:12 I guess if I do that, I can use the script to update the bug settings instead of doing it by hand 12:25:32 so, on https://launchpad.net/oslo/+milestone/next-juno there are still oslo.concurrency PBR taskflow and oslo.vmware things 12:26:02 Are those all still waiting for a tag ? 12:26:16 oh, we didn't do a final release of those, that should all move to kilo, too 12:26:30 I'll spend the morning cleaning this up. I should have looked at it yesterday. 12:26:35 we won't do a final release of those ? 12:26:57 wait, hang on, we did a release of concurrency 12:27:20 oh, no, that's serialization -- I keep mixing those up 12:27:30 ETOOMANYLIBS 12:27:40 no, we had a few libs that were not quite ready and weren't going to be adopted, so we focused on fixing up the ones in use 12:27:45 I will move all of the unfinished work to kilo 12:27:52 dhellmann: OK, so once you are done with the juno cleanup let me know, i'll doublecheck and we can close Juno for good 12:27:55 yeah, seriously, we're up to something like 19 or 20 now 12:28:02 ok, sounds good 12:29:07 dhellmann: as far as design summit is concerned... I think we can preserve ~7 oslo scheduled slots 12:29:21 (down from 11 in ATL) 12:29:29 we should be able to make that work, esp. if we have pod space on friday 12:29:30 You would get a dedicated "pod" on the Friday 12:29:38 reading my mind :-) 12:29:47 and we can also discuss major issues on the cross-project day, if any 12:30:34 I don't want oslo to be seen as the driver for those things. We may have one or two, but I want the TC to really run those as "all of openstack" rather than funnelling them through oslo 12:30:50 oh sure, that's what I meant 12:31:08 ok 12:31:31 any release red flag on your side ? 12:32:29 anything to discuss at cross-project meeting today ? 12:32:31 I haven't heard anything. We looked into that keystoneclient issue on the stable branches, but it's going to have to be fixed in their client. 12:32:49 nothing this time around, I think 12:33:09 well, I need to figure out the timing to remind everyone to prioritize adoption of libraries early in kilo 12:33:10 dhellmann: ok, great! 12:33:24 they're probably not thinking about that yet, but I don't know if we'll have project meetings after the release is actually done? 12:33:33 dhellmann: if you have some time, you can help sdague and myself go through the requirements review 12:33:45 yeah, I was going to ask if there's anything you need help with 12:33:53 the more the merrier 12:33:58 aren't we locked down for requirements changes? 12:34:10 dhellmann: yes, that's why I'd like to clean up the slack there 12:34:18 oh, so -2 things? 12:34:23 -2 what can be, abandon some 12:34:26 ok 12:34:38 and discuss at release meeting today what still needs a final call 12:34:56 I triued to come up with a list for that and got confused by some 12:35:01 ok, I'll look at that after I clean up our bug tracker 12:35:34 ok, you will be able to find us on #openstack-dev 12:35:51 ok 14:00:21 jgriffith: ready when you are 14:06:36 ttx: ready 14:06:42 #topic Cinder 14:06:50 https://launchpad.net/cinder/+milestone/juno-rc1 14:07:03 Your curve is one of the few going down at http://old-wiki.openstack.org/rc/ 14:07:13 so you seem on a good trend 14:07:22 cool! 14:07:44 There is one unassigned security issue though that we should at least try to get in the release rather than after 14:07:54 (it's the one unassigned bug in the list) 14:08:06 you might want to privately get it assigned 14:08:09 ttx: ahh 14:08:17 yeah, there's a patch proposed 14:08:24 I can mark it assigned 14:08:39 You did release a client last week (1.1.0) and the global requirements bump is gating 14:08:51 so we are covered on that side 14:09:11 Yeah, I'll do one more client bump after RC cut 14:09:12 When do you think you can empty the list ? Sometimes this week ? 14:09:20 I think this week yes 14:09:26 most are in progress and doing "ok" 14:09:30 jgriffith: one more client bump after RC cut ? 14:09:41 We wanted to freeze the clients.. last Friday 14:09:43 I'd like to if it doesn't make people freak out 14:09:48 ahh... 14:09:52 hmm... 14:09:54 so unless you have some critical issue 14:09:59 so I have one issue 14:10:11 debug output was broken by all the i8n shenanigans 14:10:24 patch is on it's way through right now to fix 14:10:32 kinda of a big deal IMO 14:11:00 OK, I think it's fine to tag a new one, but maybe not bump the global requirements 14:11:11 ttx: oh.. for sure 14:11:13 just make sure everyone knows about it when you cut it 14:11:17 I'll avoid that at all costs 14:11:31 I will... in fact I'll send a note to dev today warning them if that helps 14:11:50 do you have a bug reference for that issue ? 14:11:55 I do.... 14:12:25 https://bugs.launchpad.net/python-cinderclient/+bug/1130730 14:12:27 and it landed 14:12:38 so I'll push today and send an email to everyone 14:12:38 #info New Cinder client expected soon (1.1.1 ?) to fix bug 1130730 14:12:47 ok 14:13:03 Any red flag release-wise ? Anything you'd like to discuss at meeting today ? 14:13:16 No red flags (as of yet) 14:13:29 and no, nothing I need to bring up at meeting 14:13:52 jgriffith: as far as summit goes, i'm still working on allocation but you should get 6-7 scheduled slots 14:13:59 + the half-day meetup 14:14:13 in case there is room for it, would you be interested in a full-day thing ? 14:14:32 ttx: always, but honestly I wouldn't rank us high priority for it 14:14:46 ttx: and I'd rather see more cross-project interaction from Cinder team 14:15:00 ttx: I'm realizing more and more that a lot of folks are really silo'd 14:15:07 would like to prompt some change there 14:15:21 ok. 14:15:41 Keep in mind I'm going to propose being very picky about session topics this time around 14:15:51 assuming my successor follows that plan 14:16:28 ok, talk to you later then! Hope we can cut RC1 later this week 14:16:35 sounds good 14:16:42 morganfainberg: ready when you are 14:16:43 I'll let you know if I think it's ready before Friday 14:17:01 ttx, o/ 14:17:24 #topic Keystone 14:17:35 https://launchpad.net/keystone/+milestone/juno-rc1 14:17:47 2 bugs left, looks like we should be able to cut this week 14:18:00 ttx, those are both addressed by the same fix, should gate today 14:18:13 OK, so I might be in touch soon :) 14:18:25 ttx, in fact, working with another core to get that reviewed right now as well :) 14:18:39 morganfainberg: on another note, we might want a keystonemiddleware tag to catch the latest security issue in a release 14:18:55 before we issue an advisory for it 14:18:57 ttx, Keystone client is also ready for 0.11.1 release fixing the bug in config 14:19:29 which bug ? 14:19:39 ttx, keystonemiddleware is planned to get a new tag/release as soon as https://gist.github.com/dolph/651c6a1748f69637abd0 those 4 reviews merge. 14:20:01 ttx, https://launchpad.net/python-keystoneclient/+milestone/0.11.1 14:20:14 the glance exploding one, #1272422 14:20:14 ah ok 14:20:18 erm 1372422 14:20:45 i will either need to have you push the tag or wait for dolphm today. 14:20:51 ok 14:20:52 i do not have permission to push tags. 14:21:07 ping me as needed 14:21:19 any other thing release-wise ? 14:21:35 ttx, anytime today would be good to get 0.11.1 out. 14:21:58 ttx, no i think that is it. looking forward to getting Keystone tagged (hopefully minimal gate fighting for that last blocker) 14:22:10 As far as summit goes, still working on allocation, but keystone could get 6-7 scheduled slots + a half-day meetup 14:22:26 ttx, that sounds about the same as last time, and fair. 14:22:28 (compared to 8 scheduled slotsin ATL) 14:22:40 ttx, right, the 1/2 day covers the extra. 14:22:54 morganfainberg: that's all I had 14:23:21 ttx, cool. sounds good and i'll def. ping you as soon as we have the middleware reviews ready. My goal is for all of them to be done today / tomorrow morning 14:23:46 ttx, i expect it's just going to be gate rechecks to get things through 14:24:03 ttx, same with keystone. 14:24:10 ok, I'll be a bit busy today so I may not be able to get back to you wrt: python-keystoneclient tag. 14:24:20 If still needed by tomorrow, I should be much more available then 14:24:43 david-lyle: ready when you are 14:24:49 morganfainberg: thx! 14:25:03 ttx, i'll ping dolphm if i see him. 14:25:04 ttx: ready 14:25:10 #topic Horizon 14:25:11 ttx, if not, will bug you tomorrow :) 14:25:21 https://launchpad.net/horizon/+milestone/juno-rc1 14:25:40 So... 44 opened RC1 bugs is way too much 14:26:02 yes, getting ready to prune that down 14:26:07 you need to cut down the list to release blcokers only. If anything else gets in in the mean time, taht's fine 14:26:32 but there is no way those 44 will get in and we still hit the release date :) 14:26:55 I think the list is actually about 4 for release blocking 14:27:20 at least that's what I've been tracking 14:27:21 Ideally we'd cut RC1 before end of week, worst case before end of month 14:27:45 my target was end of the week, unless something else comes up 14:27:45 ok, you can use a tag to track the nice-to-have 14:27:54 sure 14:28:18 we'll discuss the last depfreeze exceptions at the meeting today 14:28:25 ok 14:28:26 so that we can make the final call on them 14:28:59 any red flag wrt: release ? Or topic for the meeting today ? 14:29:38 no 14:29:56 As far as design summit goes, my initial allocation gives horizon 6 slots + the half-day of meetup 14:30:12 that sounds reasonable 14:30:17 in case there is room for it, could you be interested in a full day ? 14:31:10 I'm not sure we'll need a whole day if there is pod space available 14:31:26 ok. 14:31:54 david-lyle: that's all I had. Anything else ? 14:32:16 if no other teams speak up we do have some architecture work I'd like to get done there, but I think the number of participants may not warrant a whole room 14:32:57 want to make sure my recollection is correct, once RC1 is closed, master is Kilo 14:33:06 correct? 14:33:44 yes 14:33:55 also a heads up, due to translations, we'll likely have an RC2 just for that, barring other issues 14:34:45 I think the translation team is targeting end of month 14:35:59 that's all I have 14:36:10 david-lyle: it would be good to merge relatively-recent translations for RC1 anyway 14:36:12 but i agree 14:36:31 mestery: ready when you are, but you seem to have a conflict :) 14:36:48 ttx: Sorry, yes, in a neutron meeting. Can we push this a bit for today? Apologies. 14:36:54 sure 14:37:13 ttx: OK, I'll ping you if this gets done early. 14:37:31 ttx: they're automatic now, we merge as available 14:37:33 thanks 15:01:04 ttx: Here if you're around. 15:01:13 mestery: on a call 15:01:22 ttx: OK. Any ETA? 15:01:31 I may jump into a 15 minutes call myself if you'll be at least that long. 15:01:48 at least 15 min yes 15:01:51 OK 15:29:31 notmyname: around? 15:30:04 mestery: you can go now if you want 15:32:12 ttx: ack 15:32:15 #topic Neutron 15:32:21 https://launchpad.net/neutron/+milestone/juno-rc1 15:32:34 33 targeted bugs, at this point it's too much 15:32:43 you need to reduce to true release blockers 15:32:44 ttx: I agree. 15:32:51 so that we can hit RC1 sometimes before the end of the month 15:32:52 Yes, I spent some time in the meeting talking about that. 15:33:03 I'll have this list culled down by tomorrow. 15:33:19 great 15:33:30 When will you cut RC1? 15:33:34 Is it this week? 15:36:57 ttx: There? 15:37:53 sorry just a sec 15:37:59 ttx: ack 15:39:42 I'm here (on my phone) 15:40:00 ttx: Apologies, I need to take off now. 15:40:14 mestery: ok 15:40:22 ttx: I will get the RC1 page under control, and I have nothing specific for today's cross-project meeting other than to go over the Kilo schedule if people want to. 15:40:25 ttx: Thanks! 15:40:55 sorry got interrupted 15:41:07 mestery: will talk to you again later 15:41:18 #topic Swift 15:41:30 notmyname: how is your next release coming up ? 15:41:48 Overall good. 15:42:04 Probably won't land everything I want, but the important stuff will 15:42:21 notmyname: what would be the updated ETA ? 15:42:42 We're still on track for next week. I'll work closely with you for the RC 15:42:54 notmyname: ok, I'll be around 15:43:05 I have 2 other things 15:43:11 do you need to cut another swiftclient ? 15:43:22 First, we found a regression in the last swiftclient 15:43:23 Yes 15:43:45 The last one we thought was good but into'd a keystone v3 reg 15:43:49 ok, the sooner the better, especially if you want to bump the global-requirements 15:43:58 Will cut a minor point release later this week 15:44:11 No requirements changes 15:44:12 ok 15:44:37 Second, next week we have a kid cycle meetup thing in Boston 15:44:38 #info new swiftclient expected later this week to fix a regression 15:44:56 kid cycle? 15:45:12 Mid. Phone autocorrect 15:45:18 kilo maybe 15:45:58 We'll be looking at ec work and summit prep and etc 15:46:47 ok 15:47:20 Still working on allocation, but looks like you would get 6 scheduled slots + half-day meetup 15:47:26 compared to 8 slots in ATL 15:47:32 so more time overall 15:47:46 but less cheduled ones (like everyone else) 15:47:49 Ok. I'll be starting the communal scheduling this week 15:48:00 Sounds good 15:48:22 notmyname: ok, anything els e? 15:48:37 zaneb: around? 15:48:44 No. I'm good 15:48:44 o/ 15:48:46 Thanks 15:48:50 notmyname: thx! 15:50:06 #topic Heat 15:50:16 https://launchpad.net/heat/+milestone/juno-rc1 15:50:40 we got the FFEs in :) 15:50:41 14 targeted bugs left 15:50:46 zaneb: yep:) 15:51:19 are all those release vlockers ? Or could you refine the list so that only RC things are left in it ? 15:51:23 blockers* 15:51:38 I'd like to hit RC1 before the end of the month if possible 15:52:00 yeah, I definitely don't think all of those are release blockers 15:52:18 I think that's probably feasible 15:52:24 you can use a tag for nice-to-have if you want to track them 15:52:39 I'd like to make sure we are burning down release-critical ones at an acceptable rate 15:53:08 I think the High priority ones are the most release-critical 15:53:22 So I'll be in touch later this week to see how far we are from RC1 15:53:24 fortunately we don't have a large number of those 15:53:37 ok 15:53:43 You did cut a 0.2.11 heatclient 15:53:50 * zaneb needs to find time to scrub the whole bug list anyway 15:53:55 yes we did 15:53:59 and I had a question for you about https://review.openstack.org/#/c/122520/ 15:54:08 is that bump *required* ? 15:54:16 i.eL. does it fix some release-critical bug somewhere ? 15:54:31 we shouldn't bump the floor unless it's required 15:54:42 not sure about that 15:54:49 I will check with stevebaker 15:55:00 well, the review is -1ed until you do find a good reason why we should bump in those troubled times 15:55:10 fair enough :) 15:55:16 and we'll discuss it again at the release meeting tonight 15:55:37 ok 15:56:09 Last thing I had is the provisional slot allocation for summit. Looks like you could get 7 scheduled sessions and a full day of meetup 15:56:27 (compared to 8 slots in ATL) 15:56:38 that sounds really good 15:56:55 you get a lot because your allocation was a bit behind compared to your activity 15:57:17 yeah, it's surprisingly busy around here ;) 15:57:32 (you are more active than Cinder but had 3 less slots) 15:58:03 I'm particularly looking forward to the day of meetup 15:58:45 anything you'd like to flag release-wise ? Any topic for the meeting today ? 15:59:06 nope, can't think of anything 15:59:12 ok great, talk to you later 15:59:22 SergeyLukjanov, mestery: you can go now if you're around 15:59:33 thanks ttx 16:04:30 SlickNik: ready when you are 16:04:44 or markwash__ can beat you 16:04:52 since 6pm is his slot 16:05:01 o/ 16:05:08 going once 16:05:17 markwash__: going twice 16:05:25 #topic Trove 16:05:39 https://launchpad.net/trove/+milestone/juno-rc1 16:06:32 33 bugs left targeted 16:06:33 Looked at all the bugs we have, and spent some time triaging the criticals into Juno, and the rest out. 16:07:05 33 is still way to much, I bet all those are not release blockers 16:07:29 any chance you could refine that list so that it only contains release blockers ? 16:07:33 Agreed — not all of them are. 16:07:43 and use a tag for the nice-to-fix-in-Juno ? 16:07:57 taht way we can trigger a RC1 when we are done with the release blockers 16:08:09 ideally this week, or early in the next 16:08:20 Will do that this week. 16:08:31 btw, didn't know Launchpad did tags. 16:08:35 ok, I'll be in touch later this week to see if we can push a tag 16:09:04 so if you could cull the list before then, that would be awesome 16:09:35 Do you need to cut another troveclient release before Juno release ? 16:09:36 I'll plan on spending some time to do that today. 16:09:46 or is 1.0.7 good enough 16:10:14 If you do, the deadline for that was last Friday, unless you got some regression in :) 16:10:14 1.0.7 is good enough — it's pretty recent (I think a week and a half ago) 16:10:18 ack 16:10:33 It has all the juno-3 feature bps done. 16:10:38 That's all I had release-wise. Any red flag you'd like to communicate ? 16:10:47 any topic for the meeting later ? 16:11:06 Sad that we couldn't get the juno-3 functionality into horizon though. :( 16:11:22 can't get everything 16:11:34 Yup, understand. 16:11:40 And it'll come in Kilo 16:11:41 :) 16:11:53 As far as design summit is concerned, looks like you could get 4 scheduled slots and a half-day meetup (compared to 6 scheduled slots in ATL) 16:12:06 so slight more time oevrall, but less scheduled slots (like everyone) 16:13:20 SlickNik: anything else ? 16:13:33 Cool, are you planning on drawing up a tentative schedule for the slots and posting it on the wiki like you did last time? 16:13:41 That was very helpful. 16:13:57 SlickNik: yes, waiting on some feedback before I can do that 16:14:18 Okay, sounds good. 16:14:20 TripleO needs to tell me if they eed scheduled slots or if they would rather have a full-day meetup instead 16:14:24 need* 16:14:38 That's all I had. Thank you ttx! 16:14:43 SlickNik: ok then, ttyl 16:14:44 markwash__: around? 16:14:50 ttx hi there 16:14:55 #topic Glance 16:15:19 https://blueprints.launchpad.net/glance/+spec/refactoring-glance-logging is still open 16:15:23 or appears to be 16:15:32 It's time to close all FFEs I'm afraid 16:15:39 time well passe 16:15:41 dd 16:15:52 what was there left ? 16:16:13 just https://review.openstack.org/#/c/116626/8 16:16:22 which looks fine to land, unless you think its too too late 16:16:48 let me look at it 16:16:56 no need for https://review.openstack.org/#/c/117204/ ? 16:17:32 markwash__: 116626 is only log info level changes ? 16:17:56 ttx, actually sorry I spoke a little too soon 16:18:01 I guess we should just defer 16:18:19 OK, I'll let you -2 the remaining reviews 16:18:24 kilo opens in a few days now 16:18:45 I'll mark the BP deferred 16:18:59 thanks 16:19:28 OK, so I see no release blocker on that page 16:19:45 I'm a little scared 16:19:52 but its accurate TMK 16:19:53 does that mean you're ready for RC1 tag, or that you didn't go through all the bugs to spot RC ones yet ? 16:20:03 hmm, ok 16:20:40 markwash__: maybe do a last pass on those and if still none, we could tag tomorrow or Thursday 16:20:50 will do 16:20:54 https://bugs.launchpad.net/glance/+bug/1366515 could be added, maybe 16:21:21 with maybe https://review.openstack.org/#/c/119613/ 16:21:32 (https://bugs.launchpad.net/glance/+bug/1366503) 16:22:25 OK... anything else release-related ? 16:22:53 not from me 16:23:07 Looking at design summit, Glance would get 4 scheduled sessions and a half-day meetup (compared to 5 scheduled sessions in ATL) 16:23:43 markwash__: do we have candidates for Glance PTL position already ? 16:24:00 ttx: I was just taking a look at that, and so far no 16:25:09 I imagine 4 sessions and the meetup will be sufficient 16:25:16 markwash__: ok 16:25:21 based on the past sessions 16:25:42 markwash__: talk to you later then ! 16:25:51 sayonara 16:26:02 mestery, SergeyLukjanov: time now for one more 16:26:08 first come first served 16:27:40 ttx, hey 16:27:50 #topic Sahara 16:27:54 ttx, if you're able 16:28:04 #link https://launchpad.net/sahara/+milestone/juno-rc1 16:28:14 So we need to close all remaining FFEs now 16:28:19 time has passed 16:28:35 If I remeber correctly those were technical FFEs though 16:28:49 heh, I forget to update statuses 16:28:49 i.e. one was actually done but you kept it open to track -extra work 16:28:53 both are implemented 16:28:55 and the other was doc 16:28:57 ok 16:29:14 11 bugs on the RC list 16:29:26 would be good to refine to releae blockers 16:29:35 I suspect the "undecided" unassigned one isn't 16:29:42 ttx, most of the are doc ones 16:30:33 s othose are more nice-to-have than release blockers, right ? 16:31:46 maybe use a tag to track doc nice-to-haves for Juno release 16:31:51 and keep the list for true release blockers 16:32:01 so that we know how far we are 16:32:14 ideally we would tag thiws week, or before Tuesday next week 16:32:30 I think we're able to have a tag later this week 16:32:43 we have only several blockers 16:33:09 do you need to tag a client release to catch up with final oslo versions ? 16:33:11 I will cleanup the list and share you the list of blockers 16:33:17 ttx, yup 16:33:24 ok, would be good to do it asap 16:33:29 ttx, it'll be with only one change - oslo versions update 16:33:33 I will do it today 16:33:33 right 16:33:51 do we need to bump version in global req? 16:33:52 that's all I had releasewise 16:33:56 SergeyLukjanov: no 16:34:00 ttx, ack 16:34:07 not unless that fixes a critical bug somewhere 16:34:18 ok 16:34:52 Looking at the design summit, Sahara would get 5 scheduled sessions and a half-day meetup (compared to 7 sessions in ATL) 16:34:57 so, action items on me - release sahara client w/ updated oslo libs and cleanup list of issues that are blockers for release, mark doc issues with tag 16:35:01 so more time overall, but less scheduled slots. 16:35:09 ttx, that's great 16:35:34 ttx, meetup time will make us able to discuss internalls much better than always 16:35:52 agree on actions. I'll be in touch for a potential RC1 tag later this week if you make good progress 16:36:07 anything for meeting tonight ? 16:36:42 note: we have several sahara-related fixes in horizon still on review 16:36:56 but it's not a topic for meeting I think 16:37:13 so, I think nothing more from my side 16:37:14 maybe just make sure they stay on their RC1 list 16:37:17 ok, ttyl 16:37:21 thank you 16:37:40 mestery: i'll ping you around 19:30 UTC for more sync 16:37:47 * ttx takes a break 18:31:24 ttx: I've cleaned up all of the oslo next-juno milestones (renamed the one for oslo-incubator and closed all of the others). The juno series is still open for all and I don't know how to close that, but if you let me know I can do it. 18:43:48 ttx: the requirements readme from this morning is updated - https://review.openstack.org/#/c/116708/ 18:56:19 ttx, sahara client w/ fresh req just released 19:08:12 ttx: I'll be here, thanks! 19:35:36 mestery: around? 19:35:45 ttx: o/ 19:35:51 #topic Neutron 19:36:14 so you asked, when is RC1 19:36:19 ideally some time this week 19:36:26 if not, early next week 19:36:40 OK, makse sense 19:36:52 so the goal is to cut down the buglist so that it only contains release blockers 19:37:19 Yes, I've been working on that 19:37:40 I should have it under control by tomorrow 19:37:46 Or even toinight 19:38:02 You're fine with 2.3.9 as client release ? 19:38:22 Yes, unless someone tells me otherwise 19:38:36 ok, anything else about release ? 19:38:43 I'll be in touch later this week to see if we can tag 19:39:04 Nothing at this time nope 19:39:06 Thanks ttx! 19:39:24 OK, summit-wise, Neutron will get a full day of meetup + 9-11 scheduled sessions 19:39:49 so you can start planning 19:39:50 OK, that sounds about perfect 19:39:54 We are doing that on an etherpad 19:40:07 ok great 19:40:08 https://etherpad.openstack.org/p/kilo-neutron-summit-topics 19:40:21 mestery: anything else ? 19:40:27 ttx: That's it, thanks! 19:40:29 alright then. 19:40:30 #endmeeting