openstack
/
project-team-guide
Code Issues Proposed changes

Clarify Extended Maintenance branch testing and support policy 

We at upstream community cannot commit to the maintenance of
Extended Maintenance branches and its testing. Idea behind the
Extended Maintenance is to keep them open as long as we can and
anyone backporting the fixes take care of tetsing fix or so.

Change-Id: Ide5d13139493737e5ce948b62cd1da9aad7022c7
This commit is contained in:
Ghanshyam Mann 2022-10-13 01:37:49 -05:00
parent 7cbeb0de40
commit 1246dcbb32
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/stable-branches.rst
View File

@ -67,7 +67,16 @@ Extended Maintenance
Once a branch reaches Extended Maintenance project teams will cease producing
releases and `OpenStack Vulnerability Management`_ will be reasonable efforts
only. There is no statement about the level of testing and upgrades from
Extended Maintenance are not supported within the Community.
Extended Maintenance are not supported within the Community. There should not
be an expectation on the upstream community team to keep maintaining the
Extended Maintenance stable branches upstream testing. We will keep them open
as long as possible so that any operator or user will be able to backport
required fixes. Without regular comprehensive maintenance, it is quite possible
that someone proposing a backport to an EM branch will find that tests have
broken since the last successful merge. This means that tests (or test
configuration) might need to be fixed, reduced, or reconfigured before the
backport itself can be evaluated and merged. The onus for that falls on the
backporter or the group of people looking after a specific release.
The ``last release`` of the appropriate branch will be tagged as
``$series-em``, for example: https://review.opendev.org/608296/.