22:02:40 <jpich> #startmeeting horizon
22:02:41 <openstack> Meeting started Tue Apr  2 22:02:40 2013 UTC.  The chair is jpich. Information about MeetBot at http://wiki.debian.org/MeetBot.
22:02:43 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
22:02:45 <openstack> The meeting name has been set to 'horizon'
22:02:57 <gabrielhurley> I see it's in capable hands. thanks!
22:03:18 <jpich> No problems!
22:03:19 <cody-somerville> \o_
22:03:27 <jpich> Let's go with the usual agenda and see what happens
22:03:31 <kspear> Hi all
22:03:35 <davidlyle> hello
22:03:43 <jpich> #topic General Horizon Status
22:03:56 * kspear has been away for a while, so has some catching up to do
22:04:41 <jpich> From the previous meeting: Horizon RC2 was released on Thursday and still looks good, so it'll likely become the Grizzly release
22:05:25 <jpich> For design summit: the same number of sessions than there are available was received, and since the proposals all look good they've all been accepted
22:05:48 <jpich> ...I guess that removes a lot of the scheduling difficulties
22:06:27 <jpich> Hi kspear :) Feel free to jump in!
22:06:41 <jpich> That's all I can think of, so moving on
22:06:47 <jpich> #topic Blueprints and Bugs
22:06:54 <davidlyle> any idea which days the Horizon sessions are?
22:07:39 <jpich> Someone briefly showed me a Google doc spreadsheet but I forgot, I think it might be Tuesday afternoon
22:08:00 <lcheng> Tuesday: http://openstacksummitapril2013.sched.org/
22:08:54 <jpich> Cool, thanks lcheng
22:09:21 <jpich> From 11am to 4:30pm it looks like
22:09:49 <jpich> Cool. Did anyone have any bug or blueprint matter they'd like to bring up?
22:10:14 <lcheng> I do. :)
22:10:26 <lcheng> I started working on https://bugs.launchpad.net/horizon/+bug/1147329
22:10:29 <uvirtbot> Launchpad bug 1147329 in horizon "Templates are not django 1.5 compatible" [High,In progress]
22:10:40 <jpich> Great!
22:11:12 <lcheng> Do we need to update the template to be backward compatible?
22:11:37 <lcheng> Changing: {% url myview %} to {% url "myview" %} does not work with django 1.4
22:12:23 <jpich> That's a good question. If it's not possible I don't think we should do it :-) I don't think current Horizon is compatible with Django 1.3 so it looks like we only support one Django version at a time
22:13:50 <jpich> I'd suggest adding a comment asking your question to the report
22:13:53 <kspear> lcheng: so Django broke the template format between versions?
22:14:09 <kspear> i would have thought that was unlikely
22:14:21 <lcheng> Yes. The other alternative is to keep the format of existing url tag and add {% load url from future %}  in all files using url template.
22:15:05 <lcheng> kspear: Yes, the old format of {% url myview %} would not work in django 1.5 without any changes.
22:16:10 <kspear> lcheng: i see. just read that it has been deprecated since 1.3
22:16:49 <cody-somerville> '{% load url from future %}' can be added to make it work with 1.4.
22:17:52 <kspear> guess we need to look at whether there's anything holding us back from requiring 1.5
22:18:16 <kspear> given that 1.4 is still supported security-wise until the release of 1.6 i'd lean towards continuing to support it
22:18:47 <zykes-> :pyo
22:19:23 <jpich> We haven't been really shy about using new Django features when we upgrade versions though. We might want to be more explicit about what Django versions we want to support, like we do with supporting OpenStack n-1
22:20:52 <jpich> I wanted to mention https://bugs.launchpad.net/horizon/+bug/1163369 since it blocks the Horizon tests (docs failure), however since then there's a prettytables conflict that affects multiple projects, so that'd be the new thing to keep an eye on
22:20:53 <uvirtbot> Launchpad bug 1163369 in horizon "Docs not building with Sphinx 1.2" [High,In progress]
22:21:01 <kspear> jpich: good point. we might want to look at a gate job if we decided to continue 1.4 support
22:21:46 <jpich> kspear: Maybe we should take the topic to the mailing list to discuss this then
22:23:05 <jpich> There are good bad sides to multiple versions support (shiny new features vs. making packagers' lives easier)
22:23:19 <jpich> Any other bug/blueprint matter someone would like to bring up...?
22:23:28 <amotoki> hello. i have a question about translation imports from horizon.
22:23:31 <kspear> jpich: agreed. happy to take it to the list
22:24:19 <amotoki> po files in grizzly rc are already out-of-date now.
22:24:29 <jpich> amotoki: You may ask, but I think Gabriel has been the person doing the process manually and would be the best person to answer
22:24:39 <jpich> kspear: Cheers!
22:25:31 <amotoki> jpich: thanks. i know it is done manually by gabriel. I send the mail.
22:25:38 <jpich> amotoki: we can probably do a translation update as part of the first grizzly stable release, I'm not sure when that is
22:26:21 <amotoki> i know there are some progress done in Trasifex. it is worth importing them.
22:26:34 <jpich> Yeah it sounds definitely worth it
22:26:49 <lcheng> kspear, jpich: thanks
22:27:18 <jpich> I'm not sure if we would cut a RC3 for translations, although that sounds somewhat low risk high impact...
22:28:39 <jpich> I think it's more likely to go into a stable release but that sounds worthwhile still asking the PTL or ttx
22:29:31 <jpich> Ok
22:29:34 <jpich> #topic General Discussion
22:29:56 <jpich> Anything else?
22:31:27 <jpich> Giving it another minute or two...
22:33:22 <jpich> Ok. Thank you everyone, have a nice day/afternoon/evening
22:33:26 <jpich> #endmeeting