Re: [openstack-dev] [depfreeze][horizon] Update to Django-1.7.x

2015-03-26 Thread Matthias Runge
On Thu, Mar 26, 2015 at 06:02:41AM -0400, Sean Dague wrote: > > Yes, just approved. Thank you, much appreciated! -- Matthias Runge __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-

Re: [openstack-dev] [depfreeze][horizon] Update to Django-1.7.x

2015-03-26 Thread Sean Dague
On 03/26/2015 03:40 AM, Matthias Runge wrote: > On Wed, Mar 25, 2015 at 12:00:11PM +0100, Matthias Runge wrote: >> On 25/03/15 11:34, Sean Dague wrote: >> Could you make this one "Depends on" https://review.openstack.org/#/c/167515/ so that we check that all Django 1.7 related issues

Re: [openstack-dev] [depfreeze][horizon] Update to Django-1.7.x

2015-03-26 Thread Matthias Runge
On Wed, Mar 25, 2015 at 12:00:11PM +0100, Matthias Runge wrote: > On 25/03/15 11:34, Sean Dague wrote: > > >>Could you make this one "Depends on" > >>https://review.openstack.org/#/c/167515/ so that we check that all > >>Django 1.7 related issues are fixed ? > > > >I don't think it was ever suffic

Re: [openstack-dev] [depfreeze][horizon] Update to Django-1.7.x

2015-03-25 Thread Matthias Runge
On 25/03/15 11:34, Sean Dague wrote: Could you make this one "Depends on" https://review.openstack.org/#/c/167515/ so that we check that all Django 1.7 related issues are fixed ? I don't think it was ever sufficiently explained why horizon now needs django nose to compile it's message catalog

Re: [openstack-dev] [depfreeze][horizon] Update to Django-1.7.x

2015-03-25 Thread Sean Dague
On 03/25/2015 05:04 AM, Thierry Carrez wrote: > Matthias Runge wrote: >> I'm requesting an exception to bump Django to Django-1.7.x (or better). >> >> Rationale: >> >> Django-1.8 is expected to be released during the next days. Once it's >> released, Django-1.6.x will become unsupported by its upst

Re: [openstack-dev] [depfreeze][horizon] Update to Django-1.7.x

2015-03-25 Thread Thierry Carrez
Matthias Runge wrote: > I'm requesting an exception to bump Django to Django-1.7.x (or better). > > Rationale: > > Django-1.8 is expected to be released during the next days. Once it's > released, Django-1.6.x will become unsupported by its upstream. > Unfortunately that's the latest version we'r