20:00:10 #startmeeting horizon 20:00:11 Meeting started Wed Apr 5 20:00:10 2017 UTC and is due to finish in 60 minutes. The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:15 The meeting name has been set to 'horizon' 20:00:30 o/ 20:00:33 o/ 20:00:35 o/ 20:00:35 o/ 20:00:38 o/ 20:00:44 o/ 20:00:46 o/ 20:00:53 o/ 20:01:05 Hello everyone 20:01:28 :) 20:01:42 #topic Notices 20:02:12 So, we're closing in on the pike-1 milestone (13th April) 20:02:45 We've made some good progress so far, I'm really pleased with how the cycle is going. You can check up on the current tracking at... 20:02:48 #link https://launchpad.net/horizon/+milestone/pike-1 20:03:52 Currently at 63 bugs fixed and 4 blueprints closed. We should be able to close another couple of those bps in the next week, too. 20:04:41 We'll also be bumping the Django version soon; there's a patch in requirements that I've -workflow'd until I can confirm Horizon still works fine with 1.9 20:05:09 #link https://review.openstack.org/#/c/453482/ 20:05:38 Following that we'll bump to 1.10 and 1.11, with a few weeks in between for stability. 20:05:59 I think thats everything from me; any other notices? 20:07:27 There's nothing on the agenda, so we can move to open discussion 20:07:32 #topic Open Discussion 20:07:44 I just pushed the nova policy update 20:07:51 so that will be closed as well 20:08:02 Ah excellent, thanks for that 20:08:20 had reviewed it earlier too, forgot to push :) 20:09:01 I have been asked by our release people about release tags on python-horizon-tests-tempest 20:09:11 Ohh, thats *was* you! 20:09:15 that* 20:09:15 because there was that patch there fixing pep8 on it 20:09:23 I mentioned it last week but we had no context 20:09:26 and they weren't sure how to release it 20:09:43 Do we even tag that lib? 20:09:49 yeah, sorry, the time change made me miss last meeting -- I came an hour too early and left :( 20:10:15 rdopiera, same question as last week, is that based tempest-horizon? 20:10:21 *based on 20:10:31 rdopiera: -.- 20:10:58 david-lyle: what do you mean by "that"? 20:11:27 they just wanted to package it and wondered how to version it 20:11:35 python-horizon-tests-tempest is nothing I know about 20:11:59 ah, right, that's our downstream name 20:12:07 tempest-horizon is a repo with our tempest tests 20:12:11 yes, that's tempest-horizon, sorry 20:12:13 That answers the question :) 20:12:22 not worries, just trying to clarify 20:12:26 I forgot we like to rename things 20:12:36 like Horizon is python-django-horizon for some reason 20:12:48 we have not tagged it 20:13:00 but to follow tempest, tagging would make sense 20:13:01 right, the question is, do we want to? 20:14:05 I have no problem with tagging it 20:14:48 Yeah, we can do that 20:14:58 Makes no difference to me :) 20:15:09 that would make the release peopel happy 20:15:12 people 20:15:22 sure, need to be able to track it somehow 20:16:39 I can go back and figure out where Ocata was cut and retroactively tag 20:17:29 I think there were no commits since 20:17:36 that should be the only release we care about? 20:17:46 there have been a few, I just checked 20:18:05 oops, sorry, didn't watch 20:19:00 rdopiera: Is there already a downstream release? 20:19:59 https://github.com/openstack/tempest-horizon/commit/9d5bb7bde323653af2d0b849e8a1c120b47e2b84 should be the last ocata commit 20:20:50 robcresswell: yes, we have Release: 0.20170316112600.a3312bc%{?dist} 20:21:08 I guess that's a date and the git hash 20:21:23 from tempest-horizon-0.0.1.dev13-0.20170316112600.a3312bc-a3312bcad15dc04e77fd114e0da0deff0db30336.tar.gz 20:21:50 March 16? 20:21:54 so this is what they do when there are no tags 20:21:58 that's for Pike 20:22:04 Thats the most recent commit 20:22:15 ok, so do we need an ocata tag? 20:22:29 I think one per release? or ??? 20:22:35 oh, so not released 20:23:08 sorry, I'm still not entirely familiar with our release stuff 20:23:30 rdopiera: I'm not sure what you're asking for, because the version there is the most recent upstream anyway 20:23:39 A retroactive tag seems useless now? 20:23:49 we can plan to tag pike 20:23:51 robcresswell: yeah, I'm asking about tagging it from now on 20:24:00 Ah sure 20:24:05 Yeah we can tag it for Pike 20:24:49 Does that resolve that situation? 20:25:21 there is no situation, I just thought I would mention it, I'm fine either way 20:25:23 thank you 20:25:42 Haha, sorry, "situation" was probably the wrong word 20:25:58 But yeah, happy to tag at Pike to make downstream happy 20:26:02 more of an incident 20:26:09 :p 20:26:11 defect :P 20:27:08 Anything else anyone would like to discuss? 20:28:32 I think we can call it there 20:28:45 rdopiera, btw, thanks for your help on the microversion patch 20:29:15 That was really helpful 20:29:44 And great work everyone so far, please keep it at it, we're making great progress 20:29:47 robcresswell: cheers, I'm getting better at handling mox :P 20:30:05 \o/ 20:30:18 #endmeeting