Skip to main content

Retro Action Item: Release Process Alignment

FOLLOW UP: Paula to report back to QA team, Pod Leads suggestions. Follow up with those who are accountable with action items

The team expressed challenges in having a streamline process for Release Management. To deter this from consistently happening, an implementation has been aligned on next steps. Below are the following conversation topics - notes associate with it, and action items

  1. Release Process Improvement:

Evaluate the need for a multi-tenant development environment. Assign a responsible party for issues raised in CapEx. Implement a process for QA to escalate issues to a designated owner. Establish a timeline for addressing issues in CapEx.

Action Items:

  • Ashish to work with Keith on discussing current state, improvements, and clarifying visions for SRE and development processes.
  • Ashish to Define Development Lifecycle: with defining the development lifecycle for features, including what environments are used for testing and QA handoff.
  • This process needs to be documented and made highly visible to all teams.
  1. Environment Management:

Create a separate enterprise within CapEx for QA with two orgs and at least five environments spread across them. Determine if QA will be entirely moved out of Tiberius and Augustus or if initial testing for new features will still occur in the development space.

Action Items:

  • Access and Control: Thomas suggested that QA should have some level of control or ownership within CapEx to facilitate testing without reaching out to IT.
  • Move the QA environment into a new multi-tenant enterprise within CapEx, with a clarified expectation of environments and orgs.
  1. Hotfix Criteria and Process:

Discuss and define what constitutes a hotfix. Establish a process for adding features late in the release cycle.

Action Items:

  1. Accountability:

Assign ownership for the release process, potentially to Ashish. Create a tech debt item for the infra team to address multitenancy in lower environments. Ensure product managers or leads like Thomas, Ashish, and Prashanth are informed and involved in decisions regarding customer promises and feature delivery.

Action Item:

  • whole team - be accountable in filling out details, utilize templates for tickets, and communication.