Skip to content

[OC-064] Run release conformance and 72-hour soak #65

Description

@tcballard

Gate: G5 — Packaging, hardening, and release

Planning source: validated implementation plan PR #1


  • Depends on: OC-057OC-063.
  • Deliverable: signed release-candidate evidence bundle covering clean install, both mobile peers where supported, adapter reset, relay loss, proxy mode, restart, panic, resource metrics, cache convergence, and 72-hour daemon run.
  • Acceptance: zero panics, unbounded growth, secret-bearing logs, or unexplained interop failures; all G0–G5 reports are linked; release notes state exact pins and known deviations.
  • Excludes: merging, tagging, AUR publishing, or announcement without owner approval.

Maintainer reconciliation — 2026-09-04

Next closure evidence/work: Produce signed acceptance evidence and 72-hour soak. Explicitly reconcile old G0–G5 dependencies with release scope; no tagging/publication authorised by this backlog cleanup.

Baseline reviewed: main 87c3bcb7d65e3e2ab8ae317694b751f8efe9a8ed. Implementation presence is not a live conformance claim.

Current release scope — 2026-09-05

Release acceptance must cover the current Nostr/account/TUI product, install/upgrade, relay loss, restart, panic, bounded resources and the 72-hour soak. Closed Bluetooth/mesh/courier gates are deferred scope, not passed gates or current-release prerequisites. Any mobile compatibility or Tor claim still requires its own evidence.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions