12:35:46 <ttx> #startmeeting incub_sync
12:35:47 <openstack> Meeting started Thu Sep 11 12:35:46 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:35:48 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:35:51 <openstack> The meeting name has been set to 'incub_sync'
12:35:53 <ttx> #topic Designate
12:36:12 <ttx> https://launchpad.net/designate/+milestone/juno-rc1
12:36:29 <ttx> So you still have a feature being pushed iiuc
12:36:44 <Kiall> So - from the rc1 page, we have 1 FFE Blueprint - Graham is working on getting the rebase done at the moment
12:36:56 <ttx> ok, so should merge this week?
12:37:13 <ttx> You also have at least one critical bug to fix before rc1
12:37:17 <Kiall> Yes, It should merge before Monday :)
12:37:49 <ttx> In general, you should use the RC1 page to track all the blockers before we can tag RC1 and open kilo development
12:37:59 <Kiall> Yes - bug 1366821 - We have a fix prepared, currently failing gate due to a dodgy test. It will likely be fixed and merged today / tomorrow.
12:38:10 <ttx> once it's all fixed, we can push tag and have an hopefully good release candidate
12:38:20 <ttx> and you can switch to kilo early
12:38:51 <ttx> if new release-critical bugs are found, we open a new release candidate window
12:38:52 <Kiall> Interesting - Some of the guys are itching to start on some of the K work, they'll be happy with that ;)
12:39:02 <ttx> and backport the master fix to it
12:39:09 <ttx> and cut RC2 when the new list is empty
12:39:17 <ttx> at release day, we just promote the latest RC
12:39:30 <ttx> makes sense?
12:39:33 <Kiall> Yes, perfect sense.
12:39:41 <ttx> Any question on that?
12:40:06 <Kiall> No, I'm fairly familiar with the release process
12:40:13 <ttx> OK, that's all I had then :)
12:40:51 <Kiall> Okay - I had one from last week rescheduling this to a time that I don't tend to get surprise must-attend meetings ;)
12:41:15 <ttx> oh, sure. What time would be better?
12:41:20 <Kiall> You do ptl-sync's tuesday aswell, yes?
12:41:36 <ttx> yes, PTL sync on Tuesday, Incubated syncs on Thursday
12:41:48 <ttx> all your Thursday is bad ?
12:42:48 <Kiall> No, Just Tuesday is almost wide open these days. No problem - If we pushed this back by 2 hours, to 15:30 UTC+1, It's likely a better/easier time
12:43:00 <Kiall> Does that work for you?
12:43:21 <ttx> yes, that works. So 14:30 UTC
12:43:50 <Kiall> Perfect, hopefully less surprises at that time :) Thanks, I'll update my calendar now
12:43:58 <ttx> cool, ttyl
12:44:08 <Kiall> Yep - Thanks!
15:31:23 <ttx> jraim__: ready when you are
15:31:42 <jraim__> jraim__: ready here
15:32:41 <ttx> #topic Barbican
15:32:57 <ttx> https://launchpad.net/barbican/+milestone/juno-rc1
15:33:19 <ttx> You have 3 features still on target
15:33:23 <ttx> how is that going ?
15:33:39 <jraim__> good. The PKCS work is done and should land soon
15:33:50 <jraim__> SSL certs is also on track
15:34:01 <jraim__> I need to check with Arvind and see where his status is
15:34:10 <jraim__> I think it is still good, but I havent' checked in a couple of days
15:34:37 <ttx> are they all in review ? Or some of them are still being worked on ?
15:35:01 <jraim__> They break down into multiple CRs. I think there are still some being worked on though
15:35:27 <ttx> I switched PKCS to "needs code review" since you said it's done
15:35:40 <jraim__> Okay
15:36:11 <ttx> OK, we'll use the RC1 milestone page to track what's left to do before we can tag RC1 and switch master to kilo
15:36:20 <ttx> so please add all release blockers there
15:36:32 <ttx> ideally you would be done with your FFEs by the end of week
15:36:40 <jraim__> sounds good
15:36:42 <ttx> so that you can switch to bugfixing
15:36:55 <ttx> any question at this point?
15:37:03 <jraim__> nope, I'm good
15:37:24 <ttx> awesome, ttyl
15:37:32 <ttx> flaper87: ready when you are
15:37:45 <flaper87> o/
15:37:55 <ttx> #topic Zaqar
15:38:13 <ttx> https://launchpad.net/zaqar/+milestone/juno-rc1
15:38:17 <ttx> 2 featuers still up
15:38:26 <ttx> but both are docs ?
15:38:50 <flaper87> the one with Good Progress isn't but it's done.
15:39:01 <flaper87> I was talking with Aazza 1h ago
15:39:10 <flaper87> (she's working on it)
15:39:14 <flaper87> so, I'll update it
15:39:20 <flaper87> the other one is docs
15:39:37 <ttx> ok, just update status there
15:39:56 <flaper87> sure thing. The current bugs with "Critical" status have people assigned and they're working on it as we speak
15:39:59 <ttx> Like I just said to Jarret, we'll use the RC1 page to track all remaining blockers before tag
15:40:07 <flaper87> I expect to see the patches showing up in a bit
15:40:08 <ttx> so you should target all of them to juno-rc1
15:40:17 <flaper87> +1
15:40:22 <flaper87> will do
15:40:49 <ttx> flaper87: questions?
15:40:56 <flaper87> nope, I'm good!
15:41:03 <flaper87> the rest seems to be under control
15:41:05 <flaper87> :D
15:41:14 <ttx> heh, ok
15:41:21 <ttx> flaper87: ttyl
15:41:25 <flaper87> cheers
15:45:11 <devananda> ttx: o/
15:45:35 <ttx> devananda: hey
15:45:38 <ttx> #topic Ironic
15:46:18 <devananda> ttx: so folks are workign through the bug list on https://launchpad.net/ironic/+milestone/juno-rc1
15:46:47 <ttx> how is UEFI stuff coming up?
15:46:54 <devananda> ttx: I need to check on the status of the one BP we FFE'd... I'm OK bumping it to Kilo if they don't get it in by friday
15:47:11 <devananda> of the 3 patches, 1 landed
15:47:11 <ttx> ok
15:47:24 <devananda> the other two seem quite active and they've responded to feedback...
15:47:46 <ttx> OK, after that we'll use the RC1 page as a target list, and consider we can tag RC1 when it's empty.. so add all release-critical stuff there
15:47:55 <devananda> ack
15:48:00 <ttx> devananda: any question?
15:48:06 <devananda> ttx: client release
15:48:27 <devananda> ttx: should we plan to tag one in sync with other projects on the 18th?
15:48:37 <devananda> and is there a particular version name we should use?
15:48:38 <ttx> I think that would be good practice yes
15:48:53 <ttx> no particular version name. Clients use semver
15:49:12 <ttx> The thread evolved to say that it should be done on the 19th*
15:49:28 <devananda> k. we're at 0.2.1 right now, mostly because I started low, and thought it would be odd to tag a 1.0 before graduation
15:49:29 <ttx> since you may need to bump oslo libs to final in the clients rthemselves
15:49:34 <devananda> (even if there's no policy to that effect AFAIK)
15:49:41 <devananda> ah, good point
15:49:54 <ttx> so we staggered them
15:50:14 <ttx> you're pretty free when it comes to client versioning
15:50:38 <devananda> cool
15:50:43 <devananda> no other questions from me
15:50:56 <ttx> ok, have a nice day!
15:51:01 <devananda> thanks! you too
13:42:14 <mestery> ttx: FFEs are due by today, right? If we have some which are just getting in the merge queue now, is that ok or those are out of Juno?
13:45:37 <ttx> mestery: depends if it's a whole new patchseries of 10, or the last one in an already-merged series of 10 :)
13:45:59 <mestery> ttx: Well, now we're just splitting hairs. ;)
13:46:12 <mestery> ttx: But understand, let me look things over and then bring the hammer down on BPs which have no chance.
13:46:44 <ttx> Things aproved today should be alright, but the idea is that they should merge over the week-end
13:47:00 <ttx> a series of 10 approved today still would require one week at the very least
13:47:35 <ttx> I want next week to be focused on bugfixes, not getting your lastpatches retried
13:48:02 <mestery> ttx: Agreed 100%