On 2015-11-16 20:57:09 -0600 (-0600), Matt Riedemann wrote:
[...]
> Arguably we could still be testing grenade on stable/kilo by just
> installing Juno 2014.2.4 (last Juno point release before EOL) and
> then upgrading to stable/kilo.
I encourage you, say in a month's time, to try "just" installin
On 2015-11-17 02:49:30 + (+), Rochelle Grober wrote:
> I would like to make a plea that while Juno is locked down so as
> no changes can be made against it, the branch remains on the
> git.openstack.org site.
We don't so much delete the stable/juno branch as replace its final
state with a
On 17/11/15 13:38, Alan Pevec wrote:
2015-11-12 21:37 GMT+01:00 Zane Bitter :
https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:stable/juno,n,z
It would be nice to treat the remaining 'High' priority one as a blocker.
The rest aren't a blocker for the release but it wou
2015-11-12 21:37 GMT+01:00 Zane Bitter :
> https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:stable/juno,n,z
>
> It would be nice to treat the remaining 'High' priority one as a blocker.
> The rest aren't a blocker for the release but it would be really nice to at
> least h
Mailing List (not for usage
questions)
Subject: Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re:
[Openstack-operators] [stable][all] Keeping Juno "alive" for longer.
On 11/13/15, 3:23 PM, "Flavio Percoco" wrote:
On 10/11/15 16:11 +0100, Alan Pevec wrote:
Hi
> questions)
> Subject: Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re:
> [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.
>
>
>
> On 11/13/15, 3:23 PM, "Flavio Percoco" wrote:
>
> >On 10/11/15 16:11 +0100, A
On 11/12/2015 7:40 AM, Alan Pevec wrote:
This is a call to stable-maint teams for Nova, Keystone, Glance,
Cinder, Neutron, Horizon, Heat, Ceilometer, Trove and Sahara to review
open stable/juno changes[2] and approve/abandon them as appropriate.
CCing CPLs listed in
https://wiki.openstack.org
On 11/13/15, 3:23 PM, "Flavio Percoco" wrote:
>On 10/11/15 16:11 +0100, Alan Pevec wrote:
>>Hi,
>>
>>while we continue discussion about the future of stable branches in
>>general and stable/juno in particular, I'd like to execute the current
>>plan which was[1]
>>
>>2014.2.4 (eol) early Novembe
On 10/11/15 16:11 +0100, Alan Pevec wrote:
Hi,
while we continue discussion about the future of stable branches in
general and stable/juno in particular, I'd like to execute the current
plan which was[1]
2014.2.4 (eol) early November, 2015. release manager: apevec
Iff there's enough folks inte
> Speaking of your "hacky" patch: yes and no. It makes the gate passing,
> it doesn't change the code itself. For most people, this will work fine.
>
> The right way to do it, would be to create a juno branch for doa and
> cap requirements there.
>
> How to do this? Is there a procedure to request
On 13/11/15 02:49, Tony Breeds wrote:
> On Thu, Nov 12, 2015 at 02:40:19PM +0100, Alan Pevec wrote:
>
>> AFAICT there are at least two blockers for 2014.2.4: - horizon -
>> django_openstack_auth issue Tony mentions in
>> https://review.openstack.org/172826
>
> Horizon itself is fine BUT gets cau
On Thu, Nov 12, 2015 at 02:40:19PM +0100, Alan Pevec wrote:
> AFAICT there are at least two blockers for 2014.2.4:
> - horizon - django_openstack_auth issue Tony mentions in
> https://review.openstack.org/172826
Horizon itself is fine BUT gets caught up in a mess of g-r updates. The issue
at han
On 10/11/15 10:11, Alan Pevec wrote:
Hi,
while we continue discussion about the future of stable branches in
general and stable/juno in particular, I'd like to execute the current
plan which was[1]
2014.2.4 (eol) early November, 2015. release manager: apevec
Iff there's enough folks interested
Alan Pevec wrote:
This is a call to stable-maint teams for Nova, Keystone, Glance,
Cinder, Neutron, Horizon, Heat, Ceilometer, Trove and Sahara to review
open stable/juno changes[2] and approve/abandon them as appropriate.
CCing CPLs listed in
https://wiki.openstack.org/wiki/CrossProjectLiais
On 12/11/15 14:40, Alan Pevec wrote:
>> This is a call to stable-maint teams for Nova, Keystone, Glance,
>> Cinder, Neutron, Horizon, Heat, Ceilometer, Trove and Sahara to review
>> open stable/juno changes[2] and approve/abandon them as appropriate.
>
> CCing CPLs listed in
> https://wiki.opensta
> This is a call to stable-maint teams for Nova, Keystone, Glance,
> Cinder, Neutron, Horizon, Heat, Ceilometer, Trove and Sahara to review
> open stable/juno changes[2] and approve/abandon them as appropriate.
CCing CPLs listed in
https://wiki.openstack.org/wiki/CrossProjectLiaisons#Stable_Branch
Hi,
while we continue discussion about the future of stable branches in
general and stable/juno in particular, I'd like to execute the current
plan which was[1]
2014.2.4 (eol) early November, 2015. release manager: apevec
Iff there's enough folks interested (I'm not) in keep Juno alive
longer, t
17 matches
Mail list logo
