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

Abierto
  • ¿Algo no está bien?
#43 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
15/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
rust
Área
release

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
11
Forks
1
Merge medio
9 h 48 min
PR fusionados (30 d)
13

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de aliasfoxkde/FireCraft

Todos los issues de aliasfoxkde/FireCraft

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.