Release Process Document

Release Process Document

1. Overview

This document defines the standardized release process for Backend Services & Command Center, ensuring structured deployments, accountability, and traceability.

2. Release Schedule & Frequency

• Planned Releases: Occur twice a week on Tuesday & Thursday from the master branch.
• Hotfixes: Also released directly from master as needed.

3. Deployment Process & Approval

• Commit Verification:
• AWS CodePipeline will generate a change log by comparing the latest commit in master with the last production commit.
• The change log will be reviewed to ensure:
• All commits are either QA/Product signed off or explicitly approved by Pod Leads.
• Any unverified commits must be reverted and then deployed

4. Commit Message Format

All commits from developers must follow this format:

<Jira Ticket ID> : <Jira Ticket Summary>

Example:

JIRA-1234: Fixed issue with transaction rollback in payment service

5. Ownership & Responsibilities

• Engineering Release Owner (Pod Leads):
• Ensures commit approvals, oversees deployment, and manages post-release issue resolution & Monitoring.
• Product Owner:
• Owns pre and post-release communications.
• Acts as the SPOC for Operations, Sales, and Support for release-related queries.