openstack
/
grenade
Code Issues Proposed changes

Adding document on Extended Maintainance testing policy 

As communicated in ML thread
- http://lists.openstack.org/pipermail/openstack-discuss/2020-June/015499.html

grenade team will only be responsible for maintaining the 'Maintained' stable
branches only not the EM. We will start making the grenade job on EM and oldest
'Maintained' as n-v if they start failing.

This commits document that agreement so that it can be followed consistently.

Change-Id: I615a6b88d39ab1c91fdf57b3393cbbca66833671
This commit is contained in:
Ghanshyam Mann 2020-06-18 18:13:17 -05:00 committed by Radosław Piliszek
parent 92d61393fd
commit d47289f3b1
2 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/source/index.rst
View File

@ -10,6 +10,7 @@ Grenade - an OpenStack Community Upgrade Production
plugins
plugin-registry
hacking
stable_branch_testing_policy
Code
====

23
doc/source/stable_branch_testing_policy.rst Normal file
View File

@ -0,0 +1,23 @@
Stable Branch Testing Policy
============================
Since the `Extended Maintenance policy`_ for stable branches was adopted,
OpenStack projects are keeping stable branches around after a "stable"
or "maintained" period, for a phase of indeterminate length called "Extended
Maintenance". Prior to this resolution, Grenade supported a running
voting job down to the oldest+1 stable branch which was supported upstream.
Grenade testing on any branch requires prior branch in a working state,
DevStack-wise.
Due to this requirement and team's resource constraints, Grenade will only
provide support for branches in the "Maintained" phase from the documented
`Support Phases`_. This means Grenade testing on oldest "Maintained" and all
"Extended Maintenance" branches will be made non-voting if they start
failing. All other "Maintained" branches, that is down to the oldest
"Maintained"+1, will be tested and maintained by the Grenade team.
"Extended Maintenance" team, if any, is always welcome to maintain the Grenade
testing on "Extended Maintenance" branches and the oldest "Maintained" branch,
and make the jobs voting again.
.. _Extended Maintenance policy: https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html
.. _Support Phases: https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases