v0.6.0 pre-tag readiness — test plan, approved-idle PRs, and owed decisions

Abierto
  • ¿Algo no está bien?
#665 20 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, python, shell
Área
release, testing

Línea de trabajo

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.

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

Descripción

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

  1. #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].
  2. #619 — last note says "deferred past rc1, maintainer decision needed". Confirm the deferral so the review queue reflects it.
  3. #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.
  4. #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 1 blocks 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/plain on /) — 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 :2121 hang (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.

Lenguaje dominante
Go
Estrellas
12
Forks
14
Merge medio
3 d 22 h
PR fusionados (30 d)
262

Preparar el entorno

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 OpenTollGate/tollgate-module-basic-go

Todos los issues de OpenTollGate/tollgate-module-basic-go

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.