Re: [openstack-dev] [horizon] [horizon-plugin] [requirements] Moving to Django 1.11

[Rob Cresswell]

django_openstack_auth and django-babel have been released, and now the 
generated upper-constraints patch containing Django 1.11.x is here: 
https://review.openstack.org/#/c/486093

If something suddenly starts misbehaving in Horizon or a plugin, there's a good 
chance it's stemmed from this marging and hitting the CI's. The release notes 
are here, as a reference: https://docs.djangoproject.com/en/1.11/releases/1.11/

Please ping me on IRC (robcresswell) in the #openstack-horizon room if you need 
help.

Thanks again to everyone who helped with this effort.

Rob

On 19 July 2017 at 15:38, Rob Cresswell 
> wrote:
Hi everyone,

Django 1.11 support has landed for Django OpenStack Auth [1], which was 
released shortly after [2]. Horizon's Django 1.11 support is just merging [3], 
at which point we will raise the global requirement [4] and make the Horizon / 
DOA tests voting [5].

At that point, we should be able to merge the requirements patches and tag 
Django OpenStack Auths final release for Pike. The only other blocking issue 
that I'm aware of is getting django-babel released (external to openstack) with 
Django 1.11 support; there is a GitHub issue open [6].

Overall, we should (fingers crossed) be able to land this effort on time for 
non-client lib freeze and requirements freeze. Big thanks to everyone that 
contributed towards this.

Cheers,
Rob

1. https://review.openstack.org/#/c/484722/
2. https://review.openstack.org/#/c/484914/
3. https://review.openstack.org/#/c/484277/
4. https://review.openstack.org/#/c/485221/
5. https://review.openstack.org/#/c/485220/
6. https://github.com/python-babel/django-babel/issues/38

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [horizon] [horizon-plugin] [requirements] Moving to Django 1.11

[Rob Cresswell]

Hi everyone,

Django 1.11 support has landed for Django OpenStack Auth [1], which was 
released shortly after [2]. Horizon's Django 1.11 support is just merging [3], 
at which point we will raise the global requirement [4] and make the Horizon / 
DOA tests voting [5].

At that point, we should be able to merge the requirements patches and tag 
Django OpenStack Auths final release for Pike. The only other blocking issue 
that I'm aware of is getting django-babel released (external to openstack) with 
Django 1.11 support; there is a GitHub issue open [6].

Overall, we should (fingers crossed) be able to land this effort on time for 
non-client lib freeze and requirements freeze. Big thanks to everyone that 
contributed towards this.

Cheers,
Rob

1. https://review.openstack.org/#/c/484722/
2. https://review.openstack.org/#/c/484914/
3. https://review.openstack.org/#/c/484277/
4. https://review.openstack.org/#/c/485221/
5. https://review.openstack.org/#/c/485220/
6. https://github.com/python-babel/django-babel/issues/38
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] [horizon-plugin] Raising Django version cap

[Rob Cresswell (rcresswe)]

Awesome, I appreciate the work here. I spoke with a couple Django folk on IRC 
and they didn’t have any other solution than “vendor the code”, so I think your 
approach is probably the most reasonable. I’m fairly annoyed that they dropped 
an interface like that, but oh well.

I’ll take a look at the patch and give some feedback. Hoping to also get some 
feedback on the D_O_A merge this week too, otherwise I’ll probably just go 
ahead and do it.

Rob

On 17 Jul 2017, at 09:12, Adrian Turjak 
> wrote:


Was hoping to play with this much sooner, but here is a quick hack for horizon 
working with django 1.11

https://review.openstack.org/#/c/484277/

The main issues are with widgets from Django which are no longer there, and all 
I've done is move them to our repo from django 1.10's code. This is probably 
not a good long term solution.

Then django-babel doesn't yet have a version that has django 1.11 support, 
although the change has been merged to master. Just needs a new release. For 
now a install from source works to test.

And... because it was easier, I did this off the patch that brings 
openstack_auth into horizon. Because of some import order changes in django (I 
assume), there was an issue due to an import that caused a call to 
get_user_model before openstack_auth was fully loaded.

