TO refine

Testing and docs to support Ceph-9 release

Goals:

• Need full list
• Produce Internal doc on the process for bumping major release version
•  

Accept Criteria

• Enable Official support for RHCS-9
• Current testing matrix integration:
  • rhoso 18 greenfield: gamma 7, delta (ganesha+rgw) 8, epsilon (cinder) 7
  • rhoso 18 adoption: gamma 7
• Component level : cinder+glance at 7
• considerations:
  • bump delta to 9
  • gamma greenfield to 8
  • epsilon greenfield to 8
• documentation
  • may have known limitations (needs downstream ceph ga bits first)
  • Will need to document 

Open Questions

• If Manila or RGW not ready, do we release like last time with what's ready and follow up?
•  

----

Feature Overview (mandatory - Complete while in New status)
An elevator pitch (value statement) that describes the Feature in a clear, concise way. ie: Executive Summary of the user goal or problem that is being solved, why does this matter to the user? The “What & Why”... 
Ceph 9 GA Oct 22 2025

https://productpages.redhat.com/ceph-9-0/schedule/tasks/ 

Goals (mandatory - Complete while in New status)

• upstream: change upstream operator CI, and devstack-plugin-ceph to upstream T (aka ceph 9)
• downstream: change a job to use ceph 9

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):
Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Feature. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view
…
<your text here>

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):
High-level list of items or persona’s that are out of scope.
<your text here>

Documentation Considerations {}{}(Initial completion while in Refinement status):
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..
<your text here>

Questions to Answer {}{}(Initial completion while in Refinement status):
Include a list of refinement / architectural questions that may need to be answered before coding can begin.
<your text here>

Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>

Customer Considerations {}{}(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

Team Sign Off (Completion while in Planning 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

• …