From 88d489a532e272e7146f41f3b9b696f8fc5b210a Mon Sep 17 00:00:00 2001 From: Iury Gregory Melo Ferreira Date: Wed, 18 Mar 2020 14:49:35 +0100 Subject: [PATCH] Document our policies for stable branches Action item from our weekly-meeting. Change-Id: I761e55d0aec9dd8ff64cab346c72ffbf40f242e4 --- doc/source/contributor/index.rst | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/doc/source/contributor/index.rst b/doc/source/contributor/index.rst index 256f9be52e..136827f94c 100644 --- a/doc/source/contributor/index.rst +++ b/doc/source/contributor/index.rst @@ -113,3 +113,25 @@ the documentation below. Job roles in the CI How to add a new job? How to debug failures in CI jobs + +Our policy for stable branches +------------------------------ + +Stable branches that are on `Extended Maintenance`_ and haven't received +backports in a while, can be tagged as ``Unmaintained``, after discussions +within the ironic community. If such a decision is taken, an email will +be sent to the OpenStack mailing list. + +What does ``Unmaintained`` mean? The branch still exists, but the ironic +upstream community will not actively backport patches from maintained +branches. Fixes can still be merged, though, if pushed into review by +operators or other downstream developers. It also means that branchless +projects (e.g.: ironic-tempest-plugin), may not have configurations that are +compatible with those branches. + +As of 09 March 2020, the list of ``Unmaintained`` branches includes: + +* Ocata (Last commit - Jun 28, 2019) +* Pike (Last commit - Oct 2, 2019) + +.. _Extended Maintenance: https://docs.openstack.org/project-team-guide/stable-branches.html#maintenance-phases