Beyond that, it all 'appears' to work. I launched some instances, created some 
networks, changed my password, managed some projects and users. There is tons 
to actually test, but mostly it just seems to work.

On 05/07/17 22:24, Rob Cresswell (rcresswe) wrote:
If you want to install Django 1.11 and test it, that would be very helpful, 
even if its just to open bugs. I’m in the process of adding a non-voting job 
for 1.11 right now, so we should be able to move quickly.

Rob

On 5 Jul 2017, at 01:36, Adrian Turjak 
> wrote:

Great work!

Is there anything that can be done to help meet that July deadline and get 
1.11.x in? I'm more than happy to help with reviews or even fixes for newer 
Django in Horizon, and we should try and get others involved if it will help as 
I think this is a little urgent.

Running anything less than Django 1.11 leaves us in a weird spot because of the 
point where support ends for any versions below it.

Looking at the release timelines, if we don't get 1.11 in for Pike, we'll have 
released a version of Horizon that will be for an unsupported version of Django 
in about 6 months time (8 if deployers stick with django 1.8):
https://releases.openstack.org/pike/schedule.html
https://www.djangoproject.com/download/

It isn't as bad it could be, but it's an awkward situation to be in. 1.9 is no 
longer supported, 1.10 support stops at 2018, so realistically 1.8 is the only 
version to have Pike 'safe' until Queens thats not particularly great either. 
Getting 1.11 support in would be ideal.


On 05/07/17 03:01, Rob Cresswell wrote:
Hi everyone,

I've put up a patch to global-requirements to raise the Django cap to "<1.11", 
with the upper-constraint at "1.10.7" 
(https://review.openstack.org/#/c/480215). Depending on the remaining time, I'd 
quite like to move us to "1.11.x" before Requirements Freeze, which will fall 
around the 27th of July.

Rob



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] [horizon-plugin] Raising Django version cap

[Adrian Turjak]

Was hoping to play with this much sooner, but here is a quick hack for
horizon working with django 1.11

https://review.openstack.org/#/c/484277/

The main issues are with widgets from Django which are no longer there,
and all I've done is move them to our repo from django 1.10's code. This
is probably not a good long term solution.

Then django-babel doesn't yet have a version that has django 1.11
support, although the change has been merged to master. Just needs a new
release. For now a install from source works to test.

And... because it was easier, I did this off the patch that brings
openstack_auth into horizon. Because of some import order changes in
django (I assume), there was an issue due to an import that caused a
call to get_user_model before openstack_auth was fully loaded.

Beyond that, it all 'appears' to work. I launched some instances,
created some networks, changed my password, managed some projects and
users. There is tons to actually test, but mostly it just seems to work.


On 05/07/17 22:24, Rob Cresswell (rcresswe) wrote:
> If you want to install Django 1.11 and test it, that would be very
> helpful, even if its just to open bugs. I’m in the process of adding a
> non-voting job for 1.11 right now, so we should be able to move quickly.
>
> Rob
>
>> On 5 Jul 2017, at 01:36, Adrian Turjak > > wrote:
>>
>> Great work!
>>
>> Is there anything that can be done to help meet that July deadline
>> and get 1.11.x in? I'm more than happy to help with reviews or even
>> fixes for newer Django in Horizon, and we should try and get others
>> involved if it will help as I think this is a little urgent.
>>
>> Running anything less than Django 1.11 leaves us in a weird spot
>> because of the point where support ends for any versions below it.
>>
>> Looking at the release timelines, if we don't get 1.11 in for Pike,
>> we'll have released a version of Horizon that will be for an
>> unsupported version of Django in about 6 months time (8 if deployers
>> stick with django 1.8):
>> https://releases.openstack.org/pike/schedule.html
>> https://www.djangoproject.com/download/
>>
>> It isn't as bad it could be, but it's an awkward situation to be in.
>> 1.9 is no longer supported, 1.10 support stops at 2018, so
>> realistically 1.8 is the only version to have Pike 'safe' until
>> Queens thats not particularly great either. Getting 1.11 support in
>> would be ideal.
>>
>>
>> On 05/07/17 03:01, Rob Cresswell wrote:
>>> Hi everyone,
>>>
>>> I've put up a patch to global-requirements to raise the Django cap
>>> to "<1.11", with the upper-constraint at "1.10.7"
>>> (https://review.openstack.org/#/c/480215). Depending on the
>>> remaining time, I'd quite like to move us to "1.11.x" before
>>> Requirements Freeze, which will fall around the 27th of July.
>>>
>>> Rob
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org
>> ?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] [horizon-plugin] Raising Django version cap

[Shuu Mutou]

Hi Rob,

Thanks for the notification! I confirmed that following plugins work fine with 
Django 1.10.7.

* Magnum UI
* Senlin Dashboard
* Zaqar UI
* Zun UI


Also, I tried to use Django 1.11.3, but Horizon doesn't run. If plugin seems to 
need to fix anything, please notice us again.

Shu


> -Original Message-
> From: Rob Cresswell (rcresswe) [mailto:rcres...@cisco.com]
> Sent: Wednesday, July 05, 2017 7:24 PM
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [horizon] [horizon-plugin] Raising Django
> version cap
> 
> If you want to install Django 1.11 and test it, that would be very helpful,
> even if its just to open bugs. I’m in the process of adding a non-voting
> job for 1.11 right now, so we should be able to move quickly.
> 
> Rob
> 
> 
>   On 5 Jul 2017, at 01:36, Adrian Turjak <adri...@catalyst.net.nz
> <mailto:adri...@catalyst.net.nz> > wrote:
> 
>   Great work!
> 
>   Is there anything that can be done to help meet that July deadline
> and get 1.11.x in? I'm more than happy to help with reviews or even fixes
> for newer Django in Horizon, and we should try and get others involved if
> it will help as I think this is a little urgent.
> 
>   Running anything less than Django 1.11 leaves us in a weird spot
> because of the point where support ends for any versions below it.
> 
>   Looking at the release timelines, if we don't get 1.11 in for Pike,
> we'll have released a version of Horizon that will be for an unsupported
> version of Django in about 6 months time (8 if deployers stick with django
> 1.8):
>   https://releases.openstack.org/pike/schedule.html
>   https://www.djangoproject.com/download/
> 
>   It isn't as bad it could be, but it's an awkward situation to be
> in. 1.9 is no longer supported, 1.10 support stops at 2018, so realistically
> 1.8 is the only version to have Pike 'safe' until Queens thats not
> particularly great either. Getting 1.11 support in would be ideal.
> 
> 
> 
>   On 05/07/17 03:01, Rob Cresswell wrote:
> 
> 
>   Hi everyone,
> 
>   I've put up a patch to global-requirements to raise the
> Django cap to "<1.11", with the upper-constraint at "1.10.7"
> (https://review.openstack.org/#/c/480215). Depending on the remaining
> time, I'd quite like to move us to "1.11.x" before Requirements Freeze,
> which will fall around the 27th of July.
> 
>   Rob
> 
> 
> 
> 
>   __
> 
>   OpenStack Development Mailing List (not for usage
> questions)
>   Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <mailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> 
>   http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-
> dev
> 
> 
>   __
> 
>   OpenStack Development Mailing List (not for usage questions)
>   Unsubscribe: openstack-dev-requ...@lists.openstack.org
> <mailto:openstack-dev-requ...@lists.openstack.org> ?subject:unsubscribe
>   http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-
> dev
> 
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] [horizon-plugin] Raising Django version cap

[Rob Cresswell (rcresswe)]

If you want to install Django 1.11 and test it, that would be very helpful, 
even if its just to open bugs. I’m in the process of adding a non-voting job 
for 1.11 right now, so we should be able to move quickly.

Rob

On 5 Jul 2017, at 01:36, Adrian Turjak 
> wrote:

Great work!

Is there anything that can be done to help meet that July deadline and get 
1.11.x in? I'm more than happy to help with reviews or even fixes for newer 
Django in Horizon, and we should try and get others involved if it will help as 
I think this is a little urgent.

