14:32:20 #startmeeting incub_sync 14:32:20 Meeting started Thu Sep 18 14:32:20 2014 UTC and is due to finish in 60 minutes. The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:32:21 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:32:23 Now.. The Q is, where do we put the time.sleep(1) .. 14:32:24 The meeting name has been set to 'incub_sync' 14:32:25 #topic Designate 14:32:27 oops - wrong room 14:32:28 ;) 14:32:52 https://launchpad.net/designate/+milestone/juno-rc1 14:33:09 Still have one blueprint open -- how is zone-migration-between-tenants doing? 14:33:46 Good/Bad - Graham hasn't completed the rebase. If we can't have that in by mid-week next week, I'm going to push it to kilo. 14:34:13 The good is re - it's just in need of a rebase, but everyone has been busy with other tasks! 14:34:57 You suggested last week we might cut a rc1 once they merge, a number of new bugs have been found and are in progress - they're severe enough to warrant holding out. 14:34:57 your call. If you were integrated, that would be too late, and too much of a distraction from bugfixing 14:35:13 ttx: for integrated - what's the hard deadline? 14:35:42 end of this week for the last tragglers. We deferred most of the others earlier this week 14:35:47 stragglers* 14:36:07 as for RC1, the idea is to cut something you think will be your final release, not just another milestone 14:36:19 so if you have a set of targeted bugs, better wait for them to be fixed 14:36:34 Okay - I think we can stick to that (well, closer to that!) .. If it's not merged Monday, we'll push it. I'd like to get it in :) 14:36:35 rathet than cut a RC1 and open a RC2 window hours after 14:36:47 ttx: agreed 14:37:05 Kiall: there is less risk involved with incubated projects, so feel free to push the deadline farther away 14:37:34 basically, if you don't have a viable RC1 by October 16, you wouldn't make my life miserable. Only yours :) 14:38:05 Hah - Yea, that won't happen - I won't allow it ;) 14:38:21 Is the bug list on the https://launchpad.net/designate/+milestone/juno-rc1 representative of all your release blockers ? 14:38:41 i.e. those 4 bugs left are the only ones you really need to fix before release ? 14:38:51 Yes, although I haven't triaged 1370621 Bing9 PTR Zone error : multiple RRs of singleton type yet 14:39:55 ok, you seem to have a good handle on things. Questions ? 14:40:22 Nothing new this week :) 14:42:05 (I'll have plenty once we open kilo, but they can all wait!) 15:32:27 Kiall: sorry, got caught up in something. Thanks! 15:32:38 ttx: no problem :) 15:48:41 jraim: o/ 15:48:45 #topic Barbican 15:48:47 ttx: here 15:48:56 redrobot: you there? 15:48:59 o/ 15:49:08 I see two bluepritns still open 15:49:15 add-ssl-ca-support 15:49:19 api-orders-add-more-types 15:49:35 api-orders-add-more-types is just waiting on one more CR 15:49:39 Correct. We landed one and the api-orders one is in final review 15:49:41 it would be good to complete or defer them at this point, to turn focus to bugfixing 15:49:44 I think we should be landing it in the next couple of days 15:49:55 ok 15:50:01 add-ssl-ca-support probably needs to slip to Kilo 15:50:12 I have low confidence we can complete it by RC1 15:50:43 your call really, since you bear the consequences of failing to meet the release date 15:50:58 RC1 is not really a date on the calendar 15:51:14 We're okay with slipping it if we have too...it seems like it won't make it at this point 15:51:19 the idea is that when you have something you think would make a good release, we cut a branch and pusg a rc1 tag 15:51:49 ideally it all happens befor ethe final release date so that you can release at the same time 15:52:04 (at release date we just take the latest release candidate and promote it 15:52:06 ) 15:52:30 makes sense 15:52:40 in my experience, it's good to get rid of all feature work before the end of this week -- so that you can turn undivided attention to bugfixing 15:52:55 So we'll land the one that's almost done, but it looks like we'll push the SSL one to K 15:53:07 sound slike a good call 15:53:32 We did want to ask about design sessions 15:53:43 Did we come to a resolution on how those are getting planned? 15:53:54 yeah 15:54:13 so you'll have a number of sessions on the Tuesday, something like half a day 15:54:24 that's sessions that appear on the schedule 15:54:41 you'll also have a designated pod (table) to continue the discussions throughout the rest of the week 15:55:09 Okay, so we need to plan the tues sessions, but the rest is ad hoc 15:55:14 right 15:55:44 so it's good to use the scheduled sessions for stuff you want to communicate out of the project, things you want operator feedback on, etc 15:55:57 and keep project-internal discussion at the pod 15:56:04 Right. That sounds good. We have an etherpad we've been using to get those rolling 15:56:19 Last question I think - when are we doing PTL nominations for Kilo? 15:56:33 jraim: you might want to reference your etherpad at https://wiki.openstack.org/wiki/Summit/Planning 15:56:39 starting tomorrow 15:56:40 Will do 15:56:48 (PTL nominatins start tomorrow) 15:56:55 Perfect 15:57:06 jraim: any other question? 15:57:11 nope, we're good 15:57:18 ok, talk to you next week then 15:57:58 flaper87: around? 15:58:03 ttx: yes, sir 15:58:12 https://launchpad.net/zaqar/+milestone/juno-rc1 looks good 15:58:18 no FFE in progress 15:58:29 yup, as for the 2 bugs. 1 fix is in the gate and the other one coming soon 15:58:42 feel free to target more bugs to rc1, as we will tag (and open kilo) once the list is empty 15:59:15 roger, I'm planing to go through the list of bugs tomorrow and see if there's anything that makes sense fixing in rc1 16:00:11 FWIW I scheduled the next session with the TC the week after next -- I figured we could use a one-week break 16:00:17 and start a few constructive ML threads 16:00:56 right 16:01:02 the urgency of the decision being part of the problem we had, I think 16:01:09 I sent one yday but I havne't seen any reply besides eglynn's 16:01:16 flaper87: any question on the RC1 / release ? 16:01:20 ttx: nope 16:01:26 flaper87: I'm a bit late on -dev, been traveling lately 16:01:40 no worries, I just hope it to help with the discussion 16:01:51 ok great, talk to you later 16:01:56 devananda: you around ? 16:04:59 ttx: o/ 16:05:11 #topic Ironic 16:05:22 devananda: so as far as Juno is concerned, you're still incubated 16:05:28 ttx: yep 16:05:32 https://launchpad.net/ironic/+milestone/juno-rc1 16:05:38 All FFEs done 16:05:45 and a small list of RC bugs 16:06:03 Feels like you could hit a RC1 sooner rather than later 16:06:10 or do you need to add more to the list ? 16:06:35 we were going to collectively assess the bug sitaution today and see what, if anything, is really a blocker 16:07:02 we're using targeting as a way to track what we want in right now, not necessarily release blockers 16:07:49 and as I do not see any open Critical bugs, I would agree that we probably could tag now 16:08:03 but if it's not an impediment, I'd rather tag next week to give a little time to close some of the High bugs 16:08:27 also, i'm goign to tag our final client release today 16:08:32 devananda: ok, at this point you can add a lot, and starting next week, we'll start to cut down if necessary 16:08:49 the "good enough" approach to release management 16:08:57 sounds good 16:09:06 devananda: ok, just let me know if you have any question 16:09:14 otherwise we'll close shop 16:09:36 when can we start votign on nova :) 16:09:49 though that's probably a question for the qa team, not you 16:10:26 ttx: no more questions related to the release 16:10:37 devananda: alrighty then 16:10:41 #endmeeting