On 11/16/2015 8:49 PM, 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.  Please?  
One area that could be better investigated with the branch in place is upgrade. 
 Kilo will continue to get patches, as will Liberty, so an occasional grenade 
run (once a week?  more often?  Less often) could help operators understand 
what is in store for them when they finally can upgrade from Juno.  Yes, it 
will require occasional resources for the run, but I think this is one of the 
cheapest forms of insurance in support of the installed base of users, before a 
Stable Release team is put together.

My $.02

--Rocky

-----Original Message-----
From: Gary Kotton [mailto:[email protected]]
Sent: Friday, November 13, 2015 6:04 AM
To: Flavio Percoco; OpenStack Development 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" <[email protected]> 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 November, 2015. release manager: apevec

Iff there's enough folks interested (I'm not) in keep Juno alive

+1 I do not see any reason why we should still invest time and effort
here. Lets focus on stable/kilo

longer, they could resurrect it but until concrete plan is done let's
be honest and stick to the agreed plan.

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.
Proposed timeline is:
* Thursday Nov 12 stable/juno freeze[3]
* Thursday Nov 19 release 2014.2.1


General ack from a stable-maint point of view! +1 on the above

Flavio

Cheers,
Alan

[1]
https://wiki.openstack.org/wiki/StableBranchRelease#Planned_stable.2F
juno
_releases_.2812_months.29

[2]
https://review.openstack.org/#/q/status:open+AND+branch:stable/juno+A
ND+%
28project:openstack/nova+OR+project:openstack/keystone+OR+project:ope
nsta
ck/glance+OR+project:openstack/cinder+OR+project:openstack/neutron+OR
+pro
ject:openstack/horizon+OR+project:openstack/heat+OR+project:openstack
/cei
lometer+OR+project:openstack/trove+OR+project:openstack/sahara%29,n,z

[3] documented  in
https://wiki.openstack.org/wiki/StableBranch#Stable_release_managers
TODO add in new location
http://docs.openstack.org/project-team-guide/stable-branches.html

_____________________________________________________________________
____
_
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
[email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
@flaper87
Flavio Percoco


_______________________________________________________________________
___
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-
[email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


I'm assuming you mean grenade runs on stable/kilo. A grenade job on stable/kilo is installing stable/juno and then upgrading to stable/kilo (the change being tested is on stable/kilo). The grenade jobs for stable/juno were stopped when icehouse-eol happened.

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.

--

Thanks,

Matt Riedemann


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to