Running anything less than Django 1.11 leaves us in a weird spot because of the 
point where support ends for any versions below it.

Looking at the release timelines, if we don't get 1.11 in for Pike, we'll have 
released a version of Horizon that will be for an unsupported version of Django 
in about 6 months time (8 if deployers stick with django 1.8):
https://releases.openstack.org/pike/schedule.html
https://www.djangoproject.com/download/

It isn't as bad it could be, but it's an awkward situation to be in. 1.9 is no 
longer supported, 1.10 support stops at 2018, so realistically 1.8 is the only 
version to have Pike 'safe' until Queens thats not particularly great either. 
Getting 1.11 support in would be ideal.


On 05/07/17 03:01, Rob Cresswell wrote:
Hi everyone,

I've put up a patch to global-requirements to raise the Django cap to "<1.11", 
with the upper-constraint at "1.10.7" 
(https://review.openstack.org/#/c/480215). Depending on the remaining time, I'd 
quite like to move us to "1.11.x" before Requirements Freeze, which will fall 
around the 27th of July.

Rob



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] [horizon-plugin] Raising Django version cap

[Adrian Turjak]

Great work!

Is there anything that can be done to help meet that July deadline and
get 1.11.x in? I'm more than happy to help with reviews or even fixes
for newer Django in Horizon, and we should try and get others involved
if it will help as I think this is a little urgent.

Running anything less than Django 1.11 leaves us in a weird spot because
of the point where support ends for any versions below it.

Looking at the release timelines, if we don't get 1.11 in for Pike,
we'll have released a version of Horizon that will be for an unsupported
version of Django in about 6 months time (8 if deployers stick with
django 1.8):
https://releases.openstack.org/pike/schedule.html
https://www.djangoproject.com/download/

It isn't as bad it could be, but it's an awkward situation to be in. 1.9
is no longer supported, 1.10 support stops at 2018, so realistically 1.8
is the only version to have Pike 'safe' until Queens thats not
particularly great either. Getting 1.11 support in would be ideal.


On 05/07/17 03:01, Rob Cresswell wrote:
> Hi everyone,
>
> I've put up a patch to global-requirements to raise the Django cap to
> "<1.11", with the upper-constraint at "1.10.7"
> (https://review.openstack.org/#/c/480215). Depending on the remaining
> time, I'd quite like to move us to "1.11.x" before Requirements
> Freeze, which will fall around the 27th of July.
>
> Rob
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [horizon] [horizon-plugin] Raising Django version cap

[Rob Cresswell]

Hi everyone,

I've put up a patch to global-requirements to raise the Django cap to "<1.11", 
with the upper-constraint at "1.10.7" 
(https://review.openstack.org/#/c/480215). Depending on the remaining time, I'd 
quite like to move us to "1.11.x" before Requirements Freeze, which will fall 
around the 27th of July.

Rob
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [horizon] [horizon-plugin] Django Updates - Raising upper constraint to 1.9.13

[Rob Cresswell]

Hi everyone,

It's update time and we need to start raising the upper bounds on Django in 
global-requirements. We're currently capped at <1.9, which will shortly be 
raised to <1.10. This will raise the upper-constraint to 1.9.13. See 
https://review.openstack.org/#/c/453482/

Following a couple of weeks of stability testing, we'll move to 1.10.x (<1.11 
in g-r), and eventually 1.11.x (<2.0 in g-r) before the end of the Pike release 
cycle. I'll send out further emails as these patches go up.

If you are maintaining a plugin, please ensure it is functioning on Django 1.9, 
and feel free to leave comments on the requirements patch above.

Rob
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] [horizon-plugin]

[Thai Q Tran]

Hi Jason,
 
You should have access to it already. Just import from horizon the code you need. What you're looking for resides in the (request.user) object. Here are some usage examples, https://github.com/openstack/horizon/blob/master/openstack_dashboard/templatetags/context_selection.py
 
- Original message -From: Jason Pascucci <j...@juniper.net>To: "openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org>Cc:Subject: [openstack-dev] [horizon] [horizon-plugin]Date: Wed, Aug 24, 2016 12:05 PM    
Hi, 
  
