Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?

2016-03-04 Thread Matthias Runge
On 04/03/16 10:47, James Page wrote: > Added a bug task for the Kilo UCA - this should be picked up in the next > round of kilo updates for the UCA. > I cherry-picked the fix into Red Hat OpenStack version 7, tracking bug is https://bugzilla.redhat.com/show_bug.cgi?id=1314698 Matthias

Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?

2016-03-04 Thread James Page
Added a bug task for the Kilo UCA - this should be picked up in the next round of kilo updates for the UCA. On Fri, 4 Mar 2016 at 08:35 Matt Jarvis wrote: > This thread is a great example of the value of the midcycle meetups :) > > On 4 March 2016 at 08:09,

Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?

2016-03-04 Thread Matt Jarvis
This thread is a great example of the value of the midcycle meetups :) On 4 March 2016 at 08:09, Saverio Proto wrote: > Thanks for merging the patch so quickly ! I will try today to build > new ubuntu packages and and for feedback at UCA. > > > But yes, thank you for

Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?

2016-03-04 Thread Saverio Proto
Thanks for merging the patch so quickly ! I will try today to build new ubuntu packages and and for feedback at UCA. > But yes, thank you for pointing this out. Bug fixes are mostly > backported to Liberty release, in some rare cases Kilo might get a fix > as well. This is an endless discussion

Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?

2016-03-03 Thread Matthias Runge
On 03/03/16 19:00, Sean M. Collins wrote: > Kilo is in the security supported stage of the lifecycle. > > http://releases.openstack.org/ > > So, unless it is a security bug, I do not believe that this will be > able to be backported. > In this case, it was already merged. But yes, thank you

Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?

2016-03-03 Thread Sean M. Collins
Kilo is in the security supported stage of the lifecycle. http://releases.openstack.org/ So, unless it is a security bug, I do not believe that this will be able to be backported. -- Sean M. Collins ___ OpenStack-operators mailing list

Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?

2016-03-03 Thread Saverio Proto
Thanks Matt ! I logged in and now I see the cherry-pick button. I should use the web interface always logged in :) Thank you Saverio 2016-03-03 16:51 GMT+01:00 Matt Fischer : > The backport is pretty easy. You click on Cherry pick and if there's no > conflict it just works.

Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?

2016-03-03 Thread Matt Fischer
The backport is pretty easy. You click on Cherry pick and if there's no conflict it just works. Like so: https://review.openstack.org/#/c/287928/ It still needs to go through the review process so you will need to ping some horizon developers in IRC. Getting that packaged may take longer. On

[Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?

2016-03-03 Thread Saverio Proto
Hello there, in Manchester we had this interesting discussion about asking to backport bugfixes in order to avoid to build own packages. https://etherpad.openstack.org/p/MAN-ops-Upgrade-patches-packaging We run Openstack with Ubuntu and we use the Ubuntu Cloud Archive. We are upgrading our