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

オープン
#44 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
ドキュメント
明瞭さ
おおむね明確
活発さ
活発
技術スタック
rust
領域
documentation

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Rust
スター
11
フォーク
1
平均マージ
9時間 48分
マージ済み PR(30日)
13

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

aliasfoxkde/FireCraft のほかの issue

aliasfoxkde/FireCraft の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。