-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
PatternFly 5 Upgrade: Tenant Regression tracking
-
False
-
-
False
-
Unset
-
To Do
-
0% To Do, 0% In Progress, 100% Done
-
-
WHAT & WHEN
On August 14, Chrome will start moving forward with the upgrade to using PatternFly 5 and will complete in production on September 25. Once Chrome adopts PatternFly 5, applications can proceed with their update. PatternFly 4 will continue to be supported in all environments.
PatternFly 5 provides:
- React 18 Support
- Optimized build for module federation to enable smaller bundle sizes
- Updated, more flexible, lightweight implementations of popular components such as Wizard, Select, Dropdown, Table
- Accessibility improvements
- More consistent API, especially for form elements
- Groundwork laid for streamlined adoption of PatternFly’s future updated ‘look & feel’
For more information about the PatternFly 5 major release and adoption, please visit this slide deck.
Frontend-components will also be updating to a major release to reflect the new changes in both React 18 and PatternFly 5. We will continue to support our last major release for any critical bug fixes.
Tenants DO NOT have to release on the date that chrome is updated. Chroming must go first, but you are welcome to upgrade anytime after.
August 21: stage-preview
September 4: production-preview
September 11: stage-stable
September 25: production-stable
We will send out a message after each environment has been updated in order to allow teams to check for regressions. If a bug is noticed, please reach out to PatternFly or the Platform Experience team and add your bug as a direct issue of <this epic>.
Once the Chroming has been updated in each environment, teams are allowed to update their individual applications.
WHO
This will require changes from the following: ALL frontend applications on the Hybrid Cloud Console.
ADDITIONAL INFORMATION
Please review the following post for details of the change, requirements, background information, and references: <the source blog URL>.
Relevant Jira(s): <Required: Jira for tracking and sub-tasks to be created by tenants>
PatternFly will be presenting at this week’s (10 Aug) Interlock call.
There are additional resources for developers to use in order to ease the transition from PatternFly 4 to PatternFly 5
- Upgrade guide: https://www.patternfly.org/get-started/upgrade
- Codemods: https://github.com/patternfly/pf-codemods
- Release highlights: https://www.patternfly.org/get-started/release-highlights
- PatternFly Slack workspace (invite)
PatternFly is adopting an annual major release cadence. This is to reduce the size and effort of future releases by avoiding a large backlog of breaking issues built up over several years. Read more about future PatternFly releases here.
Contact Ryan Long, Nicole Thoen, Martin Marosi, or Kat Dixon with any questions.
ConsoleDot Actions Required & Releases Source page is here.