D10: Test, Readiness, and Deployment Planning

[productmike]

Background

Drupal 10 has been released and ready for upgrade. Our current version will be supported by Drupal until 11/2023. This is considered a technical epic and therefore is a task oriented epic and driven by the devs.

User Story or Problem Statement

How might we update the drupal instance in a collaborative way so that risks for downstream products are mitigated while completing the upgrade at least a month prior to support run-out?

Affected users and stakeholders

• CMS editors
• Veteran beneficiaries of existing CMS editors
• VFS-Public Websites product team
• VFS-Facilities product team

Assumptions & Risks

• CKEditor5 upgrade will be included in the D10 upgrade.
• Public Websites and Facilities will be able to support test timing within their existing roadmap.
• Components where OIT assist is needed will be identified and supported by OIT prior to final deploy -- e.g. SAML.

Acceptance Criteria

• Automated tests has been cleaned up.
• Ownership of CMS components have been clearly identified and agreed to with Public Websites (incl PO).
• Ownership of CMS components have been clearly identified and agreed to with Facilities (incl PO).
• Test plan - including timelines (e.g. sprints) - has been established with Public Websites.
• Test plan - including timelines (e.g. sprints) - has been established with Facilities.
• Defect capturing process has been articulated by CMS team for core components. Includes clear priority definition.
• Defect review has been held with Facilities, Public Websites.
• Go/no go meet has occurred with Facilities, Public Websites.
• Deployment timing has been well communicated across teams (incl POs) -- along with identified areas of ownership.
• Post-deploy release management has been agreed to and well comminucated.
• Runbook has been created to document process used for D10.
• Post-deploy retro held to determine necessary updates to runbook.

[EWashb]

We need to revisit this epic and the associated tickets to confirm what we're doing. Also, some of these ACs should have already been completed or nearly there. It's hard to see what the truth of the current state of our efforts from this epic. Let's bring this back around for refinement.

[BerniXiongA6]

@maortiz-27-80 this has not been updated, but might be helpful if we want to repurpose any of it for Drupal 10 deployment. We can discuss. cc: @EWashb