Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?
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 ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?
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, 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 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 :) >> But please look here at page 20: >> https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf >> >> Most production systems are on old releases. >> Kilo is not that old ! And I am really curious to see the results of >> the next Survey. >> We would like to avoid to have each installation with custom packages. >> >> I think this email thread was a good example on how we can improve >> operators to developers feedback to have better stable branches. >> Operators should not be afraid of proposing a cherry-pick to stable >> branch, especially if it fixes a non-corner case problem, and if it >> easy to review. >> >> my 2 cents :) >> >> Cheers, >> >> Saverio >> >> ___ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> > > > DataCentred Limited registered in England and Wales no. 05611763 > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?
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 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 :) > But please look here at page 20: > https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf > > Most production systems are on old releases. > Kilo is not that old ! And I am really curious to see the results of > the next Survey. > We would like to avoid to have each installation with custom packages. > > I think this email thread was a good example on how we can improve > operators to developers feedback to have better stable branches. > Operators should not be afraid of proposing a cherry-pick to stable > branch, especially if it fixes a non-corner case problem, and if it > easy to review. > > my 2 cents :) > > Cheers, > > Saverio > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- DataCentred Limited registered in England and Wales no. 05611763 ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?
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 :) But please look here at page 20: https://www.openstack.org/assets/survey/Public-User-Survey-Report.pdf Most production systems are on old releases. Kilo is not that old ! And I am really curious to see the results of the next Survey. We would like to avoid to have each installation with custom packages. I think this email thread was a good example on how we can improve operators to developers feedback to have better stable branches. Operators should not be afraid of proposing a cherry-pick to stable branch, especially if it fixes a non-corner case problem, and if it easy to review. my 2 cents :) Cheers, Saverio ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?
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 for pointing this out. Bug fixes are mostly backported to Liberty release, in some rare cases Kilo might get a fix as well. Matthias ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?
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 OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?
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. 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 Mar 3, 2016 8:43 AM, "Saverio Proto" wrote: >> >> 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 production system to from Juno to Kilo and we run >> into this bug >> >> https://review.openstack.org/#/c/185403/ >> >> This is the commit the fixes the bug (Horizon repository): >> git show 8201d65c >> >> I remember someone saying that this bug can be tagged somewhere to >> request the backport to Kilo ... how do I do this ?? >> >> I have put James in Cc: because he was super kind in Manchester, and I >> he show me how to correctly package for Ubuntu. >> Once the change is merged into stable/kilo branch I will try to kindly >> ask to the people from Ubuntu Cloud Archive to refresh Kilo packages. >> Or even better I will try to help them with the packaging and testing. >> >> Let's try to start this workflow to see how long it takes ?? Do you >> guys consider this example a good follow up to the discussion we had >> in Manchester ? >> >> If we give up, we will have to build our own Kilo packages for Kilo >> even before going to production ;) >> >> thanks ! >> >> Saverio >> >> ___ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
Re: [Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?
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 Thu, Mar 3, 2016 at 8:40 AM, Saverio Proto wrote: > 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 production system to from Juno to Kilo and we run > into this bug > > https://review.openstack.org/#/c/185403/ > > This is the commit the fixes the bug (Horizon repository): > git show 8201d65c > > I remember someone saying that this bug can be tagged somewhere to > request the backport to Kilo ... how do I do this ?? > > I have put James in Cc: because he was super kind in Manchester, and I > he show me how to correctly package for Ubuntu. > Once the change is merged into stable/kilo branch I will try to kindly > ask to the people from Ubuntu Cloud Archive to refresh Kilo packages. > Or even better I will try to help them with the packaging and testing. > > Let's try to start this workflow to see how long it takes ?? Do you > guys consider this example a good follow up to the discussion we had > in Manchester ? > > If we give up, we will have to build our own Kilo packages for Kilo > even before going to production ;) > > thanks ! > > Saverio > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
[Openstack-operators] Horizon bug fixed in Liberty, how should we ask a backport to Kilo ?
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 production system to from Juno to Kilo and we run into this bug https://review.openstack.org/#/c/185403/ This is the commit the fixes the bug (Horizon repository): git show 8201d65c I remember someone saying that this bug can be tagged somewhere to request the backport to Kilo ... how do I do this ?? I have put James in Cc: because he was super kind in Manchester, and I he show me how to correctly package for Ubuntu. Once the change is merged into stable/kilo branch I will try to kindly ask to the people from Ubuntu Cloud Archive to refresh Kilo packages. Or even better I will try to help them with the packaging and testing. Let's try to start this workflow to see how long it takes ?? Do you guys consider this example a good follow up to the discussion we had in Manchester ? If we give up, we will have to build our own Kilo packages for Kilo even before going to production ;) thanks ! Saverio ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
