Feature Overview (mandatory - Complete while in New status)
Python 3.11 will go out of support during the RHEL 9.6 timeframe. We need to move the platform, and all products on top of it, up to python 3.12 before that happens.

Goals (mandatory - Complete while in New status)

Set Python 3.12 from RHEL as the default Python interpreter in our base images and builder images.

Build all packages managed by the builder image under Python 3.12.

Requirements (mandatory -_ Complete while in Refinement status):
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

Done - Acceptance Criteria (mandatory - Complete while in Refinement status):
We release application and base images with Python 3.12

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
<your text here>

Out of Scope _{}(Initial completion while in Refinement status):{_}
We do not need to update instructlab to support python 3.12.

We do not need to build RHEL AI's dependencies on python 3.12.

Documentation Considerations _{}(Initial completion while in Refinement status):{_}

We need to advertise that this change is coming and then document the python version as part of the release notes for the base images and builder image.

Questions to Answer _{}(Initial completion while in Refinement status):{_}
vllm is part of our test collection. Will we have to update to a newer vllm in order to move the python version?

Background and Strategic Fit (Initial completion while in Refinement status):
Updating the python version is part of keeping our stack running on supported components.

Customer Considerations _{}(Initial completion while in Refinement status):{_}
Customers who make their own notebook images will need to update as well, unless they build their images from scratch.

Team Sign Off (Completion while in Refinement status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

*An engineer or tech lead from the product requesting this feature is required for the signoff below.

• …