Uploaded image for project: 'Automation Analytics'
  1. Automation Analytics
  2. AA-1807

PatternFly 5 Upgrade Enablement Plan - looking out for regressions

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • None
    • UI
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ANSTRAT-37 - Introduce a gateway service to AAP that serves a centralized Platform UI

      We will NOT update. We WILL LOOK OUT for regressions.

       

      Email from c.r.com team:

       

      This email contains important information on upcoming changes to console.redhat.com that require action.

      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 and email 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.

      We are asking each tenant team to clone this ticket and track the progress of their regression testing per each environment.  Please move the cloned story to your appropriate Jira project but maintain a linking relationship with the 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

      Relevant Jira(s): RHCLOUD-27561, RHCLOUD-27562

      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

      • 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 or Nicole Thoen with any questions. 

      ConsoleDot Actions Required & Releases Source page is here.

              Unassigned Unassigned
              znemecko Zita Nemeckova
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: