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 <saverio.pr...@switch.ch> wrote: >> 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 exception. > > Well, I also would like to understand more about stable policy violations. > When I proposed such patches in the past for the release N-2 I have > always got the answer: it is not a security issue so it will not be merged. > > This is a good example of how things have been working so far: > > https://review.openstack.org/#/q/677eb1c4160c08cfce2900495741f0ea15f566fa > > This cinder patch was merged in master. It was then merged in Mitaka. > But it was not merged in Liberty just because "only security fixes" were > allowed at that point. > > You can read that in the comments: > https://review.openstack.org/#/c/306610/ > > Is this kind of things going to change after the discussion in Sydney ? > The discussion is not enough ? what we need to get done then ? > > thank you > > Saverio > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
