Re: [openstack-dev] [stable][neutron] How we handle Kilo backports

Tony Breeds wrote: On Wed, Nov 18, 2015 at 05:44:38PM +0100, Ihar Hrachyshka wrote: Hi all, as per [1] I imply that all projects under stable-maint-core team supervision must abide the stable policy [2] which limits the types of backports for N-2 branches (now it’s

Re: [openstack-dev] [stable][neutron] How we handle Kilo backports

Erno wrote: Typo fixes are not good idea for stable branches. As it might be bit annoying or amusing for the English user fixing typos in kilo will mean that it breaks translation for all the rest and I haven't seen any translation patches being proposed to older stable

Re: [openstack-dev] [stable][neutron] How we handle Kilo backports

> -Original Message- > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > Sent: Thursday, November 19, 2015 10:43 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [stable][neutron] How we handle Kilo > backports &

Re: [openstack-dev] [stable][neutron] How we handle Kilo backports

+1 for Critical + High. Kevin Benton wrote: +1. Anything that lands in the high category is usually something that will have a big operational impact. On Wed, Nov 18, 2015 at 8:44 AM, Ihar Hrachyshka wrote: Hi all, as per [1] I imply that all projects under

[openstack-dev] [stable][neutron] How we handle Kilo backports

Hi all, as per [1] I imply that all projects under stable-maint-core team supervision must abide the stable policy [2] which limits the types of backports for N-2 branches (now it’s stable/kilo) to "Only critical bugfixes and security patches”. With that, I remind all stable core members

Re: [openstack-dev] [stable][neutron] How we handle Kilo backports

On Wed, Nov 18, 2015 at 9:44 AM, Ihar Hrachyshka wrote: > Hi all, > > as per [1] I imply that all projects under stable-maint-core team > supervision must abide the stable policy [2] which limits the types of > backports for N-2 branches (now it’s stable/kilo) to "Only

Re: [openstack-dev] [stable][neutron] How we handle Kilo backports

On Wed, Nov 18, 2015 at 12:38 PM, Carl Baldwin wrote: > On Wed, Nov 18, 2015 at 9:44 AM, Ihar Hrachyshka wrote: >> Hi all, >> >> as per [1] I imply that all projects under stable-maint-core team >> supervision must abide the stable policy [2] which limits

Re: [openstack-dev] [stable][neutron] How we handle Kilo backports

On Wed, Nov 18, 2015 at 05:44:38PM +0100, Ihar Hrachyshka wrote: > Hi all, > > as per [1] I imply that all projects under stable-maint-core team > supervision must abide the stable policy [2] which limits the types of > backports for N-2 branches (now it’s stable/kilo) to "Only critical bugfixes

Re: [openstack-dev] [stable][neutron] How we handle Kilo backports

+1. Anything that lands in the high category is usually something that will have a big operational impact. On Wed, Nov 18, 2015 at 8:44 AM, Ihar Hrachyshka wrote: > Hi all, > > as per [1] I imply that all projects under stable-maint-core team > supervision must abide the