T27-09 — Obtain the maintainer's approval of the MVP v1 scope
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- Rust
- 星标
- 11
- 派生
- 1
- 平均合并
- 9 小时 48 分钟
- 30 天内合并 PR
- 13
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
aliasfoxkde/FireCraft 的其他 Issue
-
documentation release
难度 2/5 1-3 小时 新手友好度 68/100
aliasfoxkde/FireCraft#58 ·
维护者通常 1 天内回复
-
release
难度 4/5 3-5 天 新手友好度 54/100
aliasfoxkde/FireCraft#81 ·
维护者通常 1 天内回复
-
documentation
难度 5/5 一周以上 新手友好度 35/100
aliasfoxkde/FireCraft#80 ·
维护者通常 1 天内回复
-
enhancement parity
难度 4/5 3-5 天 新手友好度 48/100
aliasfoxkde/FireCraft#79 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 38/100
aliasfoxkde/FireCraft#78 ·
维护者通常 1 天内回复
查看 aliasfoxkde/FireCraft 的全部 Issue
相似的 Issue
-
难度 1/5 1 小时以内 新手友好度 94/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 2 天内回复
-
enhancement good first issue help wanted
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
area:ui
难度 2/5 1-3 小时 新手友好度 78/100
openfootmanager/openfootmanager#1365 ·
维护者通常 1 天内回复
-
documentation
难度 1/5 1-3 小时 新手友好度 90/100
JackMechem/marbble#305 ·
维护者通常 1 天内回复