Hi all,

This change has merged and is viewable here: https://governance.openstack.org/tc/resolutions/20240227-remove-murano-from-2024-1-release.html.

Murano will not be included in the 2024.1 release, and is likely to be added to the inactive projects list[0]. It's my recommendation that you avoid running it in production until or unless the project returns to an active state.

Thanks,

Jay Faulkner

OpenStack TC Chair

0: https://review.opendev.org/c/openstack/governance/+/908859

On Tue, Feb 27, 2024 at 3:34 PM Jay Faulkner <jay@gr-oss.io> wrote:

Hi all,

After discussion in the TC meeting today about lots of gathered evidence that Murano is inactive and plagued by serious bugs, I have proposed a resolution to remove Murano from the release. This is roughly equivalent to marking it inactive; however we can only use inactive status to remove things from the release before milestone-2. At this point, the TC is too late discovering the bad state of Murano to use inactivity to prevent its release. Therefore, I have proposed a special-case resolution[0] reflecting general consensus in the TC meeting that Murano should not be released.

I wanted to inform the community of this resolution, and advise anyone who may be considering deployment of Murano to be aware of its current inactive state. Additionally, if you believe our evaluation of the situation is wrong, feel free to let your voice be heard in Gerrit.

Thanks,
Jay Faulkner
OpenStack TC Chair

0: https://review.opendev.org/c/openstack/governance/+/910434