v0.6.0 pre-tag readiness — test plan, approved-idle PRs, and owed decisions
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 18/100
調査の方向性
Start by reading the release lane's gate and RELEASE-NOTES, then run verify_publication.sh and the specified pytest --tip TIP-01 --tip TIP-02 conformance command. The issue also calls for hardware acceptance, upgrade and rollback checks, owner decisions, and triage across many linked issues and PRs. Done means the required release checks and decisions are completed and the rc1 scope is resolved.
索引モデルが issue の本文から書いたものです。
説明
v0.6.0 pre-tag readiness — test plan, improvements, and owed feedback
Consolidated from the full open-issue/PR sweep (2026-10-08). Baseline: final-main Go battery 16/16 modules green (release lane), train merged, rc1 not yet tagged.
Owner decisions owed before the tag
- #648 freeze contradiction — changelog entry sits under
[v0.6.0-rc1]while the release lane holds the PR out of the RC. In → lane re-verifies the RC gate with it; out → move the entry to[Unreleased]. - #619 — last note says "deferred past rc1, maintainer decision needed". Confirm the deferral so the review queue reflects it.
- #629 / #630 — feature PRs (cold-start reseller bootstrap; hostmode ndsctl shim + nftables). Neither is rc1-scoped by the freeze logic; both need explicit park-to-next-cycle calls.
- #631 nit before merge — its changelog entry carries a "(PR pending — link filled in when upstream PR opens)" placeholder.
Approved-and-idle — merging these strengthens the RC
- #618 (dual-brand SSID discovery) and #620 (vendor-IE overflow policy): both APPROVED with hardware A/B GREEN. Re-verify against current main if the base moved, then merge.
- #643 + #647 (gonuts v0.13.0: NUT-20 signature fix + ambiguous-outcome POSTs — money-safety), #645 (apk3 resolution gate — would have caught #552), #646 (build-sdk fix), #644, #621, #626, #632 — merge-ready per orchestrator reviews posted today.
Test plan before release
RC acceptance (per the release lane's own gate):
- Hardware acceptance on the bench (x1860/MT3000) per RELEASE-NOTES.
- Upgrade 0.5.x → 0.6.0-rc1 AND rollback, both package lanes (opkg + apk). Note: fork issue #93 (preinst bare-jq
exit 1blocks upgrades) hits this exact path — fix or explicitly accept before the pass. - Clean publish gate:
verify_publication.sh; note fork #96 (release assets carry no sha256 digests) pairs with it.
Conformance, reproducibly: pytest --tip TIP-01 --tip TIP-02 on PRTA main — the story/TIP selection machinery (PRTA#20) turns the "green conformance re-run" into a defined command.
Live battery: the commissioned read-only API run (PRTA#12) when the bench link is back.
Issue-driven regression tests worth adding before the tag:
- #582 (first payment refused for present-but-unregistered client) — repro; fix-or-known-issue call. Pairs with #618's r2r work.
- #628 (discovery endpoint serves
text/plainon/) — r2r client compat; one-line class. - Fork cluster #97/#99/#100/#101 (nftables guards, NDS allowlist, firewall zones — the portal/backend-reachability class): bench-verify against the rc1 image; the live
:2121hang (2026-10-05) corroborates the class is real, and #98's stop_service sweep (merged) + a stray-holder regression rail (PRTA gap register O3) prove the fix. - PRTA#10 (degraded mode never recovers when the mint returns) — deploy-facing; the story-matrix G7/O2 rails exist to host the repro.
Improvements addressable now
- PRTA #2 (installer suite + nostr publisher): answer the opt-in-gating question and merge — it's the evidence-film pipeline the acceptance runs want to use.
- PRTA #19 (replace-mints guard): merge (triage-deferred, not release-gating, but it's green).
- Fork #103 triage is stale (the train moved past it) — refresh with the current disposition.
- omarchy-cashu #62/#63: the autopay decision + ready PR — separate product, but it's the last open decision lane there.
Explicitly NOT pre-release scope
#503 (Go leg of the conformance matrix — new infra), #504/#505 (P2 audits), upstream TIP-02 min_steps resolution (OpenTollGate/tollgate#20), #550/#521 CI proposals.
- 主要言語
- Go
- スター
- 12
- フォーク
- 14
- 平均マージ
- 3日 22時間
- マージ済み PR（30日）
- 262
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
OpenTollGate/tollgate-module-basic-go のほかの issue
-
難易度 1/5 1時間未満 初心者へのやさしさ 85/100
OpenTollGate/tollgate-module-basic-go#1159 ·
メンテナーはふだん 1 日以内に返信
-
Degraded-mode hygiene follow-ups: dead walletNotInitializedError() + main.go's startup log still over-promises mint recovery対応中かも @Amperstrand が 4 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
OpenTollGate/tollgate-module-basic-go#1135 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
setup_uhttpd_portal hardcodes the GUEST portal docroot to the TollGate path — the brand token cannot select a re-brand guest portal対応中かも @Amperstrand が 4 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
OpenTollGate/tollgate-module-basic-go#1122 ·
メンテナーはふだん 1 日以内に返信
-
changelog: dependency-security sweep missing from [Unreleased] [Amperstrand fork #105 review debt]オープン
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
OpenTollGate/tollgate-module-basic-go#1055 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
OpenTollGate/tollgate-module-basic-go#1027 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
OpenTollGate/tollgate-module-basic-go の issue をすべて見る
似ている issue
-
Cluster details: the Control Plane version field has a different border color than its icon boxオープンkind/design sig/ui
難易度 1/5 1時間未満 初心者へのやさしさ 92/100
kubermatic/dashboard#8449 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
filecoin-project/curio#1632 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
-
compose: derived node options overwrite each other's targets対応中かも @yangjj-iso が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信