openstack/governance
Code Issues Proposed changes

Resolution: Remove Murano from 2024.1 release

Browse Source 
This is a special case to remove Murano for being inactive after
milestone-2.

Change-Id: I93bc6b0f7fc9107ed07dc92f13193edb50d75cd2
This commit is contained in:
Jay Faulkner 2024-02-27 11:22:04 -08:00
parent 1b43c61e0b
commit 961d17b622
2 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
resolutions/20240227-remove-murano-from-2024-1-release.rst Normal file
View File

@ -0,0 +1,15 @@
============================================
2024-02-27 Remove Murano from 2024.1 Release
============================================
The Technical Committee recently identified that the Murano project is
inactive and has critical bugs which make it unsuitable for use in
production in its current form. However, the current policy around
`Emerging and inactive projects <https://governance.openstack.org/tc/reference/emerging-technology-and-inactive-projects.html>`__
only permits a project to be removed from the release if identified as
inactive before milestone-2.
This TC resolution instructs the releases team to cease release activities
for Murano for the 2024.1 release. It shall remain excluded from OpenStack
releases until CI is fixed, all known security issues are resolved, and
there is maintainer activity consistant with a healthy OpenStack project.

10
resolutions/index.rst
View File

@ -7,6 +7,16 @@
When a motion does not result in a change in a reference doc, it can When a motion does not result in a change in a reference doc, it can
be expressed as a resolution. be expressed as a resolution.
2024
====
.. toctree::
:maxdepth: 1
:glob:
:reversed:
2024*
2023 2023
==== ====