Re: [openstack-dev] [stable][neutron] Kilo is 'security-supported'. What does it imply?

Thierry Carrez wrote: Carl Baldwin wrote: - StableBranch page though requires that we don’t merge non-critical bug fixes there: "Only critical bugfixes and security patches are acceptable” Seems a little premature for Kilo. It is little more than 6 months old. Some

Re: [openstack-dev] [stable][neutron] Kilo is 'security-supported'. What does it imply?

Carl Baldwin wrote: >> - StableBranch page though requires that we don’t merge non-critical bug >> fixes there: "Only critical bugfixes and security patches are acceptable” > > Seems a little premature for Kilo. It is little more than 6 months old. > >> Some projects may want to continue

Re: [openstack-dev] [stable][neutron] Kilo is 'security-supported'. What does it imply?

+1 -Original Message- From: Carl Baldwin [mailto:c...@ecbaldwin.net] Sent: Thursday, November 05, 2015 10:20 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [stable][neutron] Kilo is 'security-supported'. What does it imply? On Thu, Nov

Re: [openstack-dev] [stable][neutron] Kilo is 'security-supported'. What does it imply?

On Thu, Nov 5, 2015 at 8:17 AM, Ihar Hrachyshka wrote: > - Releases page on wiki [2] calls the branch ‘Security-supported’ (and it’s > not clear what it implies) I saw this same thing yesterday when it was pointed out in the DVR IRC meeting [1]. I have a hard time believing

[openstack-dev] [stable][neutron] Kilo is 'security-supported'. What does it imply?

Hi all, there is contradictory info about what we do with kilo now that it’s not the latest stable release. - An old email thread [1] suggested that the branch can still receive all kinds of bug fixes as long as corresponding project teams want to spend time on it: "expanding the support