From 97bcf0354c897d4a6f29606b4f305edd94df6c2f Mon Sep 17 00:00:00 2001 From: Mark Goddard Date: Wed, 25 Nov 2020 17:17:54 +0000 Subject: docs: stable branch lifecycle Change-Id: Ie8ee04f036cf576888964d24b4eee83bce12a9c5 --- doc/source/contributor/release-management.rst | 31 +++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) (limited to 'doc/source') diff --git a/doc/source/contributor/release-management.rst b/doc/source/contributor/release-management.rst index c686c0dfc..cc482dae4 100644 --- a/doc/source/contributor/release-management.rst +++ b/doc/source/contributor/release-management.rst @@ -230,3 +230,34 @@ branch, no less than once every 45 days. * mark milestones on Launchpad as released * create new milestones on Launchpad for the next stable releases + +Branch Lifecycle +================ + +The lifecycle of stable branches in OpenStack is described in the `project team +guide `__. +The current status of each branch is published on the `releases +`__ site. + +Extended Maintenance (EM) +------------------------- + +When a branch is entering EM, projects will make final releases. The release +team will propose tagging the Kolla deliverables as EM, but this should only be +done once all other dependent projects have made their final release, and final +Kolla releases have been made including those dependencies. + +After a branch enters EM, we typically do the following: + +* stop backporting fixes to the branch by default. Important fixes or those + requested by community members may be merged if deemed appropriate +* stop publishing images to Dockerhub +* stop actively maintaining CI + +End of Life (EOL) +----------------- + +Once a branch has been unmaintained (failing CI, no patches merged) for 6 +months, it may be moved to EOL. Since this is done at different times for +different projects, send an email to openstack-discuss to keep the community +informed. -- cgit v1.2.3