From 362988e78d0360c956329f55a18e4bbb620e2b38 Mon Sep 17 00:00:00 2001 From: Pavel Tisnovsky Date: Thu, 18 Jun 2026 09:24:52 +0200 Subject: [PATCH] LCORE-1649: LTS flow --- docs/lts_flow.svg | 153 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 153 insertions(+) create mode 100644 docs/lts_flow.svg diff --git a/docs/lts_flow.svg b/docs/lts_flow.svg new file mode 100644 index 000000000..4bc79c918 --- /dev/null +++ b/docs/lts_flow.svg @@ -0,0 +1,153 @@ + + + + + + + + + + + + + LTS Process Flow — Request intake → Triage → Patch dev → Release → Communication + + + + + + Requesting / Ticketing + Engineering / QA + Release / Communications / Ops + + + + + Intake + Owner: Requester / Intake Module + Output: standardized ticket (metadata) + + + + + + + + + Triage + Owner: Triage Engineer + Decide: severity, SLA, affected versions + Output: triage decision, risk score + + + + + + + + + Planning and Approval + Owner: Maintainer / Leads + Output: backport plan, approvers, branches + Policy: security flag, emergency fast-track + + + + + + + + + + Development + Owner: Developer / Code Reviewer + Branch: lts/vX.Y/issue-# + Output: patch branch, CI runs + + + + + + + + + Testing and Validation + Owner: QA (+Security if needed) + Tests: unit, integration, regression, upgrade + Output: signed-off PR, test reports + + + + + + + + + Release Staging + Owner: Release Manager / CI Owner + Output: artifacts, checksums, RC + Includes: SBOM, smoke tests, signing + + + + + + + + + Release and Deployment + Owner: Release Manager / Ops + Channels: PyPI/container/OS packages + Controls: staged rollout, rollback plan + + + + + + + + + Communication and Docs + Owner: Communications Lead + Maintainer + Outputs: release notes, upgrade guidance + Channels: mailing lists, status page + + + + + + + + + Post-release and Metrics + Owner: SRE / Engineering Leadership + Outputs: verification report, postmortem + Metrics: time-to-triage, rollback rate + + + + + Optional: back-merge fix to main + + + + Legend and Quick Rules + • Branch naming: lts/vX.Y/issue-# + • Policy: patch-only for LTS (no breaking changes) unless emergency-approved + • Must log approvals and timestamps on ticket + • Security-sensitive items require Security sign-off before release + • CI gates: lint, unit, integration, regression, security scan, artifact signing + • SLA examples: triage within 24h (critical 4h); plan within 3 business days + + + Use this diagram as a printable quick-reference — add links to runbooks, ticket templates, and CI pipelines in your docs. +