16:02:54 <ttx> #startmeeting incub_sync
16:02:55 <openstack> Meeting started Thu Dec 11 16:02:54 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:02:56 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:02:59 <openstack> The meeting name has been set to 'incub_sync'
16:03:03 <ttx> sorry was lost in a IRC rant
16:03:12 <ttx> #topic Barbican
16:03:19 <redrobot> np
16:03:25 <ttx> Checked jobs and tarball contents in prep for k1 next week
16:03:36 <ttx> looks like you're all good (not just you)
16:03:58 <redrobot> Yeah, should be good to go
16:04:24 <ttx> The process is that sometimes between Tuesday and Thursday, when you're happy with the state of master and you're not waiting for zuul to chow your last +2, you can send me the SHA
16:04:39 <ttx> and I'll push the tag and do the Launchpad magic
16:04:58 <ttx> does that work for you ?
16:05:26 <redrobot> Yeah, I'll probably be emailing you.  I'm traveling next week, and my internet access will be limited
16:05:39 <ttx> that's fine
16:05:44 <ttx> https://launchpad.net/barbican/+milestone/kilo-1
16:05:57 <ttx> How is replace-concept-of-tenants-for-projects doing ?
16:06:13 <ttx> all changes proposed under that topic merged... more to come ?
16:06:29 <redrobot> I think there's one more pending for the test suite
16:06:47 <redrobot> I think it should be up for review in the next day or two
16:07:25 <ttx> ok, so we'll try to include that one in the tag
16:07:38 <ttx> anything else coming up ? Or that will be k1 ?
16:08:57 <redrobot> There may be a bug or two in flight, but no other BPs
16:09:18 <ttx> sure, committed bugs will get auto-added by the script anyway
16:09:24 <ttx> so that's fine
16:09:33 <ttx> questions about the process for next week ?
16:09:47 <redrobot> nope, I think it usually goes pretty smoothly
16:09:54 <ttx> Feel free to communicate the SHA as early as Tuesday
16:10:02 <redrobot> Sure thing.
16:10:07 <ttx> I won't mind some early start
16:10:11 <redrobot> I'll probably miss the 1:1 next week.
16:10:21 <ttx> redrobot: fine too.
16:10:40 <ttx> we'll probably skip it for those who communicated tags already
16:10:47 <redrobot> I'm assuming no 1:1 Christmas Day and New Year's?
16:11:03 <bswartz> lol good point
16:11:05 <ttx> yep, next is 8th
16:11:21 <bswartz> holidays on Thursday this year
16:11:30 <ttx> #topic Manila
16:11:33 <ttx> redrobot: thx!
16:11:37 <ttx> bswartz: o/
16:11:38 <bswartz> hi
16:11:47 <ttx> I checked all CI and we should be OK for tarballs and stuff
16:11:53 <bswartz> so we did the great k-1 purge today
16:11:58 <bswartz> a bunch of stuff got pushed out to k-2
16:11:59 <ttx> so like I told redrobot:
16:12:06 <ttx> The process is that sometimes between Tuesday and Thursday, when you're happy with the state of master and you're not waiting for zuul to chow your last +2, you can send me the SHA
16:12:10 <ttx> and I'll push the tag and do the Launchpad magic
16:12:17 <bswartz> okay
16:12:37 <ttx> you can send an email
16:12:44 <ttx> or ping me on IRC with SHA
16:12:44 <bswartz> alright
16:12:52 <ttx> https://launchpad.net/manila/+milestone/kilo-1
16:13:25 <bswartz> everything that remains here has a good chance of merging in the next 4 days
16:13:34 <ttx> alright, let's try this :)
16:13:58 <ttx> worst case scenario we'll bump them at this 1:1 sync next Thursday
16:14:31 <bswartz> okay
16:14:47 <bswartz> from your perspective, is there any difference between how milestones 1, 2, and 3 are run?
16:15:10 <ttx> from the release management perspective, 1 and 2 are the same
16:15:13 <bswartz> obviously milestone 4 has a very different flavor
16:15:18 <ttx> 3 triggers feature freeze (generally)
16:15:41 <ttx> we don't really have a 4, we have a RC1, and that's when we craete the proposed/$SRIES branch
16:15:46 <bswartz> right
16:16:03 <bswartz> are you involved with the FFE process, or is that left to the teams?
16:16:05 <ttx> but the process for "publishing" 3 is the same as 1 and 2
16:16:31 <ttx> I am involved to help PTLs in already-integrated projects
16:16:40 <ttx> but that obvisouly doesn't scale
16:16:44 <bswartz> ok
16:17:01 <bswartz> I've been following some of the TC and crossproject meetings
16:17:02 <ttx> incubated projects traditionally handled them themselves, with advice from me
16:17:16 <ttx> I think soon every project will do the same
16:17:17 <bswartz> we don't yet follow some processes, such as the specs repo
16:17:32 <bswartz> is that going to become mandatory at some point?
16:17:52 <ttx> bswartz: I don't expect it to become mandatory no
16:18:05 <bswartz> okay
16:18:11 <ttx> we are going towards more acceptance of divergent processes rather than less :)
16:18:40 <bswartz> for the most part we try to do things the way cinder does them, but with less heavy handed deadlines and fewer requirements on vendors
16:18:52 <ttx> sounds good
16:18:56 <bswartz> maybe in the long run we will have to adopt cinder's policies
16:19:18 <ttx> so for the FFE it will be mostly your call (and your delegates call)
16:19:27 <ttx> I can advise but I shouldn't be the blocker
16:19:36 <bswartz> I saw jeblair's change last week regarding the tarball release, thanks for making that happen
16:20:02 <ttx> the only reason I was so heavily involved in FFE was to guarantee some level of quality and that we hit the deadline
16:20:11 <bswartz> are you pretty confident that we'll get a k-1 tarball that packagers can accept?
16:20:24 <ttx> If I can teach people to fish, won't have to go that much to sea myself.
16:20:37 <bswartz> heh
16:20:45 <ttx> well, I know we'll get a tarball. No idea if it is usable :)
16:20:53 <bswartz> heh
16:21:08 <bswartz> okay I guess we'll have to just hope
16:21:15 <bswartz> so let's keep this meeting next week
16:21:21 <ttx> you could toss http://tarballs.openstack.org/manila/manila-master.tar.gz to prospective packagers and ask them
16:21:31 <bswartz> yes
16:21:32 <ttx> if they feel anything is missing
16:21:39 <ttx> they usually hang out in #openstack-stable
16:21:50 <bswartz> I know who they are -- I'll speak to some of them
16:21:58 <ttx> ok, time is up, talk to you next week ?
16:22:04 <ttx> flaper87: around ?
16:22:06 <bswartz> yep
16:22:07 <bswartz> thanks
16:22:16 <ttx> bswartz: thx!
16:22:45 <flaper87> ttx: yes
16:22:48 <ttx> #topic Zaqar
16:23:01 <ttx> flaper87: next week, k1
16:23:02 <flaper87> moment of truth
16:23:22 <ttx> flaper87: I'll push a tag sometimes between Tuesday and Thursday, as soon as you send me a SHA
16:23:37 <ttx> so whenever you're happy with what you have in master...
16:23:44 <ttx> just let me know
16:23:48 <flaper87> ttx: roger
16:23:57 <ttx> https://launchpad.net/zaqar/+milestone/kilo-1
16:24:00 <flaper87> those bps that seem not to have info, actually are in progress
16:24:14 <flaper87> there's still chance for them to land
16:24:15 <ttx> ok, we should fix those then
16:24:19 <flaper87> yes
16:24:23 <ttx> https://blueprints.launchpad.net/zaqar/+spec/disable-sqlalchemy-as-pool
16:24:34 <ttx> obviously at least Started
16:24:44 <flaper87> fixed :P
16:25:05 <flaper87> I'll do a ping-check on Monday during our meeting
16:25:10 <ttx> Should I set the two Undefined to "Low" prio ?
16:25:11 <flaper87> if I don't get an answer, I'll move them
16:25:31 <flaper87> I just set MEdium
16:26:12 <ttx> Yes, you should decide at that meeting if they are in the pipe and we should wait for them... or shoul djust be deferred and the tag pushed
16:26:24 <flaper87> yes
16:26:41 <ttx> that leaves a couple of days to get them proposed and reviewed
16:26:54 <ttx> Questions on the process ?
16:26:55 <flaper87> other than that, everything seems to be under control.
16:27:02 <flaper87> no questions from me
16:27:22 <ttx> alright. Have a good evening!
16:27:27 <flaper87> you too
16:27:45 <ttx> Kiall: yt?
16:28:05 <Kiall> Walking back into the office.
16:28:09 <Kiall> 2 mins
16:28:17 <ttx> np, ping me when ready
16:30:00 <Kiall> ttx: heya
16:30:11 <ttx> #topic Designate
16:30:51 <ttx> Checked jenkins/zuul and tarball contents, all green
16:31:08 <ttx> copy pasting process
16:31:10 <Kiall> Excellent, I saw you created the k2+ milestones too
16:31:10 <ttx> The process is that sometimes between Tuesday and Thursday, when you're happy with the state of master and you're not waiting for zuul to chow your last +2, you can send me the SHA
16:31:24 <ttx> and I'll make the magic happen
16:31:36 <ttx> magic == https://wiki.openstack.org/wiki/Release_Team/How_To_Release
16:31:38 <Kiall> Great, It'll likely be closer to Thu than Tue, but no problem.
16:31:48 <ttx> https://launchpad.net/designate/+milestone/kilo-1
16:32:09 <ttx> the last down the list is begging for me asking abou tit
16:32:26 <ttx> without assignee and not started :)
16:32:27 <Kiall> config reload? Yea, it will be pushed :)
16:32:40 <Kiall> let me move that out to k2 now..
16:32:42 <ttx> can I push it now ?
16:32:44 <ttx> ok
16:32:51 <Kiall> done
16:33:07 <ttx> the last two still have a good chance to make it ?
16:33:31 <Kiall> "Transition PowerDNS backend to Pools" is blocked on another issue, which doesn't have a ticket (I'll file one), but yes - it has a good chance.
16:33:57 <Kiall> The framework bits of "Centralize validation logic where it makes sense" are in, but there's more to do which won't land in k1
16:34:08 <Kiall> (i.e it's half done + merged)
16:34:17 <ttx> so then you have two options
16:34:23 <Kiall> I'm not sure what the norm for handling that is :)
16:34:32 <ttx> you can split it and mark part1 implemented
16:34:39 <ttx> or you just defer the whole to k2
16:34:50 <ttx> depends how much the part1 makes sense as a thing
16:34:59 <Kiall> Okay, I'll split it - I think that makes sense..
16:35:04 <ttx> and how much you want to pet the developer in the back
16:35:11 <Kiall> developer is me ;)
16:35:15 <ttx> hehe
16:35:55 <ttx> basically, if you feel it's worth communicating what landed in k1 to a wider audience, split it
16:36:13 <ttx> if it's just work items 1 to 4 in a 10-step plan... maybe not
16:36:22 <ttx> not an exact science here
16:36:30 <Kiall> K
16:36:40 <ttx> ok, other questions before we close ?
16:37:06 <Kiall> Nope - None from me :)
16:37:29 <ttx> alright, you're all making my job easy by being on top of what gets done in your projects, thanks
16:37:37 <ttx> have a good day!
16:37:44 <Kiall> Same to you :)
16:37:49 <ttx> #endmeeting