wpp/weirsoe-party-protocol
8
0
Fork 0
Code Issues 19 Pull Requests Actions Packages Projects Releases Wiki Activity

[READY][SPA][P11] Cutover hardening: static asset versioning + rollback playbook for USE_SPA_UI #188

New Issue
Closed
opened 2026-03-01 16:25:59 +01:00 by architecture-bot · 0 comments
architecture-bot commented 2026-03-01 16:25:59 +01:00
Owner
Copy Link

Problem
Cutover-sporet har feature-flag-opgave (#162/#184), men mangler en lille, isoleret hardening-opgave for asset-versionering og hurtig rollback-procedure. Uden dette er release-risiko højere ved cache/proxy edge cases.

Værdi
Sikrere gradvis cutover til SPA med hurtig rollback og færre cache-relaterede incidents i staging/prod.

Hvorfor nu
Skal ligge klar inden endelig cutover-beslutning, så devops/test kan validere release-train uden ad hoc driftstiltag.

Acceptance

  • Dokumenteret strategi for cache-busting/versionering af SPA assets i Django staticfiles/reverse proxy setup.
  • Konfigurerbar rollback-procedure for USE_SPA_UI (trin-for-trin, max 10 min target).
  • Smoke-artefakt beskriver hvordan både SPA on/off verificeres i samme release-vindue.
  • Ingen ændring af gameplay-funktionalitet.

Afgrænsning

  • Ingen ny infrastruktur-provisionering.
  • Ingen ændring af backend API-kontrakter.
  • Ingen UX-ændringer; kun cutover/drift-hardening.
Problem Cutover-sporet har feature-flag-opgave (#162/#184), men mangler en lille, isoleret hardening-opgave for asset-versionering og hurtig rollback-procedure. Uden dette er release-risiko højere ved cache/proxy edge cases. Værdi Sikrere gradvis cutover til SPA med hurtig rollback og færre cache-relaterede incidents i staging/prod. Hvorfor nu Skal ligge klar inden endelig cutover-beslutning, så devops/test kan validere release-train uden ad hoc driftstiltag. Acceptance - Dokumenteret strategi for cache-busting/versionering af SPA assets i Django staticfiles/reverse proxy setup. - Konfigurerbar rollback-procedure for USE_SPA_UI (trin-for-trin, max 10 min target). - Smoke-artefakt beskriver hvordan både SPA on/off verificeres i samme release-vindue. - Ingen ændring af gameplay-funktionalitet. Afgrænsning - Ingen ny infrastruktur-provisionering. - Ingen ændring af backend API-kontrakter. - Ingen UX-ændringer; kun cutover/drift-hardening.
architecture-bot added the bot-tasknice-to-havearchitectrelease-approved labels 2026-03-01 16:25:59 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
PO vil have det her prioriteret
PO-prioriteret
 architect
Architect-owned coordination thread
 backend
Backend
 bot-task
Task managed by scheduler bots
 devops
DevOps/deploy related
 epic
Long-lived scope/phase tracking
 frontend
Frontend
 i18n
Internationalization
 mvp
auto by architect runner
 need-to-have
Required before merge/release
 needs-approval
Requires PO approval before execution
 nice-to-have
Improvement not blocking MVP
 release-approved
Architect approved release scope
 resolved
Løst og merged
 scope-guardrail
Scope and acceptance criteria source-of-truth
 smoke-fail
Smoke test failure
 spa
auto by architect runner
 staging
Staging infrastructure/deploy
 stale
Ingen aktivitet / forældet ift. main
 ui
Frontend/UI related
No Label architect bot-task nice-to-have release-approved
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
architecture-bot dev-bot email-manager integrator-bot manager-bot reviewer-bot scheduler-bot tester-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wpp/weirsoe-party-protocol#188
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?