16:01:09 <ttx> #startmeeting incub_sync
16:01:10 <openstack> Meeting started Thu Feb 12 16:01:09 2015 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:01:11 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:01:14 <openstack> The meeting name has been set to 'incub_sync'
16:01:22 <ttx> #topic Barbican
16:01:52 <ttx> https://launchpad.net/barbican/+milestone/kilo-3
16:02:09 <ttx> do you plan to add more to this ?
16:02:50 <redrobot> Yes, we have a mid-cycle sprint next week, so we'll use some of the time to get people to commit to blueprints before the fetaure freeze
16:03:09 <ttx> redrobot: cool
16:03:20 <ttx> We'll skip next week syncs, btw
16:03:24 <ttx> FWIW even if we don't formally "incubate" anymore we'll keep those syncs for the time being
16:03:47 <ttx> while I reorganize how we do release management and I see how many projects I can actually coordinate
16:03:48 <redrobot> sounds good.
16:04:22 <ttx> I might end up making it simple enough to cover more than the projects in the current "integrated release"
16:04:40 <ttx> in which case Barbican could get a release:coordinated tag
16:05:02 <ttx> like integrated projects will probably have
16:05:19 <ttx> so, while things are changing, let's not change too much our habits :)
16:05:30 <ttx> redrobot: questions ?
16:05:32 <redrobot> hehe, sounds good to me.
16:05:55 <redrobot> Not really.  I put in some space requests in the spreadsheet you sent last week
16:06:06 <ttx> thx! Will have a look to that
16:06:40 <redrobot> awesome, see you again in two weeks then. :)
16:07:05 <ttx> not sure we'll have bswartz today
16:07:11 <ttx> deep in some midcycle
16:07:20 <ttx> flaper87: want to run now ?
16:15:05 <Kiall> ttx: I'm about if you've been stood up ;)
16:15:15 <ttx> Kiall: my savior!
16:15:21 <ttx> I was feeling a bit lonely here
16:15:25 <ttx> #topic Designate
16:15:38 <ttx> #link https://launchpad.net/designate/+milestone/kilo-3
16:16:00 <ttx> is that the full extent of what you're working on ?
16:16:06 <ttx> or do you expect to add more ?
16:16:39 <Kiall> The team filed + triaged lots of bugs yesterday, but I've been travelling pretty much solidly for the last month so haven't 100% caught up yet.
16:16:46 <flaper87> ttx: here now (ping me) :D
16:16:48 <Kiall> In terms of BP's - That's it as far as I know
16:16:59 <Kiall> Stability fixes from now on
16:17:10 <ttx> alright...
16:17:12 <ttx> also read what I told redrobot above: even  if we don't formally "incubate" anymore we'll keep those syncs for the time being, while we figure out what to exactly do
16:17:30 <Kiall> ttx: yea, makes sense.. I'm still trying to figure out what all the changes mean for us ;)
16:17:47 <ttx> what is costly is our try to predict what will be in next milestones... and apparently this has little value
16:18:07 <ttx> if we keep it around the release mechanics, it's relatively cheap
16:18:20 <ttx> and won't need as much coordination
16:18:36 <ttx> so I'm working on simplifying the work to the point where supporting more projects is not an issue
16:18:57 <ttx> (just talkign about release management supporting more than the current "integarted release" here
16:19:08 <ttx> so in the mean time let's act as if nothing changed
16:19:17 <Kiall> Makes sense, so you do intend to keep ahold of the non-core releases, but only from a tooling rather than release manage POV?
16:19:26 <Kiall> release manager*
16:19:46 <ttx> yeah, mostly
16:19:48 <ttx> we'll skip next week syncs though, nno point in extra useless meeting in the soft belly of the milestone
16:20:01 <Kiall> Sure - Sounds good
16:20:03 <ttx> questions on that ?
16:20:08 <ttx> or anythign else ?
16:20:15 <Kiall> Any idea on when we might make any changes?
16:20:30 <ttx> before the end of the cycle
16:21:00 <Kiall> K - So L will be entirely done by the "new rules"
16:21:02 <ttx> the idea would be to swtich to reactive rather than predictive handling of milestones for Liberty
16:21:08 <ttx> (i can't get used to that)
16:21:25 <Kiall> Liberty? yea - I'm going to keep calling it L - or Lima ;)
16:21:39 <ttx> basically, we would stop trying to predict what will land in next milestone (and fail at it)
16:21:49 <ttx> and just keep track of what actually landed
16:22:02 <ttx> since nobody seems to consume our predictions anyway
16:22:10 <ttx> and those are a hell of a lot of work to maintain
16:22:14 <Kiall> :)
16:22:34 <ttx> so we'd switch to after-the-fact accounting, which is much easier
16:22:43 <ttx> doesn't remove the need to keep BPs up to date...
16:22:53 <ttx> but we don't actually care about deferring and all
16:23:21 <ttx> which currently is the main reason for these syncs
16:23:27 <ttx> Kiall: other questions ?
16:23:32 <Kiall> No - Thats it :)
16:23:41 <ttx> Kiall: ok, talk to you in two weeks :)
16:23:45 <ttx> flaper87: you're on
16:23:50 <Kiall> Enjoy the "week off" ;)
16:23:56 <flaper87> just in time
16:23:57 <ttx> #topic Zaqar
16:24:10 <ttx> #link https://launchpad.net/zaqar/+milestone/kilo-3
16:24:21 <flaper87> so, lots of reviews to do
16:24:27 <ttx> Looks good, except that https://blueprints.launchpad.net/zaqar/+spec/ops-stats
16:24:40 <ttx> (with no assignee or status
16:24:55 <flaper87> yeah, That one I still have to evaluat the impact and decided on whether it's worth having it for K
16:25:02 <flaper87> It's likely going to be pushed to L
16:25:14 <ttx> ack
16:25:21 <flaper87> evaluate*
16:25:33 <ttx> I assume you've read what I told Kiall and redrobot above
16:25:39 <flaper87> yup :)
16:25:42 <ttx> (and we'll skip next week 1:1)
16:25:52 * flaper87 was reading other's meetings
16:25:57 <ttx> other questions ?
16:25:58 * flaper87 is a natural stalker
16:26:02 <flaper87> nope, I'm good
16:26:10 <ttx> that's why you like public channels so much , heh
16:26:14 <flaper87> hahahaha
16:26:19 <flaper87> damn, you got me
16:26:45 <ttx> ok then, have a good (two) weeks
16:32:27 <ttx> #endmeeting