Skip to content

FLX-ENG-RFC-002-US-1.4 - Branching and Release Discipline Sync

Field Value
Parent RFC FLX-ENG-RFC-002
GitHub Issue #12 - US-1.4
Owner Arun Singh
Priority P1
Status Ready for execution
Target window Day 1 or Day 2

Goal

Capture current branching, release, tagging, and rollback practice from Rahul, Tushar, and Shrikant so EPIC-1 recommendations fit how Flexli actually ships.

Agenda

  1. Current branches: main, dev, prod, feature branches, hotfix branches.
  2. Merge path: feature to dev, feature to main, or direct merge.
  3. Release trigger: PR merge, tag, manual server pull, CI/CD workflow.
  4. Rollback method: revert PR, redeploy previous image, database rollback.
  5. Excluded PRs for DORA: bot, docs-only, draft, sync-only, generated code.
  6. Pain points: slow reviews, broken tests, deployment uncertainty, manual steps.

Approaches Considered

Approach Pros Cons
15-minute focused sync Fast, enough for Week 1 May miss edge cases
Async questionnaire Easy to schedule Low response quality
Full process workshop Rich detail Too expensive for EPIC-1

Verdict

Run the short sync, then share concise notes async for correction.

Implementation Steps

  1. Schedule with Rahul, Tushar, and Shrikant.
  2. Share agenda before the call.
  3. Capture answers in the Week 1 scan report.
  4. Extract CodePulse filter rules for US-1.7.
  5. Extract release/rollback assumptions for RFC-001 and RFC-009 alignment.
  6. Post notes to the issue or PR for confirmation.

Test Cases

The notes pass review when they answer:

  • Which branch counts as production deployment?
  • What is a failed deployment signal?
  • Which PRs should be excluded from metrics?
  • Who approves release changes?
  • What is the stop rule for rollback?

Gating

  • Do not configure CodePulse deployment rules until the production branch signal is confirmed.
  • Do not treat sync-agent PRs as normal delivery PRs unless Rahul confirms.
  • Do not assert release discipline as fact until the SMEs review the notes.

Definition of Completion

  • Sync held or async notes accepted.
  • At least three pain points captured.
  • CodePulse filters are ready for US-1.7.
  • Any disagreement is captured as a decision gap issue.

Reviewer Reply Template

Thanks, I captured this from the release sync and kept the wording factual until the SMEs confirm it.