Update Git Branching Strategy

[johndeange]

Problem

We had initially created a git branching strategy:

https://github.com/HHS/OPRE-OPS/blob/main/docs/git-branching.md

This document is no longer accurate.

Facilitate a discussion with the OPS devs to decide on a new branching strategy (and possibly release process) and document it.

Acceptance Criteria

• Meeting with the devs about the issue.
• Update the documentation with the result.

---

Tasks

UX

Dev

• SPIKE: Setup deploying feature branch to slot in staging environment #2812
• SPIKE: Setup continuous deployment to standby slot in PROD #2815
• Setup staging environment for continuous deployment #2811
• Update branching/release strategy documentation markdown #2809
• ADR for branching/release strategy #2810
• Update/Add script in data-tools container to handle not dropping data but to update schema #2861
• Slack notifications for failed deployments for all environments #2819
• SPIKE: Look into running E2E tests in lower environment #2822
• DB comparison test to detect bad migrations #2821
• Write a script to roll back DB #2824
• PROD release manual/how to #2823
• Break fix FAQ #2820
• Document how we will implement semantic commits #2818
• Document how we will implement semantic versioning #2817
• Document how we will implement semantic releasing #2814

Definition of Done Checklist

• UI works as designed (UX team)
• Usability validated (UX team)
• PR(s) have been merged to main
• Design/tech debt eliminated
• New design/tech debt documented (if applicable)
• Build process updated
• Documentation updated or added
• Feature flags/toggles created

Additional Context & Resources

https://github.com/HHS/OPRE-OPS/blob/main/docs/git-branching.md

Collaborative Design Doc:

https://lucid.app/lucidchart/e7019a69-a2e8-4320-992c-d87ad1d9a0ea/edit?invitationId=inv_361201e2-13cd-4897-afbe-47b1e7c4505f&page=X~L~vrLwUtob#