openstack/horizon
Code Issues Proposed changes

Merge "[doc] Add documentation about the release process in horizon"

Browse Source
This commit is contained in:
Zuul 2022-03-31 12:37:05 +00:00 committed by Gerrit Code Review
commit f5a89f93bf
2 changed files with 42 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/source/contributor/policies/index.rst
View File

@ -11,3 +11,4 @@ This page collects basic policies on horizon development.
horizon-groups
core-reviewers
horizon-bugs
releasing

41
doc/source/contributor/policies/releasing.rst Normal file
View File

@ -0,0 +1,41 @@
==========================
Releasing Horizon Projects
==========================
Since the responsibility for releases will move between people, we document
that process here.
A full list of projects that horizon manages is available in the
`governance site <https://governance.openstack.org/reference/projects/horizon.html>`__.
Who is responsible for releases?
--------------------------------
The current PTL is ultimately responsible for making sure code gets released.
They may choose to delegate this responsibility to a liaison, which is
documented in the `cross-project liaison wiki
<https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management>`__.
Anyone may submit a release request per the process below, but the PTL or
liaison must +1 the request for it to be processed.
Release process
---------------
Releases are managed by the OpenStack release team. The release process is
documented in the `Project Team Guide
<https://docs.openstack.org/project-team-guide/release-management.html#how-to-release>`__.
In general, horizon deliverables follow the `cycle-with-intermediary
<https://releases.openstack.org/reference/release_models.html#cycle-with-intermediary>`__
release model.
Things to do before releasing
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Update default policy-in-code rules in horizon for all backend services
like cinder/glance/keystone/neutron/nova. For more information on how to
update these policy rules see the :doc:`/contributor/topics/policy`.
* Check for any open patches that are close to be merged or release critical.
This usually includes important bug fixes and/or features that we'd
like to release, including the related documentation.