Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

On 2/1/2018 2:56 AM, Saverio Proto wrote: Hello ! thanks for accepting the patch :) It looks like the best is always to send an email and have a short discussion together, when we are not sure about a patch. thank you Cheers, Saverio There is also the #openstack-stable IRC channel if you

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

Hello ! thanks for accepting the patch :) It looks like the best is always to send an email and have a short discussion together, when we are not sure about a patch. thank you Cheers, Saverio __ OpenStack Development

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

On 1/31/2018 2:51 AM, Saverio Proto wrote: Hello all, I am again proposing a change due to operations experience. I am proposing a clean and simple cherry-pick to Ocata. "it depends" works pretty bad as policy for accepting patches. Now I really dont understand what is the issue with the

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

2018-01-31 17:51 GMT+09:00 Saverio Proto : > Hello all, > > I am again proposing a change due to operations experience. I am > proposing a clean and simple cherry-pick to Ocata. > > "it depends" works pretty bad as policy for accepting patches. > > Now I really dont

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

> You seem to be interested in a policy shift toward more of a "bugfix" > branch where any fix should be allowed to land, and where branch age > should not be a factor. It would be interesting to assess if that is a > general view. I know that distros in general are happy with more of a > "stable"

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

Saverio Proto wrote: > Hello all, > > I am again proposing a change due to operations experience. I am > proposing a clean and simple cherry-pick to Ocata. > > "it depends" works pretty bad as policy for accepting patches. > > Now I really dont understand what is the issue with the Stable

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

Hello all, I am again proposing a change due to operations experience. I am proposing a clean and simple cherry-pick to Ocata. "it depends" works pretty bad as policy for accepting patches. Now I really dont understand what is the issue with the Stable Policy and this patch:

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

On 11/14/2017 10:58 AM, Davanum Srinivas wrote: Let's focus our energy on the etherpad please https://etherpad.openstack.org/p/LTS-proposal On Wed, Nov 15, 2017 at 3:35 AM, Davanum Srinivas wrote: Saverio, Please see this :

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

Let's focus our energy on the etherpad please https://etherpad.openstack.org/p/LTS-proposal On Wed, Nov 15, 2017 at 3:35 AM, Davanum Srinivas wrote: > Saverio, > > Please see this : > https://docs.openstack.org/project-team-guide/stable-branches.html for > current policies. >

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

Saverio, Please see this : https://docs.openstack.org/project-team-guide/stable-branches.html for current policies. On Wed, Nov 15, 2017 at 3:33 AM, Saverio Proto wrote: >> Which stable policy does that patch violate? It's clearly a bug >> because the wrong information

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

> Which stable policy does that patch violate? It's clearly a bug > because the wrong information is being logged. I suppose it goes > against the string freeze rule? Except that we've stopped translating > log messages so maybe we don't need to worry about that in this case, > since it isn't an

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

Excerpts from Davanum Srinivas (dims)'s message of 2017-11-15 03:04:38 +1100: > Flavio, Saverio, > > Agree, that review may be a good example of what could be done. More info > below. > > Saverio said - "with the old Stable Release thinking this patch would > not be accepted on old stable

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

Flavio, Saverio, Agree, that review may be a good example of what could be done. More info below. Saverio said - "with the old Stable Release thinking this patch would not be accepted on old stable branches." My response - "Those branches are still under stable policy. That has not changed just

Re: [openstack-dev] [Openstack-operators] LTS pragmatic example

On 14/11/17 22:33 +1100, Davanum Srinivas wrote: Saverio, This is still under the stable team reviews... NOT LTS. Your contacts for the Nova Stable team is ... https://review.openstack.org/#/admin/groups/540,members Let's please be clear, we need new people to help with LTS plans. Current