Versions Compared

Version Old Version 24 New Version Current
Changes made by

Julian Ladisch

Julian Ladisch

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Slack channel renamed: folio-release_bug_triage

...

  1. The Requestor PO submits a request for a CSP to the #release#folio-release_bug_triage channel, tagging @folio_rms, and providing a link to a Jira ticket which describes the issue and has:

    • The “Release” field set to <Target release> Service Patch <Number> for the targeted CSP release e.g. “Quesnelia (R1 2024) Service Patch #8”

    • The “RCA” field populated

    • Test cases in TestRail linked

    • The “CSP Request Details” field populated with the Required information for a CSP request

  2. The RMS panel members review and provide a thumbs up (approved) or thumbs down (not approved) on the request in the #release#folio-release_bug_triage channel. For approval a request must receive at least 5 approvals (thumbs up) including at least 2 approvals from technical approvers. If approval cannot be agreed immediately in the channel, then the Requestor PO will be invited to present the request at a RMS group meeting.

    • If the request is approved, the Requestor must set the field “CSP Approved” = Yes

    • If the request is not approved, the Requestor must set the field “CSP Approved” = No and populate the field “CSP Rejection Details”

  3. Proceed to implementation, testing and module release

  4. When the fix has been certified in Bugfest environment, the Requestor PO should change the Jira Status to Closed

  5. Add information about the CSP to the particular release’s Release Notes page on the Wiki in the Post-release CSP table

  6. DevOps team to add tag to platform-complete branch for the particular release

  7. Release Coordinator announces CSP availability using the regular Slack channels

...

  1. The PO works with their team to investigate the issue. The team determines fix strategy, effort, risk, and a test plan

  2. PO prepares the Jira ticket (see Process Logistics and Required information for a CSP request). When the ticket is populated, the PO sends a message to #release#folio-release_bug_triage channel, tagging in @folio_rms which will alert all members of the RMS group of the request. The RMS group members will review the provided material. If the case is compelling enough, they issue their approval right away. If the case is so not clear-cut, the Release Coordinator schedules a meeting for the Requestor PO with the RMS group members. 

    1. Approvers: D Howell (Support rep), K Martin (PC rep), Y Kumar (QA), L Braginski (Dev), J Skoczen, M Veksler, M Gorrell (CC rep), H Kaplanian, K Gambrell. Need 5 approvals, including 2 technical approvers (Mark V, Lee, Mike G, Jakub)

  3. If the RMS decision is a Go, the appropriate development team is tasked to go ahead with the fix.

    • If the decision is a No Go, then PO will make sure to add a workaround to the JIRA issue and additional details to release notes (see Process Logistics)

    • In the case of a Go decision, the CSP is released as soon as the work completed

...