What is the best method of obtaining the (name preferred) selected project (tenant) from the UI to pass to a plugin? 
  
-JRP 
  
  
__OpenStack Development Mailing List (not for usage questions)Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
 


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [horizon] [horizon-plugin]

[Jason Pascucci]

Hi,

What is the best method of obtaining the (name preferred) selected project 
(tenant) from the UI to pass to a plugin?

-JRP


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] [horizon-plugin] AngularJS 1.5.8

[Tripp, Travis S]

+1

On 8/3/16, 5:36 PM, "Thomas Goirand"  wrote:

On 08/03/2016 12:19 PM, Rob Cresswell wrote:
> Hi all,
> 
> Angular 1.5.8 is now updated in its XStatic
> repo: https://github.com/openstack/xstatic-angular
> 
> I've done some manual testing of the angular content and found no issues
> so far. I'll be checking that the JS tests and integration tests pass
> too; if they do, would it be desirable to release 1.5.8 this week, or
> wait until after N is released? It'd be nice to be in sync with current
> stable, but I don't want to cause unnecessary work a few weeks before
> plugin FF.
> 
> Thoughts?
> 
> Rob

Please go ahead. Debian Sid has 1.5.5, so even if we don't want to,
Debian will be using that version. It's better to be in sync.

Cheers,

Thomas Goirand (zigo)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] [horizon-plugin] AngularJS 1.5.8

[Thomas Goirand]

On 08/03/2016 12:19 PM, Rob Cresswell wrote:
> Hi all,
> 
> Angular 1.5.8 is now updated in its XStatic
> repo: https://github.com/openstack/xstatic-angular
> 
> I've done some manual testing of the angular content and found no issues
> so far. I'll be checking that the JS tests and integration tests pass
> too; if they do, would it be desirable to release 1.5.8 this week, or
> wait until after N is released? It'd be nice to be in sync with current
> stable, but I don't want to cause unnecessary work a few weeks before
> plugin FF.
> 
> Thoughts?
> 
> Rob

Please go ahead. Debian Sid has 1.5.5, so even if we don't want to,
Debian will be using that version. It's better to be in sync.

Cheers,

Thomas Goirand (zigo)


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [horizon] [horizon-plugin] AngularJS 1.5.8

[Richard Jones]

Let's do it, yep.

On 3 August 2016 at 20:19, Rob Cresswell 
wrote:

> Hi all,
>
> Angular 1.5.8 is now updated in its XStatic repo:
> https://github.com/openstack/xstatic-angular
>
> I've done some manual testing of the angular content and found no issues
> so far. I'll be checking that the JS tests and integration tests pass too;
> if they do, would it be desirable to release 1.5.8 this week, or wait until
> after N is released? It'd be nice to be in sync with current stable, but I
> don't want to cause unnecessary work a few weeks before plugin FF.
>
> Thoughts?
>
> Rob
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [horizon] [horizon-plugin] AngularJS 1.5.8

[Rob Cresswell]

Hi all,

Angular 1.5.8 is now updated in its XStatic repo: 
https://github.com/openstack/xstatic-angular

I've done some manual testing of the angular content and found no issues so 
far. I'll be checking that the JS tests and integration tests pass too; if they 
do, would it be desirable to release 1.5.8 this week, or wait until after N is 
released? It'd be nice to be in sync with current stable, but I don't want to 
cause unnecessary work a few weeks before plugin FF.

Thoughts?

Rob
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [horizon] [horizon-plugin] Xstatic Angular 1.4.x release

[Rob Cresswell]

Hi all,

There is a patch up to release xstatic-angular 1.4.10.1 here: 
https://review.openstack.org/#/c/348254

From our testing, the upgrade required only a single patch to Horizon, found 
here: https://review.openstack.org/#/c/309004

The migration guide can be found here: 
https://docs.angularjs.org/guide/migration#migrating-from-1-3-to-1-4

If you run into any difficulty, please ask in #openstack-horizon on IRC.

Rob
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev