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