Summary: Execute a comprehensive testing and communication plan to ensure the Unified Theme, Glass, and Layout changes, high contrast mode are non-breaking for existing users. This includes coordinating with downstream products (OCP, Ansible, RHOAI, Nexus, etc.) and verifying the "opt-in" nature of new features.
Scope / Child Issues:
-
Regression Testing (Default Theme): Verify that no breaking changes have been introduced to the existing Default Theme.
-
Opt-in Verification: Confirm that all new features (Glass, Unified Theme, high contrast mode) are strictly opt-in unless explicitly configured.
-
Product Enablement (Core): Coordinate testing with OCP, Ansible, and RHOAI teams.
-
Task: Identify points of contact or solicit volunteers from these teams if enablement devs are unavailable.
-
Internal Project Sync: Coordinate with Nexus, Genie, and Hummingbird teams to ensure they are consuming the latest pre-releases and vetting new features.
-
Communication Plan: Draft release notes and migration guides highlighting the new features.
Identify release candidate versions
Get the prerelease candidates out to testers
Get the prerelease candidates approved by testers
Update staging with the release candidate versions each time we pass off a round to testers
Are any Medium articles getting published or updated on the homepage? (likely not a release blocker but a good thing to track here)
Once staging is updated, sign offs below can begin
Get release notes together and approved by epic owners
Get sign off from epic owners who are delivering epics this quarter
Get sign off from PF Design Architect
Get sign off from managers
Target release date
[make a guess, this can be updated as things evolve]
Jira Issue: PF-3176
Summary: Execute a comprehensive testing and communication plan to ensure the Unified Theme, Glass, and Layout changes, high contrast mode are non-breaking for existing users. This includes coordinating with downstream products (OCP, Ansible, RHOAI, Nexus, etc.) and verifying the "opt-in" nature of new features.
Scope / Child Issues:
Regression Testing (Default Theme): Verify that no breaking changes have been introduced to the existing Default Theme.
Opt-in Verification: Confirm that all new features (Glass, Unified Theme, high contrast mode) are strictly opt-in unless explicitly configured.
Product Enablement (Core): Coordinate testing with OCP, Ansible, and RHOAI teams.
Task: Identify points of contact or solicit volunteers from these teams if enablement devs are unavailable.
Internal Project Sync: Coordinate with Nexus, Genie, and Hummingbird teams to ensure they are consuming the latest pre-releases and vetting new features.
Communication Plan: Draft release notes and migration guides highlighting the new features.
Identify release candidate versions
Get the prerelease candidates out to testers
OCP [tag tester here]
RHOAI [tag tester here]
Ansible [tag tester here]
Cost management [tag tester here]
Others?
Get the prerelease candidates approved by testers
OCP [tag tester here]
RHOAI [tag tester here]
Ansible [tag tester here]
Cost management [tag tester here]
Others?
Update staging with the release candidate versions each time we pass off a round to testers
Are any Medium articles getting published or updated on the homepage? (likely not a release blocker but a good thing to track here)
Once staging is updated, sign offs below can begin
Get release notes together and approved by epic owners
Get sign off from epic owners who are delivering epics this quarter
Get sign off from PF Design Architect
Get sign off from managers
Target release date
[make a guess, this can be updated as things evolve]
Jira Issue: PF-3176