12:00:23 <david-lyle> #startmeeting Horizon
12:00:24 <openstack> Meeting started Wed Apr 15 12:00:23 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.
12:00:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
12:00:27 <openstack> The meeting name has been set to 'horizon'
12:00:32 <sambetts> o/
12:00:39 <tsufiev> hi!
12:01:07 <mrunge> hey
12:01:13 <amotoki> hey
12:01:21 <doug-fish> hello
12:02:08 <mattfarina> hello
12:02:29 <david-lyle> #topic General
12:02:51 <david-lyle> Yesterday we tagged RC1
12:02:57 <david-lyle> \o/
12:02:59 <mrunge> congrats!
12:03:14 <doug-fish> hooray!
12:03:19 <amotoki> |o|
12:03:27 <mattfarina> yay
12:03:32 <amotoki> ....\o/
12:03:40 <david-lyle> Thanks to everyone for your hard work getting to this point
12:04:17 <david-lyle> We will have an RC2, but nothing critical is looming for it, but we need it to import final translations
12:04:45 <doug-fish> david-lyle: not to be a party pooper, but I'm really quite concerned about this:  https://bugs.launchpad.net/horizon/+bug/1444150
12:04:47 <openstack> Launchpad bug 1444150 in OpenStack Dashboard (Horizon) "New Launch Instance dialog is mostly untranslatable" [Undecided,New]
12:04:56 <doug-fish> I was hope that somebody else would tell me it all works fine
12:05:03 <doug-fish> but that hasn't happened yet.
12:05:15 <david-lyle> I also have two low risk, high gain bugs that we can cherry pick the fixes to it https://bugs.launchpad.net/horizon/+bugs?field.tag=kilo-rc-potential
12:05:21 <david-lyle> doug-fish: looking
12:06:36 <amotoki> doug-fish: Does it introduce new strings?
12:06:42 <doug-fish> I can't say why it's failing - the code looks right
12:06:44 <doug-fish> yeah, lots
12:07:02 <doug-fish> and almost none of them are in the po files I generate
12:07:10 <mrunge> I had another bug for kilo-rc-potential: https://bugs.launchpad.net/bugs/1444421
12:07:19 <openstack> Launchpad bug 1444421 in OpenStack Dashboard (Horizon) "Launch instance fails with nova network" [Undecided,New]
12:07:19 <amotoki> I think it is better to avoid introduce new strings at this stage. the dialog is regarded as experimental in this reelase
12:07:19 <david-lyle> but "Availability Zone" must be translated already
12:07:45 <amotoki> so we don't need to tackle it in this release.
12:07:46 <doug-fish> david-lyle: seems its not in the right file to be found - not in djangojs.po maybe.
12:08:09 <doug-fish> I thought this was our default option for launch instance now
12:08:24 <david-lyle> doug-fish: no
12:08:28 <doug-fish> ah ok
12:08:42 <david-lyle> I chose to leave it as experimental
12:08:47 <doug-fish> If it's experimental I feel much better about it.
12:08:53 <doug-fish> david-lyle: nice choice!
12:09:11 <david-lyle> a lot of that has to do with the fact of how late it landed and how little real world testing it has
12:09:28 <david-lyle> we can't just dump that in operators' laps
12:09:30 <mattfarina> doug-fish it's unknown why the js translations aren't working? are they just not working for launch instance or all js?
12:09:32 <doug-fish> agreed. Is there a setting to enable/disable it?
12:09:40 <david-lyle> and hope for the best
12:09:51 <david-lyle> doug-fish: yes and it's disabled by default
12:10:11 <doug-fish> mattfarina: I know some js is working (like network topology) and some isn't (like launch instance)
12:10:59 <david-lyle> the translation mechanism is the same as other JS files, so not sure what would be failing, but the way the JS is forced to use those translated strings is horrible
12:11:15 <david-lyle> and fixing that is one of the top priorities in Liberty
12:11:30 <doug-fish> yes, that sounds good to me.
12:11:32 <david-lyle> mrunge: I tagged yours as such
12:11:41 <david-lyle> that shouldn't be happending
12:11:47 <mrunge> david-lyle, thanks, I did as well...
12:12:01 <mrunge> no idea, how launchpad will handle that
12:13:09 <david-lyle> mrunge: looks right
12:13:17 <david-lyle> I assigned myself
12:13:21 <david-lyle> will look today
12:13:41 <mrunge> david-lyle, strange thing is, I remember it worked
12:13:52 <mrunge> not sure, what changed there
12:14:02 <david-lyle> I wouldn't have thought a lot
12:14:19 <mrunge> yes, same here.
12:15:05 <david-lyle> So as your doing your testing, if you come across a bug you think may be critical to the release, please either tag it as kilo-rc-potential, or ping me
12:15:34 <david-lyle> We have a couple weeks left to fix these problems
12:15:56 <david-lyle> With RC1 cut, master is now open for liberty
12:16:16 <david-lyle> so many of the items that just missed Kilo will start landing
12:16:32 <david-lyle> I have not prioritized items for L-1
12:17:02 <david-lyle> if they are assigned it's either self-assigned or carry-over
12:17:28 <david-lyle> today or tomorrow I will open up a specs repo for Horizon
12:17:53 <david-lyle> and we'll move the specifications to that, so we have a better voting record than launchpad
12:18:12 <mrunge> awesome!
12:18:16 <david-lyle> I email the dev list when I have that set up
12:18:21 <tsufiev> great news!
12:18:50 <david-lyle> when we move to using that, self-assigning of blueprints to milestones will be disabled in launchpad
12:19:19 <david-lyle> the Horizon Drivers will be the only ones that can set that
12:19:38 <david-lyle> since the spec will be the notification mechanism
12:20:00 <david-lyle> It will reduce a lot of the milestone planning noise and maintenance that I have to do
12:20:27 <david-lyle> we will still have trivial feature adds that won't require a full spec
12:20:45 <david-lyle> do we want to handle that with a trivial spec, or just a blueprint?
12:21:22 <doug-fish> i'd suggest trivial spec
12:21:37 <doug-fish> otherwise people will just declare their blueprint trival and bypass that process
12:21:45 <mrunge> +1 doug-fish
12:21:46 <doug-fish> I know that's what I'll do!
12:21:56 <david-lyle> that would be more consistent
12:22:16 <david-lyle> ok, we can handle both in the specs repo
12:23:38 <david-lyle> For the summit, I believe we have 3 fishbowl sessions, 7 working sessions and 2 half-day meetup sessions (like friday last time)
12:24:17 <david-lyle> #link https://etherpad.openstack.org/p/horizon-liberty-summit is for topic suggestions
12:24:46 <david-lyle> we'll need to start voting that down in the next couple of weeks
12:25:13 <david-lyle> I also want to point out #link https://wiki.openstack.org/wiki/Design_Summit/Planning
12:25:44 <david-lyle> if you are interested in cross-project topics or other services
12:26:37 <david-lyle> I think that's all I had for general items
12:26:42 <david-lyle> any questions?
12:27:24 <tsufiev> david-lyle, are we still waiting here https://review.openstack.org/#/c/163028/ for new version of openstack_auth?
12:27:49 <david-lyle> amotoki, has indicated final translations are targeted for April 23
12:28:26 <david-lyle> tsufiev: I release 1.2.0 a couple of days ago
12:28:59 <david-lyle> we now need to move g-r to require >= 1.2.0 before we can merge that change
12:29:10 <tsufiev> david-lyle, ah, got it, thanks
12:29:30 <david-lyle> 1.2.0 brought Django 1.7 support which was needed for the release of Kilo
12:29:47 <david-lyle> but did not require moving the minimum version of d-o-a
12:29:58 <mrunge> I have a tiny patch currently not passing tests for django-1.8 :D
12:30:28 <david-lyle> mrunge: Django 1.8 support needs to be a K-1 item
12:30:36 <david-lyle> no more waiting around on our parts
12:30:38 <mrunge> l-1 item?
12:30:44 <mrunge> but yes!
12:30:45 <david-lyle> err, L-1
12:30:55 <david-lyle> where am I?
12:31:10 <mrunge> since diffs are quite small, we even might be able to backport that
12:31:21 <david-lyle> mrunge: sure
12:32:03 <david-lyle> and Django will probably release again before we ship Liberty and ruin everything :P
12:32:23 <doug-fish> I think 1.8 is a LTS release
12:32:26 <mrunge> david-lyle, 1.8 was released a few days ago
12:32:37 <david-lyle> doug-fish: yes it is
12:32:40 <david-lyle> mrunge: I know
12:32:41 <mrunge> and yes, it's a lts release
12:32:54 <doug-fish> we can stay on it forever!
12:32:55 <doug-fish> (almost)
12:32:56 <david-lyle> but seems to be a 6 month cadence now
12:33:23 <david-lyle> we can also look at dropping 1.4 support once we have 1.8 support
12:33:57 <david-lyle> Something I should not about the 1.2.0 d-o-a release, it no longer supports python 2.6
12:34:09 <david-lyle> as Django 1.7 does not support 2.6
12:34:54 <david-lyle> #topic Open Discussion
12:35:55 <david-lyle> Other high priority items are plugin strategy
12:36:57 <david-lyle> now that the release pressure has subsided we need to consider plugins from two perspectives, new items in OpenStack and some items already in Horizon
12:37:05 <tsufiev> Speaking of plugins... https://review.openstack.org/#/c/128133/ - still not merged as part of Kilo -> plugins are not being added to the proper PanelGroup
12:38:37 <david-lyle> that has RC potential
12:39:03 <tsufiev> okay, just had to make sure, nobody forgets about it :)
12:39:19 <david-lyle> I tagged it
12:39:41 <david-lyle> I need to look at that one more closely
12:40:50 <david-lyle> mrunge: I see very few patches on tuskar-ui, do you know if that's still a point of interest
12:40:59 <david-lyle> and does it need a release for kilo?
12:41:12 <david-lyle> asking you with your red hat on
12:41:45 <mrunge> david-lyle, I must admit, I don't know
12:41:51 <mrunge> akrivoka, can you comment?
12:42:08 <akrivoka> david-lyle: it is definitely still of interest
12:42:41 <david-lyle> ok, is it ready to release?
12:43:12 <david-lyle> generally at this time of the cycle someone asks me to release it
12:43:12 <akrivoka> david-lyle: let me double check and get back to you soon
12:43:18 <david-lyle> akrivoka: thanks!
12:43:27 <akrivoka> david-lyle: thank you!
12:47:25 <david-lyle> anyone have another item for today?
12:48:03 <david-lyle> I will be posting release notes soon to the wiki page for the release
12:49:09 <david-lyle> I'm contemplating making the command decision not to merge and rst version in the horizon tree this time
12:49:20 <david-lyle> i looked and no other service seems to do that
12:49:38 <david-lyle> and I missed the release cut-off
12:49:45 <david-lyle> and issues with that
12:50:00 <doug-fish> I don't quite follow what you are not going to do ...
12:50:02 <david-lyle> s/and/any/
12:50:32 <mrunge> I found release notes useful in the past
12:50:43 <david-lyle> typically release notes for say Kilo are posted to an openstack wiki page and in the source tree
12:50:50 <mrunge> and I must admit, I never looked at them in the wiki
12:51:05 <akrivoka> david-lyle: we have one patch we need to land in tuskar-ui before we're ready to release
12:51:14 <akrivoka> david-lyle: will let you know when we're ready
12:51:15 <mrunge> ... try to find something in the wiki, that is awful
12:51:19 <david-lyle> on the wiki they are combined with all the other services
12:51:41 <david-lyle> akrivoka: thank you, once that's merged, I can release
12:52:02 <akrivoka> david-lyle: thanks!
12:52:22 <david-lyle> mrunge: maybe I can try to slip it into RC-2
12:52:54 <david-lyle> just wasn't sure anyone used them
12:53:00 <mrunge> david-lyle, I didn't even knew you were supposed to prepare two different formats
12:53:29 <mrunge> david-lyle, if I'm the only one using them, I'd say: wiki is fine
12:53:36 <david-lyle> mrunge: not a big deal
12:54:05 <david-lyle> I'll see where I get with them in the next few days
12:54:13 <mrunge> cool
12:54:20 <david-lyle> I'll need reviews either way
12:54:28 <david-lyle> I always miss items
12:54:40 <mrunge> I just wanted to mention, release notes are really read by humans :D
12:56:44 <david-lyle> mrunge: as long as someone finds them useful and I'm not just writing to myself, I'm ok with taking the effort
12:58:31 <david-lyle> I'll call it for today. Thanks everyone for your efforts on Kilo, please take the time to test the RC so we don't ship anything major that could have been addressed.
12:58:38 <david-lyle> Have a great week!
12:58:42 <david-lyle> #endmeeting