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

Release-often lane: split SPA MVP into 3 merge-klare micro-PR batches #251

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

Problem: Manglende konkret sekvens giver risiko for store PRs og langsom trunk-fremdrift.

Værdi: Små uafhængige PR-bidder øger mergefrekvens og reducerer integrationsrisiko.

Hvorfor nu: MVP-fase kræver release often / trunk-fokus.

Scope:

  • Definér 3 micro-batches med tydelig rækkefølge: (A) shell/router, (B) session+i18n wiring, (C) lobby/join/start minimal flow.
  • For hvert batch: Done-kriterier, testkrav, og rollback-note.
  • Angiv hvilke batches der kan køres parallelt uden konflikt.

Acceptance:

  1. Sekvensen kan eksekveres uden blokering mellem batches.
  2. Hver batch kan merges/releaseres selvstændigt.
  3. Planen linker til konkrete dev-opgaver.
Problem: Manglende konkret sekvens giver risiko for store PRs og langsom trunk-fremdrift. Værdi: Små uafhængige PR-bidder øger mergefrekvens og reducerer integrationsrisiko. Hvorfor nu: MVP-fase kræver release often / trunk-fokus. Scope: - Definér 3 micro-batches med tydelig rækkefølge: (A) shell/router, (B) session+i18n wiring, (C) lobby/join/start minimal flow. - For hvert batch: Done-kriterier, testkrav, og rollback-note. - Angiv hvilke batches der kan køres parallelt uden konflikt. Acceptance: 1) Sekvensen kan eksekveres uden blokering mellem batches. 2) Hver batch kan merges/releaseres selvstændigt. 3) Planen linker til konkrete dev-opgaver.
architecture-bot added the bot-taskneed-to-havemvpspa labels 2026-03-02 02:25:51 +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 bot-task mvp need-to-have spa
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#251
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?