Hello Stackers, We're slowly approaching Milestone-1 of the 2024.2 (Dalmatian) release cycle [1]. As you observe, there is a buzz of activity across all OpenStack repositories as we've just gotten out of our design and planning event. I hope you've been enjoying the PTG summaries that have been posted thus far; I would especially recommend reading through the summary JayF put up for the Technical Committee meetings [2]. Allow me to take you through the latest news from the Technical Committee: === Weekly Meeting === Last week's TC meeting was held on IRC on Apr 23rd, 2024. The meeting was logged to eavesdrop [3]. Our main topic of discussion was about the fate of unmaintained branches, and the discussion was timely given that Elod Iles from the OpenStack Release Management SIG brought a discussion to this list about transitioning the "stable/zed" branch of all release-cycle deliverables to "unmaintained/zed" [5]. This process is underway [6]. Concerns were expressed that the unmaintained process may be easy for teams to opt in, and the burden on the "unmaintained-core" team is growing with each branch. Project Teams are expected to actively assist in transitioning branches to end-of-life. Since this isn't happening, and since the TC has noted that a number of projects have CI (Zuul) configuration errors on these "unmaintained" branches, it was proposed that we be aggressive about proposing end-of-life for unmaintained branches. It was also argued that our release model is going too fast for real-world deployments to catch up, and transitioning a lot of branches simultaneously to EOL may impact many consumers. In the interest of time during the meeting, we decided not to interfere with the transition of stable/zed to "unmaintained/zed". We encourage project leaders to: - Get their CI configuration in order for any unmaintained branches - If there is no interest/time to maintain any unmaintained branch, please actively pursue the branch's EOL process [7] In the rest of the meeting, we went through open governance proposals. We have been distracted by the PTG and Action Items across OpenStack, so some of these proposals are lacking review attention. We'll be focusing on getting these adequate review attention in the coming week/s. The next TC meeting is today, Apr 30th, 2024, at 1800 UTC on OFTC's #openstack-tc channel [4]. The agenda feels light, but we'll try to address a number of TC trackers at this meeting. This meeting is enhanced by the community's participation. We'd especially invite project leaders (PTLs, DPLs, Core maintainers) to participate and propose topics. === Goal Proposals === I'd like to request a community review of the following OpenStack community goals and updates: - Migrate eventlet usages to asyncio (https://review.opendev.org/c/openstack/governance/+/902585) - Goal: Remove eventlet requirements from shared libraries (https://review.opendev.org/c/openstack/governance/+/916546) - Add timeline to remove enforce_scope in RBAC goal (https://review.opendev.org/c/openstack/governance/+/915179) === Governance Proposals === The following governance proposals are close to being merged: - Add option to move leaderless project to Inactive status (https://review.opendev.org/c/openstack/governance/+/914726) - Appoint Wenxiang Wu as PTL of Skyline | (https://review.opendev.org/c/openstack/governance/+/915108) - Transition Freezer project to DPL | (https://review.opendev.org/c/openstack/governance/+/914911) The following governance proposals are actively being discussed: - Add DPL model & liaison reset policy (https://review.opendev.org/c/openstack/governance/+/916833) - Update to include docs and miscellaneous repos for AC status (https://review.opendev.org/c/openstack/governance/+/915021) - Clarify the timeline for a project to move to Inactive state (https://review.opendev.org/c/openstack/governance/+/908880) The following governance proposals need some review attention: - Move openstack/kuryr and openstack/kuryr-libnetwork to Zun (https://review.opendev.org/c/openstack/governance/+/917517) - 2023 User Survey TC Question Analysis (https://review.opendev.org/c/openstack/governance/+/900516) And finally, please consider volunteering as an Election official for the next OpenStack elections! [8] Thank you very much for reading! On behalf of the OpenStack TC, Goutham Pacha Ravi (gouthamr) OpenStack TC Chair [1] https://releases.openstack.org/dalmatian/schedule.html [2] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.... [3] https://meetings.opendev.org/meetings/tc/2024/tc.2024-04-23-18.00.log.html [4] https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting [5] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.... [6] https://review.opendev.org/q/topic:zed-unmaintained [7] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branch... [8] https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack....