T27-09 — Obtain the maintainer's approval of the MVP v1 scope

Aperta
  • Qualcosa non va?
#43 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
15/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
release

Direzione di ricerca

Read docs/RELEASE-ENGINEERING-PLAN.md §1.1 and docs/release/EXECUTION-BOARD.md §3 to understand the proposed MVP scope, then check docs/decisions for an approval record. Completion requires a maintainer decision naming the approved scope, date, and approver, plus an updated board section citing that record and marked approved. The issue says this external decision is required and blocks three dependent tasks.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

release

T27 row: T27-09
Work package: RP-00 — Inventory, release contract, baseline, task ledger
Priority: P0
Status: BLOCKED

Objective

Obtain a written maintainer decision naming the approved release scope. Until this exists, no scope is approved and no row may claim an approved matrix.

Acceptance criteria: A decision record names the approved MVP scope, the date, and the approver; the board's §3 scope split is updated to point at that record and is marked approved rather than recommended.

Inputs

The MVP candidate list in docs/RELEASE-ENGINEERING-PLAN.md §1.1 and in docs/release/EXECUTION-BOARD.md §3; the campaign's MVP list.

Authority

Campaign §5 P1.3 — "Record the maintainer's approved scope. Do not treat a recommendation as approval." docs/RELEASE-ENGINEERING-PLAN.md §1.1 — "a recommended scope cut for maintainer approval, not an automatic change".

Stopping condition

A decision record exists and the board cites it. Until then T27-10, T27-60 and T27-61 remain blocked on this row.

Verification

grep -n 'Approved by' docs/decisions/00XX-*.md

Evidence and blockers

The MVP candidate list is written down (docs/RELEASE-ENGINEERING-PLAN.md §1.1 and the campaign's P1.3 list), and the campaign record states plainly: "Record the maintainer's approved scope. Do not treat a recommendation as approval."

No approval record exists on main: git grep -l 'Approved by' origin/main -- docs/decisions returns nothing, and docs/decisions/0075-release-scope-mvp.md is not on main (it lives on the unmerged feat/release-workflow-repair base of PR #19). The execution board's §3 therefore still records the MVP as a recommendation.

Blocker (external): a maintainer decision. Nothing in the repository can substitute for it — this row stays open until a decision record naming the approved scope, the date and the approver is committed.

Ledger: docs/tasks/T27-09-mvp-scope-approval.md and docs/release/EXECUTION-BOARD.md row T27-09 (these land with PR #12).
Campaign: docs/planning/release-compaign/Cross-Platform Releas.txt.

Lingua principale
Rust
Stelle
11
Fork
1
Merge medio
9h 48m
PR unite (30g)
13

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di aliasfoxkde/FireCraft

Tutte le issue di aliasfoxkde/FireCraft

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.