Hi all,

Here’s another edition of “What’s happening on the Technical Committee.”

Meeting ======= The Technical Committee met on April 25 on the #openstack-tc channel on OFTC IRC.

The next meeting will be held on May 2 at 18:00UTC on Zoom. For more information visit https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting

Happenings ==========

Holding on dropping Python 3.8 ------------------------------ We are drafting guidelines to keep Python 3.8 support in OpenStack for 2023.2. This was discussed during Tuesday's TC meeting as it was causing significant breakage to the gate.

[0]. https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033469.ht...

New proposal to add release naming recommendations for package maintainers ------------------------------------------------------- During the last TC meeting we discussed the confusion arising from upstream OpenStack standardizing on the release names (ex. 2023.2) whereas some distros were favoring codenames (ex. Bobcat). We have a proposal up to recommend package maintainers follow our naming.[1]

[0]. https://meetings.opendev.org/meetings/tc/2023/tc.2023-04-25-18.00.log.html#l... [1]. https://review.opendev.org/c/openstack/governance/+/881712

New Upstream Investment Opportunity: Ironic ARM Support ------------------------------------------------------- Thanks to Jay Faulkner for proposing a new investment opportunity that we just merged![0]

"The OpenStack community is seeking ARM hardware and system administrators or developers with background in provisioning ARM devices to partner with the Ironic bare metal team. The Ironic project produces the OpenStack service and libraries to manage and provision physical machines."

[0]. https://governance.openstack.org/tc/reference/upstream-investment-opportunit...

Changes ======= • Merged • Add charmed openstack-hypervisor OpenStack Charms | https://review.opendev.org/c/openstack/governance/+/879437 • Update to hacking v6 (code-change) | https://review.opendev.org/c/openstack/governance/+/881266 • Switch to 2023.2 testing runtime py version (code-change) | https://review.opendev.org/c/openstack/governance/+/881137 • Correct the old deprecated policies removal timeline for SLURP release (formal-vote) | https://review.opendev.org/c/openstack/governance/+/880238 • Deprecate TripleO (formal-vote) | https://review.opendev.org/c/openstack/governance/+/877132 • Add Contribution Opportunity: Ironic ARM support (formal-vote) | https://review.opendev.org/c/openstack/governance/+/879080 • New Open • Appoint Jerry Zhou as Sahara PTL (formal-vote) | https://review.opendev.org/c/openstack/governance/+/881186 • Add recommendations for release naming to package maintainers (formal-vote) | https://review.opendev.org/c/openstack/governance/+/881712 • Align release naming terminology (documentation-change) | https://review.opendev.org/c/openstack/governance/+/881706 • Abandoned • All Open • https://review.opendev.org/q/project:openstack/governance+status:open

How to contact the TC =====================

If you would like to discuss or give feedback to TC, you can reach out to us in multiple ways:

1. Email: you can send an email with the tag [tc] on the openstack-discuss mailing list. 2. Weekly meeting: The Technical Committee conduct a weekly meeting every Thursday 16:00 UTC 3. IRC: Ping us using the 'tc-members' keyword on the #openstack-tc IRC channel on OFTC.