| *** markmcclain has joined #openstack-relmgr-office | 00:49 | |
| *** markmcclain has quit IRC | 01:16 | |
| *** morganfainberg is now known as morganfainberg_Z | 01:30 | |
| *** david-lyle has joined #openstack-relmgr-office | 01:42 | |
| *** morganfainberg_Z is now known as morganfainberg | 01:49 | |
| *** morganfainberg is now known as morganfainberg_Z | 02:08 | |
| *** morganfainberg_Z is now known as morganfainberg | 03:52 | |
| *** morganfainberg is now known as morganfainberg_Z | 08:34 | |
| *** johnthetubaguy has joined #openstack-relmgr-office | 09:17 | |
| *** johnthetubaguy has quit IRC | 09:20 | |
| *** johnthetubaguy has joined #openstack-relmgr-office | 09:22 | |
| *** johnthetubaguy1 has joined #openstack-relmgr-office | 09:39 | |
| *** johnthetubaguy has quit IRC | 09:41 | |
| *** david-lyle has quit IRC | 11:46 | |
| ttx | dhellmann: hi! | 12:15 |
|---|---|---|
| dhellmann | ttx: hi! | 12:15 |
| dhellmann | I hope you enjoyed your vacation :-) | 12:15 |
| ttx | I did! Almost maanged to stay offline all week | 12:16 |
| ttx | https://launchpad.net/oslo/+milestone/icehouse-rc1 | 12:16 |
| dhellmann | :-) | 12:16 |
| ttx | Did you recently drop oslo-db-lib ? | 12:16 |
| dhellmann | I did -- I don't want them to cut that new library out until we are sure we are done with critical fixes in the db code, so we don't miss anything. | 12:17 |
| ttx | Great | 12:17 |
| dhellmann | and I don't want to impose the stable branch process yet | 12:17 |
| ttx | Looking at the bugs side | 12:17 |
| dhellmann | so I moved that one to j1 | 12:17 |
| ttx | i want to get 1081795 fixed before I tag a new oslo.rootwrap | 12:18 |
| ttx | any other known bugs in the libs that we'd like to fix pre-release ? | 12:18 |
| dhellmann | ok | 12:18 |
| ttx | oslo.messagign has 1288425 | 12:18 |
| dhellmann | I see 1 change in nova, but I don't see the rootwrap change in oslo | 12:19 |
| dhellmann | the messaging change should be merging today, I just approved it | 12:19 |
| ttx | If we only have two issues in all oslo libs it looks quite good | 12:19 |
| ttx | is it true though ? | 12:19 |
| dhellmann | I've been looking over https://review.openstack.org/#/q/status:open+project:openstack/oslo-incubator,p,002ba72700012968 to try and tell | 12:20 |
| ttx | dhellmann: that's the oslo.rootwrap fix: https://review.openstack.org/#/c/72093/ | 12:20 |
| ttx | we need to revive it | 12:20 |
| dhellmann | ah | 12:21 |
| ttx | I don't have "restore change", asked Dirk to resurrect it | 12:21 |
| ttx | but he hasn't yet | 12:21 |
| ttx | should I just repush it ? | 12:21 |
| dhellmann | yeah, that seems fair | 12:21 |
| dhellmann | I guess I don't have a way to revive it directly, either | 12:21 |
| dhellmann | oh, it may just need a reverify, did you look at why it failed to merge? | 12:22 |
| ttx | no idea if repuhsing it with same changeID will do the trick | 12:22 |
| * dhellmann needs a gerrit view for failed merges | 12:22 | |
| ttx | dhellmann: the tests fail on borked images from March 6 | 12:23 |
| sdague | dhellmann: https://review.openstack.org/#/q/Verified-2,n,z | 12:23 |
| dhellmann | sdague: thanks! | 12:23 |
| sdague | not perfect, but you can search on those columns sanely | 12:24 |
| dhellmann | ttx: if there's a bug for that, we could just reverify that change | 12:24 |
| ttx | dhellmann: hmm failure is a bit unclear | 12:24 |
| dhellmann | ttx: yeah, that may take a while to work out | 12:25 |
| jd__ | you can't push on an abandoned changeset AFAIK | 12:25 |
| jd__ | you need to use a new Change-Id | 12:25 |
| dhellmann | recheck doesn't work either | 12:25 |
| ttx | devstacklog looks like it was just interrupted | 12:26 |
| ttx | which is why I planned to recheck | 12:26 |
| ttx | anyway | 12:26 |
| ttx | will repush it if Dirk doesn't do it soon | 12:26 |
| dhellmann | ok | 12:26 |
| ttx | dhellmann: wanted to attract your attention to the Dependency freeze discussion planned for the meeting later | 12:27 |
| dhellmann | I'm going to be 15-20 minutes late to the release meeting :-/ | 12:27 |
| ttx | we need to work out if/how we should freeze internal deps like oslo libs | 12:28 |
| * ttx should add a link to the agenda | 12:28 | |
| dhellmann | ok, I would have expected us to do the same thing we do with 3rd party libs, maybe a little more liberal about accepting patch releases | 12:28 |
| ttx | right | 12:29 |
| ttx | anything else you'd like to discuss at meeting ? | 12:29 |
| dhellmann | not for today | 12:30 |
| dhellmann | like I said, I'm going to have to be a little late, but I'll try to be back as quickly as possible -- something unexpected came up | 12:30 |
| ttx | ok | 12:31 |
| ttx | will try to discuss RC1 until you arrive :) | 12:31 |
| dhellmann | ttx: thanks :-) | 12:31 |
| ttx | jd__: if you're around, you may steal mark's spot, he is delayed | 12:32 |
| jd__ | ttx: présent | 12:32 |
| ttx | jd__: https://launchpad.net/ceilometer/+milestone/icehouse-rc1 | 12:32 |
| ttx | FFE still in progress (?): https://blueprints.launchpad.net/ceilometer/+spec/vmware-vcenter-server | 12:32 |
| jd__ | no, forgot to change the status | 12:33 |
| jd__ | just fixed :) | 12:33 |
| ttx | https://review.openstack.org/#/c/80314/ should be turned into a bugfix then | 12:33 |
| ttx | or dropped | 12:33 |
| ttx | looks like it alters behavior | 12:34 |
| jd__ | I'll add a comment | 12:35 |
| ttx | About the RC1 buglist... is it the complete list of bugs you want to fix before release ? | 12:35 |
| ttx | i.e. all known release-critical issues ? | 12:36 |
| ttx | looks a bit.. slim | 12:36 |
| jd__ | so far I think so | 12:37 |
| jd__ | though I admit I didn't browse all the bugs | 12:37 |
| jd__ | I count on my fellow core developers to handle part of that job ;) | 12:37 |
| ttx | OK, would be good to go through them and produce a more "final" buglist asap | 12:37 |
| ttx | since we'll use it to decide when it's "ready" | 12:37 |
| ttx | anything you'd like to discuss at meeting tonight ? | 12:38 |
| jd__ | nop | 12:38 |
| ttx | ok then, see you later | 12:39 |
| jd__ | see ya :) | 12:39 |
| jgriffith | ttx: did we swap times? | 12:52 |
| ttx | you're one hour later UTC | 12:53 |
| ttx | but i can do you now | 12:53 |
| jgriffith | ttx: yay for me... and sure, since I'm here | 12:53 |
| jgriffith | I thought you rolled everything back | 12:53 |
| ttx | ok, let's do this | 12:53 |
| ttx | err.. you are at 13:45 UTC | 12:54 |
| jgriffith | ttx: fair warning/disclosure I'm behind in my triage | 12:54 |
| ttx | so same time UTC, one hour later US | 12:54 |
| ttx | at your request | 12:54 |
| ttx | but let's do it now | 12:54 |
| jgriffith | yes,,, I'm with ya, thanks! | 12:54 |
| ttx | https://launchpad.net/cinder/+milestone/icehouse-rc1 | 12:54 |
| jgriffith | didn't know my request worked out :) | 12:54 |
| ttx | https://blueprints.launchpad.net/cinder/+spec/prophetstor-dpl-driver | 12:55 |
| *** markmcclain has joined #openstack-relmgr-office | 12:55 | |
| ttx | I think it moved back to rc1 | 12:55 |
| jgriffith | yes it seems so | 12:55 |
| jgriffith | he moved it again after my email | 12:55 |
| ttx | If it's ready to go in and you want to have it in, I'm fine with it | 12:55 |
| jgriffith | honestly I don't really care about it at all | 12:55 |
| ttx | if it takes time and distracts from bugfixing, then no | 12:56 |
| jgriffith | but others are rightfully annoyed | 12:56 |
| ttx | yes, I get the "no exception" benefit | 12:56 |
| ttx | I think it's easier to justify than the other way around | 12:56 |
| jgriffith | justify the exception you mean? | 12:56 |
| ttx | it's easier to say "no exception" than "exception but only for X" | 12:57 |
| jgriffith | ahh... yes I agree | 12:57 |
| jgriffith | I'll see if he convinces others tomorrow | 12:57 |
| jgriffith | after that I'm putting it to bed til Juno | 12:57 |
| jgriffith | I don't mind giving him 5 minutes of meeting time | 12:58 |
| ttx | jgriffith: OK, also if it needs more review rounds I'd also deny it as distracting from pressing bugfixing duties | 12:58 |
| jgriffith | agreed | 12:58 |
| ttx | ok | 12:58 |
| jgriffith | and that was my last comment to him via review | 12:58 |
| ttx | let's keep it on the slate until tomorrow | 12:58 |
| jgriffith | more than fair | 12:58 |
| ttx | Buglist | 12:58 |
| ttx | You have two unassigned bugs in there | 12:58 |
| jgriffith | I'll likely take them | 12:59 |
| jgriffith | 1289931 is actually by design | 12:59 |
| ttx | also you mentioned being behind on triage, does that mean the list is not complete yet ? | 12:59 |
| jgriffith | correct :( | 12:59 |
| ttx | OK... ideally the first RCs will appear starting next week, so getting that list nailed down is pretty critical at this point | 13:00 |
| jgriffith | I can do that | 13:00 |
| jgriffith | for sure | 13:00 |
| jgriffith | I've glanced over them and it's not looking too bad | 13:00 |
| jgriffith | if you get rid of the "python 3" BS | 13:00 |
| ttx | also feel free to remove anything "nice to have" and only list "need to have" bugfixes | 13:00 |
| jgriffith | Yes, I've already started dropping the hammer so to speak this week | 13:01 |
| ttx | "nice to have" will be included by the natural review process if someone cares enough to fix them | 13:01 |
| jgriffith | it will continue to get more difficult for people | 13:01 |
| ttx | i.e. everybody can fix the bugs they want | 13:01 |
| ttx | we just need to track how far we are from RC1 | 13:02 |
| jgriffith | understood... let the review process sort it | 13:02 |
| jgriffith | Yep, I'll have it in good shape by tonight | 13:02 |
| ttx | ok great | 13:02 |
| jgriffith | assuming the input slows | 13:02 |
| jgriffith | which it seems to have over the past couple of days | 13:02 |
| ttx | ok, anything you'd like to discuss at meeting ? | 13:03 |
| jgriffith | The only things I had were the SSL cert and the Shares security issues | 13:03 |
| jgriffith | I'm still playing with those | 13:03 |
| jgriffith | but I think they may have to wait til Juno | 13:03 |
| ttx | ok | 13:03 |
| jgriffith | Other than that no | 13:03 |
| ttx | ok then, talk to you later! | 13:04 |
| ttx | markmcclain: o/ | 13:04 |
| jgriffith | ttx: thanks... and thanks for swapping my time | 13:04 |
| ttx | markmcclain: you around ? | 13:08 |
| markmcclain | ttx: yes | 13:20 |
| ttx | o/ | 13:21 |
| ttx | markmcclain: https://launchpad.net/neutron/+milestone/icehouse-rc1 | 13:21 |
| ttx | So, time to drop the hammer as jgriffith would say | 13:22 |
| ttx | You deferred port-region already | 13:22 |
| markmcclain | yes and I'm in the process of moving v6 BPs out too | 13:22 |
| ttx | ipv6-two-attributes looks merged, can I mark the BP implemented ? | 13:22 |
| markmcclain | well it's half implemented | 13:23 |
| markmcclain | and I'm likely to revert it | 13:23 |
| ttx | OK, so you defer everything ? | 13:23 |
| markmcclain | this is one item.. I'd like to still merge: https://blueprints.launchpad.net/neutron/+spec/ml2-deprecated-plugin-migration | 13:23 |
| ttx | that's the upgrade script right | 13:24 |
| markmcclain | yep…it holds no functional risk since it is a one time item | 13:24 |
| ttx | rigth, that one is fine. | 13:24 |
| ttx | also probably not something that generates too much review distraction | 13:24 |
| ttx | so let's defer all but this one | 13:24 |
| ttx | and then focus on bugfixes | 13:25 |
| markmcclain | makes sense | 13:25 |
| markmcclain | one cross project item.. I think there was an FFE for v6 work in Horizon | 13:26 |
| ttx | about ml2-deprecated-plugin-migration: would still be good to merge it before end of week though, to reduce doc impact | 13:26 |
| markmcclain | that should now be deferred | 13:26 |
| ttx | markmcclain: i'll tell david | 13:26 |
| markmcclain | I expected it to merge yesterday because we had 2 cores verbally +2 | 13:26 |
| markmcclain | had another reviewer look at it and he -1'd | 13:27 |
| ttx | can I help you defer ? Or are you on it ? | 13:28 |
| markmcclain | I'll defer the items | 13:29 |
| ttx | ok | 13:29 |
| ttx | RC1 buglist now | 13:29 |
| markmcclain | yes.. it is too large | 13:29 |
| ttx | I think at this point you need to only list "must fix" bugs, rather than everything everyone plans to work on | 13:30 |
| markmcclain | I told the team yesterday that anything not critical or high would be moved out | 13:30 |
| ttx | the "nice to haves" will get into master alright using the natural review process | 13:30 |
| ttx | we need that list to reflect progress towards the creation of the RC | 13:30 |
| ttx | i.e. only release-critical bugs | 13:30 |
| ttx | and all known release-critical bugs :) | 13:30 |
| markmcclain | yeah… the most concerning bug to me is: https://bugs.launchpad.net/bugs/1283522 | 13:31 |
| ttx | Also no bug in the list shall be unassigned | 13:31 |
| ttx | (can temporarily be unassigned until you discuss assignment, but can't stay that way) | 13:31 |
| markmcclain | we introduced a regression on 14th and we're trying to get to the bottom vs reverting | 13:31 |
| markmcclain | right they should all have assignments right now | 13:32 |
| ttx | so in summary, now that FFEs are out of the way, the key focus from release management perspective is to get a sane, complete list of known RC issues | 13:33 |
| ttx | so that we can project RC1 dates from burndown rates | 13:33 |
| ttx | removing nice to have and adding missing must-have is therefore key | 13:34 |
| markmcclain | right | 13:34 |
| ttx | if you need help clicking LP just ask me | 13:34 |
| markmcclain | I'm guessing the ideal cut date for the RC is early next week? | 13:34 |
| ttx | ideal date is "next week" | 13:34 |
| markmcclain | ok | 13:35 |
| ttx | we should have most RCs done by the end of next week | 13:35 |
| markmcclain | ok barring any other last minute regression, I think that is doable for us | 13:36 |
| ttx | so the sooner we have a sane list to work from, the better | 13:36 |
| ttx | that's all I have | 13:36 |
| ttx | anything for the meeting later ? | 13:37 |
| markmcclain | ok… I'll refine the buglist further | 13:37 |
| markmcclain | no I don't have anything new | 13:37 |
| ttx | we'll have a quick look at refined buglists during the meeting | 13:37 |
| ttx | and then probably on Thursday | 13:37 |
| ttx | to check progress | 13:38 |
| ttx | markmcclain: cheers! | 13:38 |
| markmcclain | sounds good.. sorry on the train delay | 13:38 |
| dolphm | ttx: o/ | 13:59 |
| ttx | dolphm: o/ | 14:00 |
| ttx | https://launchpad.net/keystone/+milestone/icehouse-rc1 | 14:01 |
| ttx | no FFE | 14:01 |
| ttx | How "complete" is your RC1 buglist ? | 14:02 |
| ttx | Did you go through all known bugs to build it ? | 14:02 |
| dolphm | it's one short afaik | 14:02 |
| dolphm | not *all* known bugs, but everything reported during icehouse for sure | 14:02 |
| ttx | OK great | 14:03 |
| dolphm | our keystone meeting today will be mostly focused on sharing the bug load https://wiki.openstack.org/wiki/Meetings/KeystoneMeeting | 14:03 |
| ttx | 1291157 has no assignee | 14:03 |
| ttx | 1293781 is assigned to a group | 14:03 |
| ttx | Otherwise looks good and could make for a quick RC1 | 14:03 |
| dolphm | that one is first on the agenda, i suspect it may not be an RC blocker, but we need to discuss | 14:03 |
| ttx | OK, just make sure you get them all assigned, keep the list current with new stuff being reported... and burn the list down | 14:04 |
| dolphm | the group assignment is intentional, we just created it as a reminder to ourselves | 14:04 |
| ttx | dolphm: anything for the meeting later ? | 14:04 |
| dolphm | nope! | 14:04 |
| ttx | dolphm: ok then, talk to you later | 14:07 |
| dolphm | ttx: /salute | 14:07 |
| *** johnthetubaguy1 is now known as johnthetubaguy | 14:13 | |
| ttx | russellb: oh. missed our time | 14:28 |
| ttx | russellb: you around ? | 14:28 |
| russellb | ttx: oops,s orry | 14:28 |
| russellb | ttx: yes | 14:28 |
| russellb | johnthetubaguy: ping | 14:28 |
| russellb | and tjones not on yet looks like | 14:28 |
| johnthetubaguy | hey | 14:28 |
| johnthetubaguy | was the time not set in UTC for this one? | 14:29 |
| russellb | johnthetubaguy: oh sorry, it is, but not this week and next | 14:29 |
| russellb | johnthetubaguy: because ... DST mass confusion | 14:29 |
| johnthetubaguy | russellb: no problem | 14:29 |
| ttx | https://launchpad.net/nova/+milestone/icehouse-rc1 | 14:29 |
| ttx | https://blueprints.launchpad.net/nova/+spec/smarter-network-cache-update | 14:30 |
| russellb | i keep trying to ping arosen on that one | 14:30 |
| russellb | trying to figure out if the important stuff is done already and should just be marked implemented | 14:30 |
| johnthetubaguy | some abandoned patches, one remaining | 14:30 |
| russellb | dansmith: you have any idea on that? since you've been in nova+neutron land lately | 14:30 |
| ttx | russellb: a bit concerned with this last patch being WIP | 14:31 |
| dansmith | russellb: I need to go look at the outstanding things, there are several that he has up and I don't know which apply to that | 14:31 |
| dansmith | I thought we merged the important bits, | 14:31 |
| russellb | ok, well let's get this sorted asap | 14:31 |
| dansmith | and that the pending patches are fixes for that | 14:31 |
| russellb | either marked implemented if appropriate, or deferred | 14:31 |
| dansmith | I can try to catch up with him today | 14:31 |
| ttx | russellb: at this point I would only accept it if it could be considered a bug | 14:31 |
| russellb | k, that'd be great | 14:31 |
| russellb | ttx: agreed | 14:31 |
| ttx | i.e. feature completed but gap needing to be addressed | 14:32 |
| russellb | the other blueprint, rpc versioning, has 1 patch left to merge and then it's done | 14:32 |
| ttx | https://blueprints.launchpad.net/nova/+spec/rpc-major-version-updates-icehouse -> when do you want to push that one ? Last thing before RC1 ? | 14:32 |
| dansmith | russellb: need another +A on that or something? | 14:32 |
| ttx | or forst thing after formal FFE | 14:32 |
| johnthetubaguy | I +2ed that just now | 14:32 |
| russellb | dansmith: updated last night to fix another typo | 14:32 |
| ttx | formal FF* | 14:32 |
| dansmith | russellb: on its way | 14:33 |
| russellb | dansmith: johnthetubaguy thanks! | 14:33 |
| russellb | ttx: k, in the gate :) | 14:33 |
| ttx | ack | 14:33 |
| russellb | johnthetubaguy: dansmith we have to watch out for how rpc changes are done while the code supports 2 versions, it's a bit more tricky | 14:33 |
| ttx | OK so.. RC1 buglist | 14:34 |
| ttx | your list looks curated enough | 14:34 |
| russellb | we've been pretty strict with the list so far | 14:34 |
| ttx | would you say it's complete (as in: reflects all known blockers) ? | 14:34 |
| russellb | yes | 14:34 |
| russellb | from my POV | 14:34 |
| ttx | cool | 14:34 |
| ttx | ideally we'll cut a RC1 (and open Juno) sometimes next week | 14:35 |
| russellb | that'd be awesome | 14:35 |
| dansmith | woo | 14:35 |
| ttx | but then I don't really want to open a RC2 window the next day | 14:35 |
| russellb | right.. | 14:35 |
| ttx | so we'll try to respect the RC1 buglist | 14:35 |
| russellb | at least they're all in progress | 14:36 |
| ttx | and cut when no RC bug is there | 14:36 |
| *** david-lyle has joined #openstack-relmgr-office | 14:36 | |
| ttx | russellb: ok, you seem to have stuff under control | 14:36 |
| ttx | anything you'd like to discuss at meeting later ? | 14:36 |
| russellb | johnthetubaguy: good comment on https://bugs.launchpad.net/nova/+bug/1291741 ... seems like we should drop that from the list | 14:36 |
| russellb | ttx: don't think so | 14:36 |
| ttx | russellb: OK then. talk to you later | 14:37 |
| johnthetubaguy | russellb: yeah, just going through that list | 14:37 |
| russellb | ttx: maybe give props to the guys who seem to have squashed the top gate bug | 14:37 |
| russellb | the "ssh bug" | 14:37 |
| ttx | oh! missed that | 14:37 |
| ttx | I'll let you mention it inmeeting :) | 14:38 |
| ttx | david-lyle: around? | 14:38 |
| david-lyle | ttx: here | 14:38 |
| ttx | https://launchpad.net/horizon/+milestone/icehouse-rc1 | 14:38 |
| ttx | no more FFEs running | 14:38 |
| ttx | massive RC1 buglist could use some refinement | 14:38 |
| david-lyle | agreed | 14:39 |
| ttx | david-lyle: the RC1 buglist should ideally only list blockers (other bugfixes can make it in through the natural review process) | 14:39 |
| ttx | i.e. only "MUST fix", not "would be NICE to fix" | 14:39 |
| david-lyle | ok, makes sense, will prune down | 14:39 |
| ttx | Also ideally it should only contain assigned bugs | 14:39 |
| ttx | the idea is that we track progress until we can cut a release candidate that doesn't look too bad | 14:40 |
| ttx | (there will always be bugs, the RC buglist is a mechanism to decide when "good enough" is) | 14:40 |
| ttx | so if we keep nice to haves in there, it's never finished | 14:40 |
| david-lyle | so other bug fixes can go in, we just don't need to track them as RC1 critical | 14:41 |
| ttx | right | 14:41 |
| ttx | we get stricter after RC1 | 14:41 |
| ttx | but for RC1, any bugfix can go in | 14:41 |
| ttx | and when we get down to 0 RC bugs, we tag | 14:41 |
| david-lyle | alright, I understand now. I think we are low on blocking issues | 14:41 |
| david-lyle | I'll try to have a real list by this afternoon | 14:41 |
| ttx | cool, thx | 14:41 |
| ttx | you can use a tag to track nice-to-hace ones if necessary | 14:42 |
| ttx | david-lyle: markmcclain mentioned that the neutron thing you were waiting on... was deferred. But i don't think you were waiting on that at this point ? | 14:43 |
| david-lyle | no, heard it wasn't close by the end of last week, so we dropped it | 14:43 |
| ttx | david-lyle: ack | 14:44 |
| ttx | david-lyle: anything you'd like to discuss at meeting later ? | 14:44 |
| david-lyle | I think my biggest issue isn't for this afternoon but probably the summit | 14:45 |
| david-lyle | keystone v3 support | 14:45 |
| ttx | hmm, yes, Juno material | 14:45 |
| david-lyle | we have support in Horizon, but you can't use a v3 token to do anything else in OpenStack | 14:45 |
| david-lyle | alright, I'll propose a cross project session if there isn't one already | 14:46 |
| ttx | david-lyle: i think it's generally a "use latest APIs" cross-project discussion | 14:46 |
| ttx | also affects glance | 14:46 |
| david-lyle | otherwise, I'm good | 14:47 |
| *** tjones has joined #openstack-relmgr-office | 14:57 | |
| *** tjones_ has joined #openstack-relmgr-office | 15:20 | |
| *** tjones_ has quit IRC | 15:21 | |
| *** tjones has quit IRC | 15:22 | |
| *** tjones has joined #openstack-relmgr-office | 15:23 | |
| *** tjones is now known as tjones-phone | 15:23 | |
| notmyname | ttx: good morning/day to you | 15:30 |
| ttx | notmyname: hi! | 15:30 |
| notmyname | ttx: this is the right time, right? | 15:30 |
| ttx | it is! | 15:30 |
| ttx | https://launchpad.net/swift/+milestone/next-icehouse | 15:30 |
| notmyname | gret! | 15:30 |
| ttx | how is your next release / our common release shaping up ? | 15:31 |
| *** tjones-phone has quit IRC | 15:31 | |
| notmyname | ...good. sorry for the delay. trying to figure out the best way to answer that :-) | 15:32 |
| notmyname | we'll be having the 1.14 release for the Icehouse RC | 15:32 |
| ttx | heh | 15:32 |
| notmyname | ie in that timeframe | 15:32 |
| notmyname | that LP page is wildly inaccurate | 15:32 |
| notmyname | and so it looks like I need to spend some time there | 15:33 |
| ttx | So.. targeting sometimes between March 25 and April 10 | 15:33 |
| ttx | leaving enough time to iterate on RCs before final on April 17 | 15:33 |
| notmyname | I'll be sending an email to the -dev mailing list probably later this week about swift 1.14 | 15:33 |
| notmyname | yes to that timeframe | 15:33 |
| ttx | notmyname: if you want I can create a 1.14.0-rc1 milestone page | 15:34 |
| ttx | or just rename the next-icehouse one | 15:34 |
| notmyname | ttx: not yet. let me look at it first. it may end up being 1.13.1. That's what I need to check on | 15:34 |
| ttx | ok | 15:35 |
| ttx | probably renaming is the right step, as we don't expect another next-icehouse | 15:35 |
| notmyname | :-) | 15:35 |
| notmyname | makes sense | 15:35 |
| ttx | just potentially a -rc2 to ctach some release critical last-minute issue | 15:35 |
| notmyname | right | 15:36 |
| *** markwash has joined #openstack-relmgr-office | 15:36 | |
| notmyname | I don't have anything for the meeting today | 15:36 |
| ttx | i suspect that question ties into the definition of the feature content for that release | 15:36 |
| ttx | (the adequate version number) | 15:36 |
| notmyname | correct | 15:36 |
| ttx | notmyname: when do you expect to have the goals defined ? | 15:37 |
| notmyname | ttx: actually, I have a really good idea right now, but I need to talk with the other core devs before saying anything in public :-) | 15:37 |
| ttx | hah! | 15:37 |
| notmyname | that's what I have to do as soon as I get to the office today! :-) | 15:38 |
| ttx | notmyname: ok. As a heads-up, we'll discuss dependency freezing tonight, and I'd love to get the swift perspective on it | 15:38 |
| ttx | i.e. if and when you could participate to that | 15:38 |
| notmyname | ok, cool. is there some background to read up on first? | 15:38 |
| ttx | mostly packagers asking that we stop adding new deps as we get nearer to release | 15:38 |
| ttx | http://lists.openstack.org/pipermail/openstack-dev/2014-March/030277.html | 15:39 |
| notmyname | ok (yup, one of the 84 unread messages in that folder this morning) | 15:39 |
| ttx | question being, if you can follow that, when would be an acceptable date | 15:39 |
| notmyname | I'll ready up | 15:39 |
| notmyname | *read | 15:39 |
| ttx | mostly a question of expected dep addition in the remaining feature set | 15:40 |
| ttx | also doesn't have to be strict freeze, there can always be exceptions, the idea being to communicate to packagers those exceptions properly | 15:40 |
| notmyname | right. seems a reasonable request | 15:40 |
| ttx | rather than let them unearth them by surprise | 15:40 |
| ttx | anyway, just a heads-up | 15:41 |
| notmyname | thanks | 15:41 |
| ttx | talk to you at meeting later today ! | 15:41 |
| notmyname | ok | 15:41 |
| ttx | markwash: ready when you are | 15:42 |
| markwash | ttx: greetings | 15:42 |
| ttx | https://launchpad.net/glance/+milestone/icehouse-rc1 | 15:42 |
| ttx | No more FFEs | 15:42 |
| ttx | 3 bugs in the RC1 list -- is that the complete set of release-critical bugs, or you still need to review the bug backlog ? | 15:43 |
| markwash | yup | 15:43 |
| markwash | That's what I know of except there was another bug that was fixed but never made it into the list | 15:43 |
| markwash | so I should probably retroactively add it | 15:43 |
| markwash | but I'll also take another pass on the bug backlog | 15:43 |
| ttx | it will get caught up by the release process | 15:43 |
| ttx | (the fixed bug) | 15:43 |
| ttx | no need to add them all manually | 15:44 |
| markwash | okay, that's fine then | 15:44 |
| ttx | OK, looks like you're in great shape then | 15:44 |
| ttx | I feel nostalgy for the time when nothing was working at all two weeks after FF | 15:45 |
| markwash | haha | 15:45 |
| ttx | markwash: any interesting topic (or non-interesting topic) you would like to dicuss at meeting today ? | 15:45 |
| ttx | or discuss | 15:45 |
| markwash | I can merge some stuff at random if you like :-) | 15:45 |
| ttx | markwash: if you disable tests first, I'm game | 15:46 |
| hub_cap | lol can i watch? | 15:46 |
| markwash | actually I'd like a little guidance from the group about utf-8 charset enforcement in tables | 15:46 |
| markwash | that's one of our bugs, and I think getting some insight from the broader group would be very helpful | 15:46 |
| ttx | markwash: sounds like a good topic. Care to add it to https://wiki.openstack.org/wiki/Meetings/ProjectMeeting ? | 15:47 |
| markwash | will do | 15:47 |
| ttx | markwash: cool then, talk to you later | 15:47 |
| ttx | hub_cap: around? | 15:48 |
| hub_cap | aye | 15:48 |
| hub_cap | u know, mark and i could just sit next to each other when we do this meeting :) | 15:48 |
| hub_cap | markwash: ** i should say ** | 15:48 |
| ttx | https://launchpad.net/trove/+milestone/icehouse-rc1 | 15:48 |
| markwash | well, today I'm in seattle :-) | 15:48 |
| hub_cap | nm! | 15:48 |
| hub_cap | so the xml bp got merged (the trove piece) | 15:48 |
| ttx | hub_cap: destroy-xml-api looked done to me last time I looked ? | 15:49 |
| ttx | ok | 15:49 |
| hub_cap | but we are stil using it to track some tests / cli stuff | 15:49 |
| hub_cap | im not sure why those are in this bp | 15:49 |
| ttx | Let's mark the BP implemented | 15:49 |
| hub_cap | ya | 15:49 |
| hub_cap | done | 15:49 |
| ttx | OK, that leaves your RC buglist | 15:50 |
| ttx | Is it a complete list of known release-critical bugs ? | 15:50 |
| ttx | Did you review your bug backlog to build it ? | 15:50 |
| hub_cap | well i think one got bumped w/o my knowledge | 15:50 |
| hub_cap | i have not reviewed a bug backlog to build it | 15:50 |
| hub_cap | maybe slicknik did | 15:50 |
| hub_cap | ill ping him, and do a review of this today | 15:50 |
| ttx | hub_cap: OK, would be good to check you don't have a critical thing missing in there | 15:51 |
| hub_cap | one of those is not critical | 15:51 |
| hub_cap | i can see already | 15:51 |
| hub_cap | so ill talk w/ slick to see if he upgraded it | 15:51 |
| ttx | you can remove the nice-to-haves from the list | 15:51 |
| ttx | they will just make it in release if they are merged in time | 15:51 |
| hub_cap | itll auto do that for me right? | 15:51 |
| hub_cap | if its merged in the milestone will be set for bugs | 15:51 |
| *** markwash has quit IRC | 15:51 | |
| hub_cap | right? | 15:51 |
| ttx | they will get added to the milestone when we tag | 15:52 |
| hub_cap | cool | 15:52 |
| hub_cap | thats what i thought, ok good to know | 15:52 |
| hub_cap | ill clean up | 15:52 |
| hub_cap | and make sure we dont have any more criticals | 15:52 |
| ttx | (release process picks up all "FixCommitted" bugs and sets milestone for them | 15:52 |
| hub_cap | so once this is all fix committed, we can cut rc1 right? | 15:52 |
| ttx | OK, that will let us measure how far we are from tagging a release candidate | 15:52 |
| hub_cap | and go back to pushing things to juno pipeline :) | 15:52 |
| ttx | right when all fixcommitted, tag RC1, open master for Juno dev | 15:53 |
| ttx | then if we discover a NEW release-critical issue, we open a RC2 window on the release branch | 15:53 |
| ttx | and backport the master fix | 15:53 |
| hub_cap | perfect | 15:54 |
| ttx | all the process relies on having a good RC buglist :) | 15:54 |
| hub_cap | hehe ya | 15:54 |
| ttx | not too much,n not too little | 15:54 |
| hub_cap | yup and defining what is really critical :) | 15:54 |
| ttx | anything more you'd like to discuss at meeting later ? | 15:54 |
| hub_cap | naw but one more q for u | 15:55 |
| ttx | (also "what is release-critical" shifts as we get nearer to release) | 15:55 |
| hub_cap | oh thatll be fun discussion :) | 15:55 |
| hub_cap | so as for the client, when do they normally get cut? | 15:55 |
| ttx | hub_cap: when you want | 15:55 |
| hub_cap | so there is not really a method to the madness there heh | 15:55 |
| ttx | usually when you stop moving things around below them | 15:55 |
| hub_cap | past X3 i assume | 15:56 |
| ttx | the client is supposed to always being able to talk to all releases | 15:56 |
| *** tjones has joined #openstack-relmgr-office | 15:56 | |
| ttx | so tagging it is just about making sure the good stuff reaches more people | 15:56 |
| ttx | but yeah, we usually see a few tags appear around RC1 | 15:57 |
| ttx | because post-RC1 we only fix a handful of bugs | 15:57 |
| ttx | so it's easy to weigh the client impact | 15:57 |
| *** tjones has left #openstack-relmgr-office | 15:57 | |
| hub_cap | sweet | 15:57 |
| hub_cap | ok then thats all for me ill start the cleanup now | 15:58 |
| hub_cap | and only have critical bugs in the rc1 | 15:58 |
| ttx | OK. Will ping you when that list gets down to 0. If it ever does | 15:58 |
| hub_cap | oh god i hope so! | 15:58 |
| hub_cap | ;) | 15:58 |
| ttx | hub_cap: talk to you later! | 15:59 |
| hub_cap | ok so quick q | 15:59 |
| ttx | ask | 15:59 |
| hub_cap | ttx do i leave the fix committed in as well? | 15:59 |
| hub_cap | and the in progress criticals | 15:59 |
| hub_cap | or _just_ the criticals and let the script do the rest heh | 16:00 |
| ttx | sure, the Fixcommitted don't hurt | 16:00 |
| hub_cap | k thx | 16:00 |
| ttx | we just track how many open ones | 16:00 |
| ttx | On http://old-wiki.openstack.org/rc/ | 16:00 |
| * ttx needs to get that URL fixes | 16:00 | |
| ttx | hub_cap: any other question ? | 16:01 |
| hub_cap | nosir | 16:04 |
| hub_cap | lol old-wiki | 16:04 |
| ttx | hub_cap: ok then, see you later! | 16:04 |
| hub_cap | cu ttx thx again | 16:04 |
| *** johnthetubaguy has quit IRC | 16:13 | |
| *** johnthetubaguy has joined #openstack-relmgr-office | 16:14 | |
| *** markwash has joined #openstack-relmgr-office | 16:57 | |
| *** markwash has quit IRC | 17:01 | |
| *** morganfainberg_Z is now known as morganfainberg | 17:01 | |
| *** markwash has joined #openstack-relmgr-office | 17:07 | |
| *** johnthetubaguy has quit IRC | 17:27 | |
| *** johnthetubaguy has joined #openstack-relmgr-office | 17:27 | |
| *** morganfainberg is now known as morganfainberg_Z | 17:38 | |
| *** morganfainberg_Z is now known as morganfainberg | 17:58 | |
| *** johnthetubaguy has quit IRC | 18:57 | |
| *** johnthetubaguy has joined #openstack-relmgr-office | 18:57 | |
| *** johnthetubaguy has quit IRC | 19:15 | |
| ttx | stevebaker: ready when you are | 19:30 |
| stevebaker | I am ready! | 19:31 |
| ttx | https://launchpad.net/heat/+milestone/icehouse-rc1 | 19:31 |
| ttx | No more FFE running | 19:31 |
| ttx | So focus shifts to the release-critical buglist | 19:31 |
| ttx | The idea is to make it only contain release-critical issues, so that we can track how far we are from cutting a valid release candidate | 19:32 |
| ttx | so you might want to track nice-to-haves using a tag | 19:32 |
| ttx | and refine that list to only contain blockers | 19:32 |
| ttx | and assigned bugs | 19:32 |
| stevebaker | so anything that must be in should be Critical? | 19:32 |
| ttx | not necessarily | 19:32 |
| ttx | Bug importance describes impact | 19:33 |
| ttx | sometimes it's a doc fix you want to set right before release | 19:33 |
| stevebaker | right, understood | 19:33 |
| stevebaker | when is rc1 out? | 19:33 |
| ttx | RC1 is tagged whenever we manage to get that list down to 0 | 19:33 |
| ttx | ideally sometimes next week | 19:34 |
| ttx | RC1 is, in theory, a valid release candidate | 19:34 |
| ttx | so something where all known release-critical issues are fixed | 19:34 |
| stevebaker | ok, so it might pay to kick medium bugs which are not in progress | 19:34 |
| ttx | The list should just contain all the bugs you don't want to release with | 19:35 |
| ttx | anything else that passes review in time will also get in | 19:35 |
| stevebaker | will there be an rc2 milestone in launchpad? | 19:35 |
| ttx | so it doesn't prevent from fixing OTHER bugs | 19:35 |
| ttx | There is a RC2 milestone when (if) we open a RC2 window | 19:35 |
| ttx | i.e. if we "discover" a release-critical issue post-RC1 | 19:36 |
| ttx | https://wiki.openstack.org/wiki/ReleaseCycle#Pre-release_.28Release_Candidates_dance.29 | 19:36 |
| ttx | All explained there ^ | 19:36 |
| stevebaker | I shall ready that | 19:36 |
| ttx | Now that's the theory | 19:36 |
| ttx | In practice it all depends where you draw the line between release-critical and not release-critical | 19:37 |
| ttx | and that line moves as we get closer to release (we get more picky) | 19:37 |
| ttx | At this point, just list all the bugs you would not be comfortable releasing with. Ignoring nice-to-haves | 19:37 |
| ttx | that way we can check how fast we burn them down | 19:38 |
| stevebaker | how should I list them? Is there a tag? | 19:38 |
| ttx | target them to -rc1 | 19:38 |
| ttx | so that they appear on https://launchpad.net/heat/+milestone/icehouse-rc1 | 19:38 |
| stevebaker | ok, and everything else as next? | 19:39 |
| ttx | or use a tag like "icehouse-rc-potential" | 19:39 |
| ttx | but you don't really need to track "everything else" | 19:39 |
| ttx | FixCommitted bugs will get added to the milestone when we cut it | 19:40 |
| stevebaker | yep, ok | 19:40 |
| ttx | so you don't need to list them all | 19:40 |
| ttx | That should probably reduce your list of 35 open RC1 bugs to ~15 | 19:40 |
| stevebaker | yep, that sounds reasonable | 19:40 |
| ttx | We track progress at http://old-wiki.openstack.org/rc/ | 19:41 |
| ttx | heat cinder neutron are a bit too high, either they are in really bad shape, or just have cruft i their RC1 buglist | 19:41 |
| ttx | I bet on cruft and ask you to refine :) | 19:41 |
| ttx | stevebaker: any topic for the meeting in 75 minutes ? | 19:42 |
| stevebaker | yes, we tend to kick the can to the next milestone for every release | 19:42 |
| stevebaker | nothing for the meeting that I can think of | 19:43 |
| ttx | stevebaker: yeah, not sure that really works well. Maybe abuse bug "importance" to select the list of please-fix bugs | 19:43 |
| ttx | i.e. make all the can-kicked bugs >=High | 19:43 |
| ttx | because setting a milestone should correspond to some engagement to fix it | 19:44 |
| ttx | in that milestone | 19:44 |
| ttx | just deferring it over and over looks a bit funny | 19:44 |
| stevebaker | yeah, I tend to use the milestone to indicate that it should get some attention "soon" | 19:44 |
| ttx | stevebaker: yeah. I'd recommend to use a tag or importance to get that info, at least as long as we are on LP | 19:45 |
| stevebaker | yep | 19:45 |
| ttx | because moving bugs from one milestone to the next is not my definition of fun | 19:45 |
| ttx | and it doesn't magically get people to fix them | 19:45 |
| ttx | I'd rather let the milestone buglist mean: "the bugs we raelly intend to fix during that milestone" | 19:46 |
| ttx | anyway. talk to you later ! | 19:46 |
| *** david-lyle has quit IRC | 19:46 | |
| stevebaker | ok, later | 19:46 |
| *** david-lyle has joined #openstack-relmgr-office | 20:18 | |
| *** markwash_ has joined #openstack-relmgr-office | 21:52 | |
| *** markwash has quit IRC | 21:54 | |
| *** markwash_ is now known as markwash | 21:54 | |
| *** markmcclain1 has joined #openstack-relmgr-office | 22:17 | |
| *** markmcclain has quit IRC | 22:17 | |
| *** markmcclain1 has quit IRC | 22:24 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!