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 because of an email thread or a discussion in Forum"
Saverio said - "Let's see if this gets accepted back to stable/newton"
My response - "The branch the review is against is still under stable
policy. So things that will or will not be backported will not change"
Saverio said - "Please note that a developers/operators that make the
effort of fixing this in master, should do also all the cherry-pickes
back. We dont have any automatic procudure for this."
My response - "How the cherry-picks are done for stable branches will
not change. This is a stable branch, so there is no automatic
procedure for backporting"
I really want folks to help with stable first, learn how things are
done and then propose changes to stable branch policies and help
If folks want to chase LTS, then we are outlining a procedure/process
that is a first step towards LTS eventually.
On Wed, Nov 15, 2017 at 2:46 AM, Flavio Percoco email@example.com wrote:
On 14/11/17 22:33 +1100, Davanum Srinivas wrote:
This is still under the stable team reviews... NOT LTS.
Your contacts for the Nova Stable team is ...
Let's please be clear, we need new people to help with LTS plans.
Current teams can't scale, they should not have to and it's totally
unfair to expect them to do so.
I think you may have misunderstood Saverio's email. IIUC, what he was trying
do was provide an example in favor of the LTS branches as discussed in
rather than requesting for reviews or suggesting the stable team should do
On Tue, Nov 14, 2017 at 8:02 PM, Saverio Proto firstname.lastname@example.org wrote:
here an example of a trivial patch that is important for people that
do operations, and they have to troubleshoot stuff.
with the old Stable Release thinking this patch would not be accepted
on old stable branches.
Let's see if this gets accepted back to stable/newton
Please note that a developers/operators that make the effort of fixing
this in master, should do also all the cherry-pickes back. We dont
have any automatic procudure for this.
Davanum Srinivas :: https://twitter.com/dims
OpenStack Development Mailing List (not for usage questions)