08:01:43 <ttx> #startmeeting ptl_sync
08:01:44 <openstack> Meeting started Tue Sep 16 08:01:43 2014 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:01:46 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:01:47 <ttx> #topic Nova
08:01:48 <openstack> The meeting name has been set to 'ptl_sync'
08:01:59 <mikal> Oh hai!
08:02:08 <mikal> Not sure where John is, he's not in the nova channel at the moment either
08:02:12 <mikal> Regardless, let us proceed
08:02:13 <ttx> https://launchpad.net/nova/+milestone/juno-rc1
08:02:22 <ttx> I see 3 still up
08:02:26 <mikal> So, yeah
08:02:32 <mikal> All FFEs are now implemented / merged
08:02:44 <mikal> Those three weren't granted FFEs
08:02:56 <mikal> Well, except perhaps the partial one
08:03:04 <mikal> I'm not sure why they're there, I need to touch base with John
08:03:14 <ttx> here is is
08:03:19 <mikal> johnthetubaguy: oh hai!
08:03:23 <ttx> he is*
08:03:48 <ttx> yeah, I'd tend to just move them to kilo-1 at this point
08:04:03 <mikal> Yeah, I think that's the plan
08:04:09 <mikal> With the possible exception of the partial one
08:04:20 <ttx> yes, if it makes sense to split it
08:04:24 <mikal> We should also be moving onto just bug fixes now
08:04:39 <mikal> I also need to do a python-novaclient release in the next day or so
08:04:44 <mikal> But didn't manage to get to it today
08:05:29 <ttx> I can see that sdague did some serious triaging last week, so I feel like most of the critical issues were identified and targeted
08:05:39 <mikal> Yeah, Sean has been doing an awesome job
08:06:05 <mikal> The only other thing I have to discuss is the ongoing extra-atcs "fun"
08:06:16 <ttx> so apart from moving BPs to k1 I'd say the next step is to assign those bugs
08:06:18 <mikal> But that might be an "open discussion" item for the meeting tomorrow
08:06:48 * mikal checks if all criticals are listed there
08:06:54 <mikal> Ummm, no
08:06:55 <ttx> what did you want to discuss about them ? More a TC or a cross-project meeting topic ?
08:07:02 <mikal> So yes, I agree that we need to get people assigned to the critical bugs
08:07:11 <mikal> About extra-atcs?
08:07:14 <ttx> yes
08:07:20 <johnthetubaguy> mikal: ttx: morning, sorry, battling getting my computer to wake up
08:07:29 <mikal> Mostly that other PTLs need to do it themselves, the elections people had concerns with me doing it for people
08:07:30 <johnthetubaguy> but here now
08:07:58 <mikal> johnthetubaguy: hi!
08:08:04 <ttx> johnthetubaguy: the question is abot those BPs without a FFE still present on juno-rc1 page
08:08:09 <johnthetubaguy> lots of people just target bugs for giggles, they are not all important
08:08:16 <ttx> johnthetubaguy: should we move them all to k-1 ?
08:08:28 <mikal> johnthetubaguy: and what about the v2.1 api one
08:08:35 <mikal> johnthetubaguy: its partial, so perhaps we mark it implemented now?
08:08:44 <ttx> should it be implemeted/split
08:08:45 <johnthetubaguy> ttx: I think thats bad, given what we have agreed with people at this point, but certainly should do that semi-quickly
08:09:00 <mikal> Oh yeah
08:09:02 <johnthetubaguy> ttx: +1 mark it partial and complete
08:09:09 <mikal> ttx: so, we said that kilo would require spec reapproval
08:09:11 <johnthetubaguy> mikal: I think we need to merge the spec in K
08:09:13 <mikal> So we should just untarget them
08:09:16 <mikal> But not move them to K
08:09:37 <mikal> And K specs don't open until the start of October IIRC
08:09:38 <ttx> mikal: ok, remove juno-rc1 from them then, and remove priority
08:09:59 <ttx> so that if they retarget it, they won't stick
08:10:31 <ttx> mikal: so clear the milestone target, and set priority to undecided
08:10:38 <mikal> Yep
08:10:50 <ttx> I'll mark the partial v2/v3 implemented
08:10:57 <mikal> Ok
08:11:46 <ttx> So yes, focus this week is to come up with a reasonable list of release-critical bugs, get them all assigned
08:11:59 <ttx> so that we can potentially have a RC1 cut next week
08:12:54 <ttx> does that make sense?
08:13:14 <mikal> Yep
08:13:21 <mikal> Ok, so those two BPs have been untargetted now
08:13:59 <mikal> I'll start chasing people about RC bugs ASAP
08:14:01 <ttx> Kilo PTL election season starts at the end of this week, too
08:14:17 <ttx> with one week for self-nomination
08:14:22 <mikal> Yep, which is why extra-atcs is important
08:14:30 <mikal> But so noted
08:15:10 <ttx> mikal: I'll add the topic of extra-atcs to the cross-project meeting
08:15:19 <ttx> that's where the PTLs are
08:15:22 <mikal> ttx: do you intend to use this 1:1 next week for getting a rc1 sha?
08:15:30 <mikal> ttx: or do we need to sync up before then on that?
08:15:44 <mikal> Yep, agreed that's the right venue for it
08:15:54 <mikal> Hopefully the TC will have made a stance clear in the meeting before the release meeting
08:16:06 <mikal> i.e. -1'ed to death the review or approved it
08:16:09 <ttx> mikal: there is no set date for the RC1 sha. It's when ready. But starting next week, if the list is empty, we should cut one yes
08:16:22 <johnthetubaguy> sorry, it died again, batter is very, very low
08:16:22 <mikal> ttx: do you try to sync up the projects?
08:16:29 <mikal> ttx: or just when nova is ready we do nova?
08:16:34 <mikal> johnthetubaguy: :(
08:16:36 <ttx> mikal: no, RCs are done "when ready"
08:16:44 <mikal> Ok, define done for me
08:16:48 <mikal> All RC bugs closed?
08:16:50 <ttx> mikal: yes
08:16:55 <johnthetubaguy> mikal: yeah, we need that list
08:17:05 <mikal> And I assume there's a RC bug tag we use to mark bugs as RC?
08:17:07 <ttx> so the question becomes: fine-tuning that list
08:17:22 <ttx> mikal: no, that's anything on juno-rc1
08:17:30 <mikal> Ahhh, ok
08:17:32 <ttx> we use the milestone target
08:17:32 <mikal> Makes sense
08:17:40 <mikal> So what's the historical stance on critical bugs?
08:17:44 <mikal> Are they all RC by definition?
08:17:48 <mikal> Cause, critical?
08:17:49 <ttx> well, it would make more sense if that targeting was restricted to drivers, but meh
08:18:08 <ttx> so, generally yes, critical bugs are RC
08:18:16 <ttx> but sometimes a non-critical bug is RC
08:18:27 <mikal> Oh, agreed
08:18:30 <ttx> think a doc bug, or a missing file in tarball
08:18:34 <mikal> Its just we have untargetted criticals as well
08:18:37 <johnthetubaguy> ttx: mikal: sorry, lazyness, but we said friday was the drop dead date for FFEs, did anyone kick those out of juno yet, and we wait for spec to be moved to kilo before re-approve?
08:18:39 <ttx> things you need to fix before release rather than the day after
08:18:48 <ttx> missing LICENSE file, that sort of thing
08:18:52 <mikal> johnthetubaguy: so... all FFEs merged
08:18:59 <mikal> johnthetubaguy: the two things without FFE were bumped just now by me
08:19:06 <johnthetubaguy> mikal: gotcha
08:19:13 <mikal> johnthetubaguy: assuming I didn't horribly screw up
08:19:19 <johnthetubaguy> mikal: you got the blueprint links? I can put them in the usual places
08:19:21 <ttx> mikal: if they are truly critical then yes, they should be RC
08:19:21 <mikal> johnthetubaguy: certainly all the things on the etherpad merged
08:19:32 <ttx> but sometimes they aren't that critical, if you see what I mean
08:19:46 <mikal> johnthetubaguy: links for the two things I untargetted you mean?
08:19:54 <johnthetubaguy> I guess easy backports on not worth delaying the train, etc
08:19:57 <mikal> ttx: in which case they should have their priority changed
08:20:00 <johnthetubaguy> mikal: yes
08:20:03 <ttx> mikal: exactly
08:20:10 <mikal> johnthetubaguy: https://blueprints.launchpad.net/nova/+spec/lvm-ephemeral-storage-encryption
08:20:15 <mikal> johnthetubaguy: https://blueprints.launchpad.net/nova/+spec/libvirt-start-lxc-from-block-devices
08:20:26 <johnthetubaguy> mikal: cool, thank you
08:20:30 <mikal> NP
08:20:42 <mikal> Ok
08:20:46 <mikal> I will target all criticals
08:21:02 <mikal> And bump any criticals which aren't really critical (and possibly untarget them as well)
08:21:09 <mikal> bump == "reduce priority"
08:21:22 <johnthetubaguy> awesome
08:21:25 <ttx> generally, after one week, we realize we won't cut a RC1 in time for final release, and we aggressively raise the bar for release-criticalness :)
08:21:33 <johnthetubaguy> mikal: will you catch tracy when she is online?
08:21:46 <mikal> johnthetubaguy: yep, tomorrow morning I assume
08:21:53 <mikal> But I feel an email in my future as ewll
08:21:55 <mikal> well even
08:22:22 <ttx> mikal: in summary, you build a god list, and then we trim it down either by bugfixing or considering bugs non-release-critical after all
08:22:26 <ttx> good*
08:22:36 <mikal> Works for me
08:23:45 <ttx> then we track RC burndown in graphs like http://ttx.re/images/havana-rcs.png
08:24:01 <mikal> Oh, I love a good management dashboard
08:24:11 <johnthetubaguy> mikal: cool, I removed the approval of those blueprint, moved them to trunk where I am holding the others, and added a note about whats happened to them, and that they will need a kilo spec.
08:24:26 <ttx> you can see when we started refining the nova list for havana
08:24:35 <mikal> johnthetubaguy: thanks
08:24:50 <ttx> it was like OMG we'll never make it, then on 9/24 we just cut the list down
08:25:13 <mikal> Wow, that's a lot of RC bugs at the start
08:25:29 <ttx> mikal: you could argue it was unreasonably too much
08:25:47 <ttx> bugs were added to list faster than they were fixed
08:25:56 * ttx should geberate that graph again
08:26:00 <ttx> or generate
08:26:08 <mikal> No, I prefer geberate
08:26:14 <johnthetubaguy> I think we had some bug triage day to pick the top ones, but I might be miss-remembering
08:26:29 <mikal> johnthetubaguy: yeah, I was just thinking on the process of picking them
08:26:36 <mikal> johnthetubaguy: might be email to -drivers time?
08:27:00 <mikal> Although perhaps -dev is the right place
08:27:03 <johnthetubaguy> mikal: well, may as well ask everyone, stuff thats hard to backport, and affects lots of people
08:27:06 <johnthetubaguy> yeah
08:27:11 <mikal> sdague has been doign good work and I want to include him
08:27:45 <johnthetubaguy> yeah, I have a lot of time for him
08:27:53 <mikal> I do too
08:27:59 <mikal> But then he went and triaged every nova bug
08:28:00 <ttx> mikal: ok any other questions?
08:28:06 <mikal> So now I think I owe him my first born or something
08:28:16 <mikal> ttx: no, I think I know what to be doing for the next week
08:28:53 <ttx> ok then, talk to you tomorrow morning
08:29:14 <johnthetubaguy> mikal: any urgent stuff you need me to do today, was off yesterday, hence not fixing up the RC1 blueprint list
08:29:38 <johnthetubaguy> (yesterday being monday for me)
08:30:03 <mikal> johnthetubaguy: I think we ok for now
08:30:11 <johnthetubaguy> good good
08:30:14 <mikal> johnthetubaguy: I'm a bit worried about getting RC bugs fixed, but step one is working out what is RC
08:30:26 <mikal> ttx: thanks once again for being super helpful
08:30:54 <ttx> np!
11:44:07 <ttx> eglynn: ready when you are
11:44:18 <eglynn> ttx: cool, let's go for it :)
11:44:30 <ttx> #topic Ceilometer
11:44:31 <eglynn> #link https://launchpad.net/ceilometer/+milestone/juno-rc1
11:44:45 <eglynn> all FFE BPs are now landed :)
11:44:51 <ttx> great!
11:45:10 <ttx> so now the focus is on identifying release-critical bugs and fixing them
11:45:11 <eglynn> I've done a trawl of the targeted bug and punt on all that look like they don't have sufficient traction to land
11:45:14 <eglynn> yep
11:45:27 <ttx> geenrally a good time to triage all bugs too
11:45:30 <eglynn> one new high priority bug is the main concern https://bugs.launchpad.net/bugs/1369836
11:45:54 <eglynn> yep, I'll be going all the untriaged bugs
11:46:03 <eglynn> going *over
11:46:33 <eglynn> are you still thinking in terms of end of week for RC1?
11:46:38 <ttx> You build a nice list of RC bugs, all targeted to juno-rc1. Whenever we manage to empty the list, we can generate a release candidate
11:46:50 <ttx> I was more thinking sometimes next week
11:46:55 <eglynn> cool
11:47:09 <eglynn> are the RC1 tags synchronized for all projects?
11:47:16 <ttx> no they aren't
11:47:30 <ttx> some projects have less bugs and want to open kilo faster
11:47:47 <eglynn> a-ha, k, got it
11:47:52 <ttx> the only rule is to have at least one RC before final release
11:48:19 <ttx> to guarantee that, we try to get everyone with an RC1 befor ethe end of month
11:48:34 <eglynn> OK, that makes sense
11:48:45 <ttx> but starting next week, if your bug list is empty, we should tag
11:49:36 <ttx> I'll resurrect the RC burndown chart, hopefully today
11:49:49 <ttx> that wil let us track progress towards RC1 and see if adjustments are needed
11:49:58 <eglynn> right, I'd expect the bug list to grow a bit first as the triage progresses, but yeah lets aim for next week
11:50:27 <ttx> questions on the process ?
11:50:37 <ttx> anything you want to discuss at meeting today?
11:50:53 <eglynn> in parallel, the kilo summit planning will be kicking off, just wondering about your timing expectations on that collaborative scheduling exercise?
11:51:19 <eglynn> in particular pre- or post- PTL elections?
11:51:58 <ttx> hmm, starting next week I should have a slot allocation (i.e. the number of "scheduled" slots we propose for your program, and the length of the "contributors meetup" thing
11:52:19 <eglynn> cool, that'll be a good start
11:52:33 <ttx> we want the new PTLs involved obviously, so final planning happens after election
11:52:52 <ttx> goal is to have a final schedule one week after release
11:52:53 <eglynn> yeah, that's kinda what I'd suspected
11:53:25 <ttx> (10 days before summit)
11:53:33 <eglynn> so in summary, no hard decisions on summit scheduling until after the incoming PTL is confirmed
11:53:37 <ttx> so it's more of an October thing
11:53:40 <eglynn> that makes sense
11:53:42 <ttx> exactly
11:53:54 <ttx> but it's good to open the dumping ground early
11:54:20 <ttx> so that when you think about something you can write it down
11:54:23 <eglynn> cool, we'll discuss at our weekly meeting on Thurs and agree the shared doc format at least
11:54:43 <eglynn> and get a link onto your wiki page
11:55:23 <ttx> I'll write something up soon
11:55:28 <eglynn> cool
11:55:40 <ttx> ok then ttyl
11:55:45 <eglynn> yep, laters
12:07:46 <ttx> dhellmann: sergey will be late, so you can go whenever you are ready
12:12:44 <dhellmann> ttx: here now
12:14:59 <ttx> #topic Oslo
12:15:02 <ttx> dhellmann: hi!
12:15:15 <dhellmann> ttx: good afternoon!
12:15:21 <ttx> https://launchpad.net/oslo/+milestone/next-juno
12:15:37 <ttx> I tagged a last alpha for rootwrap this morning using my script
12:15:48 <ttx> we can tag the final maybe tomorrow
12:16:05 <dhellmann> you don't want to wait and do it thursday with the others?
12:16:26 <ttx> sure, thursday. I thought some of those were being tagged earlier
12:16:31 <ttx> based on your recent announcements
12:16:39 <ttx> so i thought it was ASAP
12:16:53 <ttx> but Thursday is easier for me anyway, so Thursday it is
12:16:58 <dhellmann> I guess we could do some earlier, but I was just planning to do them all at once
12:17:13 <dhellmann> cliff is already a final, but it wasn't using an alpha release irrc
12:17:17 <ttx> should we open stable/juno from those same commits ?
12:17:28 <dhellmann> yes, that makes sense
12:17:44 * ttx thinks the script could also do that for you
12:17:48 <dhellmann> I'd also like to create the appropriate branch in the incubator so we can start cleaning things up
12:17:53 <ttx> but let's do it manually for now
12:18:13 <ttx> dhellmann: when do you want the incubator branch to be created? Thursday too?
12:18:16 <dhellmann> ok, I don't remember if I've ever done that step so I'm not sure how
12:18:24 <dhellmann> yes, thursday is the Big Day :-)
12:18:45 <dhellmann> we have this unicode issue with mask_password to land in the incubator before we branch
12:18:46 <ttx> dhellmann: I know it required a bit of spcial rights, but you may have those
12:18:55 <SergeyLukjanov> ttx, dhellmann, good day
12:19:00 <dhellmann> I wasn't sure of the process
12:19:02 <dhellmann> hi, SergeyLukjanov
12:19:49 <ttx> for reference, to open a branch you can use something like http://git.openstack.org/cgit/openstack-infra/release-tools/tree/rccut.sh#n74
12:20:15 <dhellmann> oh, well, that's easy then
12:20:17 <ttx> probably requires push reference right
12:20:29 <dhellmann> I thought there might be something special to make gerrit take it
12:20:38 <ttx> you ca, also do it directly on gerrit ui
12:20:41 <ttx> can*
12:20:43 <dhellmann> and the branch should be called proposed/juno?
12:21:06 <ttx> depends if it's final juno or not
12:21:19 <ttx> in the case of the incubator ISTR we did stable/juno directly
12:21:37 <dhellmann> ok
12:21:45 <ttx> https://review.openstack.org/#/admin/projects/openstack/oslo-incubator,branches
12:21:50 <dhellmann> and for the libs, should we call it stable/juno or should we use the version numbers
12:21:53 <ttx> that's where the UI for the branch creation is ^
12:22:07 <ttx> if you see "create branch" there you probably can do it
12:22:15 <dhellmann> I don't
12:22:25 <dhellmann> so that's something to work out today
12:22:38 <ttx> i'll be around to do that for you
12:22:41 <ttx> on Thursday
12:22:57 <dhellmann> ok, maybe I'll just let you do it then
12:23:27 <ttx> sure, that's fine
12:23:30 <dhellmann> I have a dentist appointment thursday morning around this time, so I probably won't be tagging releases until a bit later in the morning
12:23:36 <ttx> want to do it on Thursday, or before ?
12:24:03 <ttx> (the oslo-incubator final tag and branch)
12:24:13 <dhellmann> I have one patch I want to make sure we've merged before we cut it
12:24:16 <dhellmann> looking now
12:24:38 <ttx> for oslo.messaging in icehouse we did stable/icehouse
12:24:41 <dhellmann> oh, good, that one merged
12:24:47 <ttx> so I guess we should do stable/juno for oslo.*
12:24:51 <dhellmann> ok, let's stick with that
12:26:03 <dhellmann> the incubator is ready to be branched but it looks like we have one or two other bugs to close before we're completely done
12:26:44 <ttx> for oslo-incubator we can do two ways... tag rc1 and create proposed/juno, or tag 2014.2 and create stable/juno
12:27:10 <ttx> in the first case we would tag 2014.2 on release day and rename proposed/juno to stable/juno then
12:27:23 <ttx> apparently for icehouse, we did the latter
12:28:02 <ttx> tagged rc1 on April 3, created proposed/juno then
12:28:11 <ttx> err. proposed/icehouse I mean
12:28:34 <ttx> then one change was backported on April 9
12:28:47 <ttx> bah, doesn't really matter that much tbh
12:28:51 <dhellmann> that seems fine, we're pretty good at backports
12:29:01 <dhellmann> we've been doing them for graduating modules all cycle
12:29:56 <ttx> basically if we backport something to proposed/juno we'd have to sync it in all consuming projects
12:30:05 <ttx> which is a bit painful
12:30:13 <ttx> (in RC perdiod)
12:30:19 <ttx> period*
12:30:41 <dhellmann> I think last time we only synced to projects that had the issue being fixed
12:30:54 <ttx> yes
12:31:12 <ttx> bah, let's do the incubator at the same time as the libs ? If it's ready then ?
12:31:30 <ttx> and do rc1 / proposed/juno until release ?
12:32:17 <dhellmann> my plan is to start prepping for kilo work right away, because I want to close our kilo work down a little earlier in the cycle
12:32:23 <dhellmann> that means deleting things from the master branch
12:32:42 <ttx> since there is no incubator release, the proposed/stable choice and what tag we use is actually quite irrelevant :)
12:32:42 <dhellmann> so I think it makes just as much sense to call it stable/juno right away, since some backports are going to bypass master
12:32:47 <dhellmann> right
12:33:05 <ttx> right, there is no proposal there.
12:33:14 <dhellmann> I think we're considering the libs "stable" too, so we can go straight to stable/juno for them as well
12:33:17 <ttx> ok, let's do it that way
12:33:21 <ttx> anything else ?
12:33:36 <ttx> some topic for meeting today ?
12:33:44 <dhellmann> that's all I had, I'll ping you when I get back from the dentist thurs to set up the tags
12:33:47 <dhellmann> er, branches
12:34:00 <dhellmann> nothing to add to the meeting
12:34:35 <ttx> dhellmann: ok, thx! ttyl
12:34:49 <ttx> SergeyLukjanov: around?
12:34:53 <SergeyLukjanov> ttx, yup
12:34:54 <dhellmann> thanks, ttx!
12:35:00 <ttx> #topic Sahara
12:35:14 <ttx> https://launchpad.net/sahara/+milestone/juno-rc1
12:35:21 <SergeyLukjanov> client release is now in the gate
12:35:33 <ttx> So your 3 FFEs appear to still be in progress ?
12:35:47 <ttx> two of them being Doc, iirc
12:36:13 <SergeyLukjanov> ttx, doc bp is in progrecc, one is in the gate
12:36:27 <ttx> ok that leaves us with...
12:36:34 <ttx> https://blueprints.launchpad.net/sahara/+spec/edp-swift-trust-authentication
12:36:36 <SergeyLukjanov> and the largest one re trusts for swift auth all the changes are now merged
12:36:55 <SergeyLukjanov> folks doing final testing for it
12:36:59 <ttx> should we mark it implemented then ?
12:37:10 <ttx> if tests reveal bugs that can be addressed using RC bugs ?
12:37:34 <SergeyLukjanov> there are several more actions required
12:37:38 <SergeyLukjanov> in sahara-extra repo
12:38:03 <SergeyLukjanov> probably it's better to keep bp open to show current status
12:38:19 <SergeyLukjanov> but it doesn't require any more changes in sahara repo
12:38:27 <ttx> ok let me document that
12:38:45 <ttx> #info cluster-persist-sahara-configuration gating
12:38:55 <ttx> #info move-rest-samples-to-docs is docs, still in progress
12:39:22 <ttx> #info edp-swift-trust-authentication all sahara changes merged, some remaining work items in sahara-extra
12:39:36 <SergeyLukjanov> ttx, thx
12:39:46 <ttx> SergeyLukjanov: would be great to get those extra items done quickly so you can focus on bugfixing
12:40:08 <SergeyLukjanov> ttx, yeah, I hope it'll be completed this week
12:40:33 <ttx> So after that, focus should be on identifying release-critical bugs, target them all to juno-rc1, assign someone to fix them, fix them all
12:40:37 <ttx> then we can tag RC1
12:40:44 <SergeyLukjanov> ttx, oh, I'm on vacation now and will be travelling tomorrow to CA, so, I'm unable to attend today's project meeting
12:40:55 <ttx> SergeyLukjanov: ok, no problem
12:41:11 <ttx> any question on the release process at this point?
12:41:25 <SergeyLukjanov> ttx, yeah, exactly - we already have some folks who are working on qa
12:41:44 <SergeyLukjanov> ttx, I think no, everything is going ok
12:41:49 <SergeyLukjanov> ttx, thank you
12:42:17 <ttx> SergeyLukjanov: ok, enjoy openstacksv
12:42:36 <SergeyLukjanov> ttx, openstacksv?
12:43:06 <SergeyLukjanov> ttx, oh, OpenStack Silicon Valley
12:43:07 <SergeyLukjanov> heh
12:43:27 <SergeyLukjanov> ttx, I'm going to CA for mirantis internal things
12:44:12 <SergeyLukjanov> and for big data meetup[
13:17:59 <ttx> SergeyLukjanov: ah, ok !
13:59:50 <ttx> jgriffith: ready when you are
14:02:06 <notmyname> ttx: I'm going to leave for openstack SV soon. I won't be online much (any?) for the rest of the day
14:02:22 <ttx> notmyname: ok, anything urgent ?
14:03:05 <ttx> notmyname: I had nothing special on my side
14:03:32 <notmyname> ttx: (1) swiftclient release because now there's a deadline for that. so that will happen this week; (2) I'm still following and concerned about defcore. I'm planning on phoning in to the BoD meeting on thursday
14:03:46 <notmyname> ttx: otherwise, "the usual"
14:03:50 <ttx> notmyname: ok
14:04:09 <notmyname> thanks
14:04:12 <ttx> I'll #topic and #info the client release so it appears in summary
14:04:16 <ttx> #topic Swift
14:04:25 <ttx> #info swiftclient release because now there's a deadline for that. so that will happen this week
14:04:30 <notmyname> heh
14:04:35 <ttx> notmyname: enjoy openstacksv
14:04:42 <notmyname> thanks. talk to you later
14:07:55 <ttx> morganfainberg: ready when you are
14:08:00 <morganfainberg> ttx, o/
14:08:08 <ttx> #topic Keystone
14:08:27 <ttx> So you've completed your FFEs a long time ago
14:08:43 <morganfainberg> yep those are looking good.
14:08:51 <ttx> so the focus now is on identifying the release-critical bugs we need to solve before we can do a release candidate
14:08:56 <ttx> and fixing those
14:09:23 <ttx> morganfainberg: would you say that the current list at https://launchpad.net/keystone/+milestone/juno-rc1 is representative of what you need to fix before release ?
14:09:39 <ttx> Or do you plan to go through reported bugs and increase that list a bit
14:10:05 <morganfainberg> ttx, I hope that is represenatative, but I expect a few more to sneak onto that list.
14:10:23 <morganfainberg> ttx, s/sneak/need to be added
14:10:40 <ttx> right
14:11:00 <morganfainberg> there are a few recent bugs that might need to be added but we've been trying to keep that list up to date as possible.
14:11:14 <ttx> that's the focus on week, test things and make sure we track RC bugs
14:11:23 <ttx> s/on/this/
14:11:45 <morganfainberg> I expect it wont be many more bugs that what is there now.
14:11:48 <ttx> morganfainberg: do you have any question on the process ?
14:12:06 <ttx> morganfainberg: any specific topic you'd like to see discussed at the cross-project meeting later today ?
14:12:11 <morganfainberg> ttx, not off the top of my head.
14:12:23 <ttx> morganfainberg: if you have any, don't hesitate to ping me :)
14:12:24 <morganfainberg> ttx, if anything comes up between now and then I'll let you know.
14:12:27 <morganfainberg> :)
14:12:40 <ttx> ok then, thanks for stepping up, and talk to you later
14:12:45 <morganfainberg> cheers
14:31:38 <ttx> mestery: you can go now if you're around
14:31:46 <ttx> looks like we don't have david or johnG yet
14:31:48 <mestery> ttx: o/
14:31:52 <mestery> Ready and waiting
14:31:53 <ttx> #topic Neutron
14:32:06 <ttx> https://launchpad.net/neutron/+milestone/juno-rc1
14:32:11 <ttx> all ffes set ?
14:32:15 <mestery> Yes, we're all done!
14:32:18 <mestery> 10 merged, I moved one out
14:32:30 <mestery> I plan to scrub bugs today
14:32:56 <ttx> https://review.openstack.org/#/c/120806/ is still up for add-ipset-to-security
14:33:02 <ttx> but I advocated it should be done in K
14:33:13 <mestery> I tend to agree, and will reply on that thread
14:33:47 <ttx> so yeah, this week is identify RC bugs, and get them assigned
14:33:55 <mestery> ttx: Ack on that
14:34:04 <ttx> coming up with a list we can burn down
14:34:19 <mestery> Yes, and prioritizing them as such as well
14:34:21 <ttx> ideally sometimes in the next 2 weeks :)
14:34:31 * mestery hopes to have that done today even. :)
14:34:40 <ttx> I mean burning down the RC1 list
14:34:45 <mestery> Ah ...
14:34:47 <ttx> :)
14:34:49 <mestery> Yes, that will take longer than today ;)
14:35:24 <ttx> I don't think I have anything to add here
14:35:43 <ttx> questions ? topics for cross-project meeting tonight ? anyting blocking you ?
14:36:17 <mestery> I need to talk to mikal about the nova-network deprecation status for Juno
14:36:21 <mestery> Otherwise, nothing else :)
14:36:45 <ttx> mestery: want me to add that as discussion topic for the meeting ? Or would you rater have a 1:1 on that ?
14:36:58 <mestery> ttx: Let me do a 1:1 first, maybe next week we can add that. Sound fair?
14:37:02 <ttx> ack
14:37:08 <ttx> talk to you later!
14:37:12 <ttx> david-lyle: ready?
14:37:18 <mestery> ttx: thanks and later!
14:39:52 <david-lyle> ttx: here
14:39:55 <ttx> #topic Horizon
14:40:03 <ttx> https://launchpad.net/horizon/+milestone/juno-rc1
14:40:08 <ttx> All FFEs in
14:40:27 <ttx> and a nice set of release-critical issues
14:40:39 <ttx> david-lyle: do you think you identified most of them ?
14:40:59 <ttx> (i.e. the target list is somehow representing upcoming RC1 work) ?
14:41:12 <ttx> or do you need to scrub more
14:41:17 <david-lyle> I think we have a good handle on them
14:41:35 <david-lyle> a couple may appear
14:41:51 <ttx> sure
14:42:10 <ttx> one of them is unassigned, but overall you seem to have your team on it
14:42:35 <ttx> david-lyle: any question on the RC1 process ? Any topic for the cross-project meeting today ?
14:43:00 <david-lyle> no questions
14:43:11 <david-lyle> I'll work on an assingee for the last issue
14:43:20 <david-lyle> *assignee
14:43:23 <ttx> david-lyle: ok then, thanks for the sync time, and talk to you later
14:43:27 <david-lyle> later
14:43:38 <ttx> jgriffith: you can go now if you're around
14:49:58 <jgriffith> ttx: cool
14:50:09 <jgriffith> ttx: offer still good?
14:51:13 <ttx> #topic Cinder
14:51:25 <ttx> jgriffith: yes, within the next 8 min :)
14:51:36 <jgriffith> ttx: cool
14:51:36 <ttx> https://launchpad.net/cinder/+milestone/juno-rc1
14:51:42 <ttx> All FFEs implemented
14:51:58 <ttx> did you scrub all bugs to find the release-critical ones ?
14:52:06 <ttx> I see you have a sane list aleady
14:52:07 <jgriffith> started, not completed
14:52:31 <ttx> OK, well, that's the objective for this week, identify all known issues taht would be release-critical
14:52:39 <jgriffith> ttx: on it
14:52:49 <ttx> then get people assigned to those and then get them all fixed and then RC1
14:52:59 <ttx> jgriffith: any question on that process ?
14:53:04 <ttx> jgriffith: anything blocking you ?
14:53:09 <jgriffith> good thing is most items already have someone working/assigned
14:53:13 <ttx> jgriffith: any topic for the cross-project meeting today?
14:53:22 <jgriffith> no topics for the meeting
14:53:34 <jgriffith> ttx: do we want to set a timeline today?
14:53:42 <jgriffith> ttx: or just shooting for RC next week?
14:53:44 <ttx> timeline for.. rc1?
14:53:50 <jgriffith> ttx: yeah, rc1
14:54:05 <ttx> the window would be Sep 22-31
14:54:23 <jgriffith> Oh.. same is published... never mind
14:54:25 <ttx> sounds like the sweet spot
14:54:48 <jgriffith> Yeah, I think that's going to line up just about right
14:54:50 <ttx> but really, the idea is to tag when you're done with known issues and want to start working on kilo :)
14:54:54 <jgriffith> ttx: ok... thanks
14:55:18 <ttx> if you still have 30 bugs opened next week, we migth want to work on culling the list
14:55:26 <ttx> and start documenting known issues :)
14:55:32 <jgriffith> ttx: I'm goign to work on it this week for sure
14:55:46 <ttx> jgriffith: sounds good
14:55:50 <jgriffith> ttx: there's also sure to be "more" coming along
14:56:07 <ttx> yes, the curve tends to go up in the first days of rc1 bug tracking
14:56:12 <ttx> that's fine :)
14:56:23 <jgriffith> ttx: yeah... and I've lost control of drivers at this point :(
14:56:34 <jgriffith> anyway...
14:56:36 <ttx> havana was like this: http://ttx.re/images/havana-rcs.png
14:56:55 <jgriffith> :)
14:56:57 <ttx> I restarted tracking @ http://old-wiki.openstack.org/rc/
14:57:04 <jgriffith> ttx: this is where the fun starts IMO
14:57:17 <ttx> ok then, talk to you later!
14:57:26 <jgriffith> ttx: thanks
14:57:28 <jgriffith> cya
15:43:32 <zaneb> o/ I'm awake
15:47:17 <ttx> zaneb: o/
15:47:22 <ttx> #topic Heat
15:47:31 <ttx> https://launchpad.net/heat/+milestone/juno-rc1
15:47:44 <zaneb> it's better than it looks ;)
15:47:51 <ttx> So it looks like you still have 4 FFEs open
15:47:56 <ttx> I hope so!
15:48:09 * ttx puts back the baseball bat under the desk
15:48:30 <zaneb> the first one is basically done for our purposes
15:48:44 <zaneb> cfn-api support hasn't merged yet, but I don't care about that
15:49:07 <zaneb> the Sticky parameters one has one patch still in the gate currently
15:49:22 <zaneb> it would have merged last night except there was a random Neutron failure
15:49:24 <ttx> zaneb: so the first one could technically be marked "implemented" ?
15:49:58 <zaneb> ttx: I guess it could, although _technically_ there is still one patch left to merge
15:50:12 <ttx> zaneb: how far is that patch?
15:50:21 <zaneb> also client support, but that is on a different release schedule
15:50:51 <ttx> sticky parameters, if the final patch is gating, we can let it in
15:50:57 <zaneb> it's pretty close, but the return value is wrong w.r.t. CloudFormation
15:51:16 <zaneb> yep, agree on the sticky parameters
15:51:43 <zaneb> the snapshot/rollback was a late addition
15:51:49 <ttx> so you could consider that last cancel-update-stack patch as a RC bug I guess
15:51:50 <zaneb> because most of it had already merged
15:52:06 <zaneb> ok
15:52:12 <ttx> I'm just concerned you guys can't fully focus on bugfixing because you are distracted with those last patches
15:52:25 <ttx> and it's way past that moment in the cycle now
15:52:40 <ttx> I guess 2 patches is fine, 5..
15:52:58 <zaneb> yeah, I think we should wrap these up now
15:53:10 <ttx> so we keep the first two and defer the last two ?
15:53:31 <ttx> I think that's a good compromise -- complete features that are 90% in
15:53:33 <zaneb> basically yeah
15:53:49 <zaneb> and actually the third one, half of it merged already before FF
15:53:59 <zaneb> so we got something in
15:54:13 <zaneb> it's somewhat useful without the rest
15:54:16 <ttx> zaneb: how wrong does it look if it stays that way up to release ?
15:54:28 <zaneb> I'm OK with it
15:54:32 <ttx> ok
15:54:41 <zaneb> basically we have snapshot but not rollback yet
15:54:43 <ttx> ok, let's keep the first two and defer the last two
15:54:51 <ttx> and switch everyone to bugfixing asap
15:54:52 <zaneb> +1
15:55:29 <ttx> is the rc1 list somehow representative of your release-critical bugs, or is there more work needed to compile a good list ?
15:56:04 <zaneb> I scrubbed the list a couple of weeks back and didn't see anything major languishing
15:56:16 <ttx> #info FFE maintained for to finalize cancel-update-stack & troubleshooting-low-level-control
15:56:27 <zaneb> I should probably go through it again, but it should be reasonably representative I think
15:56:42 <ttx> #info Defer handle-update-for-security-groups and stack-snapshot to kilo
15:56:47 <ttx> zaneb: ok good
15:57:22 <ttx> so yeah, now focus on identifying release blockers, get someone to fix them, fix them all
15:57:30 <ttx> then we can tag rc1 and open kilo
15:57:40 <ttx> hopefully all within the next two weeks
15:57:43 <zaneb> it sounds so easy when you put it like that ;)
15:57:54 <ttx> easy peasy. Benn doing that a few times
15:57:59 <ttx> Been*
15:58:13 <ttx> zaneb: questions on the process at this point ?
15:58:24 <ttx> zaneb: any topic you want to discuss at cross-project meeting today?
15:58:41 <zaneb> nope, I think I'm ok
15:58:55 <ttx> zaneb: great, talk to you later then
15:58:58 <ttx> markwash__: o/
15:59:02 <zaneb> cool, thanks ttx
15:59:07 <markwash__> ttx: ahoy hoy
15:59:08 <ttx> #topic Glance
15:59:48 <ttx> https://launchpad.net/glance/+milestone/juno-rc1
15:59:56 <ttx> one FFE still up:  	refactoring-glance-logging
16:00:03 <ttx> what's up with that ?
16:00:25 <markwash__> ttx: it is in a mostly great state, we had a little disagreement about the appropriate log levels
16:00:46 <markwash__> there was an overwhelming consensus on the ML though so I think we're one new patchset away from landing it
16:00:51 <ttx> markwash__: how far is it from merging ? We need to switch focus to full bugfixing now
16:01:23 <markwash__> ttx: I expect middle-late this week
16:01:46 <ttx> how much of your bugfixing resources does this tie up?
16:02:04 <ttx> You don't have any RC bug on your list yet :)
16:02:15 <markwash__> yeah I was just looking through the high bugs
16:02:21 <ttx> not sure it's because you're perfect, or because you didn't have time to compile a list :)
16:02:22 <markwash__> we had a bug day and I didn't find anything that looked super blocky
16:02:55 <ttx> well, as long as you don't have any RC bug, I'd say you can have a few more days to merge that logging thing
16:03:03 <markwash__> we're fairly untriaged so I was really looking for bombs though--I would probably increase my sensitivity if there weren't so many "NEW" to worry about
16:03:31 <ttx> but if that means your core team doesn't have time to scrub bug reports because it's still reviewing a featury thing... let's kill it
16:04:11 <markwash__> ttx I don't think it will take that much time o:-)
16:04:36 <ttx> markwash__: ok, let's keep it
16:04:39 <ttx> for the rest of the week
16:04:57 <ttx> #info FFE maintained for refactoring-glance-logging
16:05:34 <ttx> but you need to get those NEW bugs checked and do some testing of the new features
16:05:48 <ttx> so we are reasonably sure we aren't overlooking a big issue
16:06:01 <ttx> markwash__: does that sound like a good deal ?
16:06:04 <markwash__> yes
16:06:19 <ttx> ok then -- question on anything ? Topics for the meeting today ?
16:06:33 <markwash__> only the ever-present existential questions
16:06:53 <ttx> the answer would be 42
16:07:07 <markwash__> hmm, yeah actually the math checks out
16:07:07 <ttx> markwash__: ok then, talk to you later!
16:07:17 <markwash__> ttx: thanks! see you then
16:07:35 <ttx> fWIW we are skipping Trove this week, will sync via email
16:07:38 <ttx> #endmeeting