T27-10 — Reconcile the release documentation against one scope authority

Aperta
  • Qualcosa non va?
#44 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
35/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
documentation

Direzione di ricerca

Read docs/release/PHASE-0-AUDIT.md and docs/RELEASE-ENGINEERING-PLAN.md §§1.1 and 3 first, then compare the listed release documents with docs/release/ARTIFACT-MATRIX.md and the decision records. Resolve the scope conflict from a written maintainer decision, or record it as a blocker with an owner. Done means the release documents cite one scope authority and contain no CI, artifact, or platform claims that conflict with the matrix.

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

Descrizione

documentation release

T27 row: T27-10
Work package: RP-00 — Inventory, release contract, baseline, task ledger
Priority: P1
Status: NOT STARTED

Objective

Make T27, docs/TASKS.md, docs/RELEASING.md, docs/TOOLCHAINS.md and the artifact matrix cite the same scope authority and contain no stale CI or status claims.

Acceptance criteria: Every release document cites one scope authority; no document claims a CI state, artifact state or platform support that the matrix does not record; the §3-versus-§1.1 conflict is resolved in favour of the maintainer's decision.

Inputs

docs/tasks/T27-cross-platform-release.md; docs/TASKS.md; docs/RELEASING.md; docs/TOOLCHAINS.md; docs/release/ARTIFACT-MATRIX.md; docs/decisions/.

Authority

docs/RELEASE-ENGINEERING-PLAN.md §1.1 and §3 (the target matrix and the MVP candidate currently disagree — §3 lists Windows/macOS/Android as required while §1.1 proposes a reduced first cut).

Stopping condition

The documents agree, or the disagreement is recorded as an explicit blocker with an owner.

Verification

grep -rn '0\.2\.5' docs/RELEASING.md docs/TOOLCHAINS.md docs/tasks/T27-cross-platform-release.md

Evidence and blockers

The Phase-0 baseline audit (docs/release/PHASE-0-AUDIT.md, merged on main as part of PR #16) established the ground truth and enumerated the stale claims, but the release documents themselves have not been reconciled: every item in the campaign's P1.4 list (T27, docs/TASKS.md, docs/RELEASING.md, docs/TOOLCHAINS.md, docs/release/ARTIFACT-MATRIX.md, tag/main baseline discrepancies, stale CI status claims) is still unchecked.

PR #19 ("reconcile release ledgers with the Phase 0 baseline audit") merged into the feat/release-workflow-repair base branch, so its reconciled documents are not on main yet.

Blocker: T27-09 — the §3-versus-§1.1 scope conflict can only be resolved in favour of a written maintainer decision.

Ledger: docs/tasks/T27-10-doc-scope-reconciliation.md and docs/release/EXECUTION-BOARD.md row T27-10 (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.