Skip to content

v1.6 Release Roadmap — sequencing, waves & critical path (provisional) #392

Description

@VijitSingh97

Single source of truth for the v1.6 release plan — same format as #364. Provisional: small milestone, far out; re-sequence when the cycle opens. Spec-gap assessments from the 2026-07 audit sit on every issue.

The theme: v1.6 loosens where the stack can live. Everything to date assumes the appliance model — one dedicated host, Caddy owning :443, the default subnet. v1.6 makes the documented opt-outs real: co-hosting next to other services (#181), a remote Tari node like Monero's remote mode (#103), and proof the stack actually works off the default subnet (#201).

   #181  co-hosting umbrella ── split into: disable-Caddy mode / alternative-ports
         (Wave 0: split the issue; define the auth-when-Caddy-is-bypassed fail-closed rule)
   #103  remote Tari base node ── Wave 0: feasibility SPIKE first
         (remote --merge-mine over gRPC: templates/submission/latency/auth → go/no-go;
          must define how the #314 socat Tor bridge behaves in remote mode)
   #201  e2e: non-default network.subnet in the live matrix
         (independent; extend to cover post-#346 proxy_net + the #344 onion vhost binding)

Wave 0 — Splits & spikes

The work

Release status — cycle not open

Gates when it opens: #181 split merged · #103 spike verdict recorded · gouda pass including one co-hosted-profile scenario · CHANGELOG · standard cut process.

Metadata

Metadata

Assignees

No one assigned

    Labels

    infraDeployment, packaging, releases

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions