Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
18 commits
Select commit Hold shift + click to select a range
080b4d6
quest: re-cut milestones by kind of change and priority (checkpoint)
kixelated Nov 5, 2026
11d6705
quest: point recurring cut, review, gate, and audit text at the new m…
kixelated Nov 5, 2026
976d68b
chore: follow moved quest paths outside the quest tree
kixelated Nov 5, 2026
5058462
quest: update prose that names a milestone in the present tense
kixelated Nov 5, 2026
54753ec
Merge remote-tracking branch 'origin/main' into quest-plan/milestone-…
kixelated Nov 5, 2026
f4790d3
quest: keep other repositories' quest links unchanged by the re-cut
kixelated Nov 5, 2026
1c00d1c
Merge remote-tracking branch 'origin/main' into quest-plan/milestone-…
kixelated Nov 5, 2026
c18d660
quest: settle pullfrog's findings on the re-cut
kixelated Nov 5, 2026
78dcb4c
Merge remote-tracking branch 'origin/main' into quest-plan/milestone-…
kixelated Nov 5, 2026
d3640c2
quest: follow announce-takeover's move in the route wire decisions
kixelated Nov 5, 2026
861bbc3
Merge remote-tracking branch 'origin/main' into quest-plan/milestone-…
kixelated Nov 5, 2026
2c020ef
quest: annotate release-nix-cache's placement with its post-re-cut mi…
kixelated Nov 5, 2026
8da4cdd
Merge remote-tracking branch 'origin/main' into quest-plan/milestone-…
kixelated Nov 5, 2026
b287504
Merge remote-tracking branch 'origin/main' into quest-plan/milestone-…
kixelated Nov 5, 2026
46e1dff
Merge base and preserve audited quests across milestone moves
Nov 5, 2026
3185701
Merge remote-tracking branch 'origin/main' into HEAD
kixelated Nov 6, 2026
479cc1b
Merge origin/main into quest-plan/milestone-recut
kixelated Nov 6, 2026
94bde86
Merge remote-tracking branch 'origin/main' into HEAD
kixelated Nov 6, 2026
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
2 changes: 1 addition & 1 deletion bench/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -203,7 +203,7 @@ also run during timing. Every timed round reads and checks all payload bytes,
returns lease credit, and fills each stream again. Throughput counts delivered
payload once. Nightly's supplemental Rust benchmark leg records the series and
keeps the memory output with its raw results. The broader MoQ session transport
and version sweep remains in [its quest](/quest/m2/bench-transport-sweep.md).
and version sweep remains in [its quest](/quest/m4/bench-transport-sweep.md).

Compare one multi-threaded Tokio runtime with the same number of independent
Tokio/epoll and io\_uring workers:
Expand Down
2 changes: 1 addition & 1 deletion doc/concept/socket.md
Original file line number Diff line number Diff line change
Expand Up @@ -137,7 +137,7 @@ every hop, so a slow reader slows the writer, as TCP backpressure does, and
nothing is lost. A writer that doesn't wait sheds the front of its half, and a
reader that falls behind it fails with an eviction error instead of skipping
data. Pacing reaches across native QUIC and qmux hops; see
[unbounded groups](https://github.com/moq-dev/moq/tree/main/quest/m1/unbounded-groups)
[unbounded groups](https://github.com/moq-dev/moq/tree/main/quest/m2/unbounded-groups)
for what remains, such as browsers, which read without pacing.

Use `tcp` for a byte stream or a log of records that must all arrive in order,
Expand Down
2 changes: 1 addition & 1 deletion infra/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ which can update an existing worker but not create one or change its route.
So the first deploy, and any change to the custom domain, runs by hand under a
maintainer's `wrangler login`. Whether Editor alone passes wrangler's
custom-domain check on every deploy is unproven until the first `release`
run; [the deploy quest](../quest/m2/release/moq-sh-deploy.md) tracks it.
run; [the deploy quest](../quest/m3/release/moq-sh-deploy.md) tracks it.

## Write credentials

Expand Down
63 changes: 42 additions & 21 deletions quest/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,23 +7,42 @@ grouped into milestones ordered by priority.

## Plan

m0 holds urgent fixes and release-line maintenance. m1 is everything that
lands before the next cut of `main` into `release`, breaking or not:
clustering stability first, the in-tree QUIC stack, and planned public API and
format breaks with their correctness and validation.
m2 holds independently shippable capabilities and optimizations, plus the
publication and adoption steps that follow m1. m3 holds external conditions
and speculative work. A milestone is a priority horizon; m0 maintenance does
not make unrelated infrastructure a gate for the main-to-release cut.

Milestones shift up after each major release (decided 2026-10-19): m0 is the
current release line, m1 the next major, m2 the one after, and m3 stays the
deferred bucket. The [release cut](/quest/m2/release/cut.md) recurs and
performs the shift. The hygiene audits at the end of each milestone recur
once per major release: each run adds its successor to the end of the next
milestone.

The [release execution](/quest/m2/release/README.md) starts after m1 is ready.
m0 holds urgent work of any type: release-line maintenance, broken CI and
Nightly, and any fix that cannot wait for its milestone, breaking or not.
m1 holds this cycle's additive work: improvements and fixes that need no
semver-breaking release, so each ships with the next cut or as a `release`
patch when backported. m2 is the next breaking release: every change that
would need one if it landed right after the cut, plus the
[cut gate](/quest/m2/cut-gate/README.md). The cut waits on m2 alone. m3 and m4
are later work split by priority: m3 holds what a named consumer waits on,
release execution, and bug fixes in shipped code; m4 holds tests, tooling,
benchmarks, optimizations, and features nobody waits on yet. m5 holds work
gated on the outside world, or speculative work with no named consumer.

A change is breaking when a published consumer or a deployed peer must adapt
to it: the public Rust, JS, or bindings API, a frozen wire version, the hang
catalog JSON, a stored or exported container format, or CLI flags, config
keys, and environment variables. The test is whether it would need a breaking
release if it landed right after the cut, so a change to lite-07-wip or to a
`main`-only API the cut would publish counts. A non-urgent fix that breaks
joins m2; when a non-breaking fix exists, the fix joins m1 and the break m2.
An epic joins the milestone its outcome needs, children included.

Decided 2026-11-05 (maintainer, milestone re-cut): milestones split by kind of
change for the current cycle and by priority after it. This replaces m1 as
"everything before the cut, breaking or not" (2026-10-20). Grouping by kind
could bury urgent breaking work behind additive work, so urgency still wins:
urgent work of either kind joins m0.

Milestones shift after each cut (decided 2026-10-19, rule replaced
2026-11-05). The [release cut](/quest/m3/release/cut.md) recurs and performs
the shift: remaining release-execution quests move to m0, m3's quests split
by kind into m1 and m2, m4's move to m3, m4 starts empty, and m5 stays the
deferred bucket. The cut PR also re-creates the cut gate in m2. The hygiene
audits recur once per major release in m3, behind the cut, so the shift
brings each into m1.

The [release execution](/quest/m3/release/README.md) starts once m2 is done.
It publishes artifacts before downstream adoption and rollout can complete.
Critical fixes continue to reach the existing release through backports.

Expand All @@ -35,7 +54,9 @@ planning PR's review is the check.

## Required

- [m0: immediate priorities](/quest/m0/README.md) - urgent correctness fixes and maintenance of the current release
- [m1: next wave](/quest/m1/README.md) - everything before the next release cut, breaking or not, with its required correctness and validation
- [m2: later work](/quest/m2/README.md) - byte streams and mesh libraries first, then release execution, deferred features, optimization, and design studies
- [m3: deferred](/quest/m3/README.md) - gated on the outside world (hardware, a partner, a consumer, a provider's offer, or an upstream release), or speculative with no named consumer
- [m0: immediate priorities](/quest/m0/README.md) - urgent work of any kind, and maintenance of the current release
- [m1: additive work](/quest/m1/README.md) - this cycle's improvements and fixes that need no breaking release; each ships with the next cut or as a backported patch
- [m2: the next breaking release](/quest/m2/README.md) - every change that would need a breaking release if it landed after the cut, plus the cut gate; the cut waits on m2 alone
- [m3: later work, higher priority](/quest/m3/README.md) - byte streams and mesh libraries first, release execution, what a named consumer needs, and bug fixes in shipped code
- [m4: later work, lower priority](/quest/m4/README.md) - tests, tooling, benchmarks, optimizations, and features nobody waits on yet
- [m5: deferred](/quest/m5/README.md) - gated on the outside world (hardware, a partner, a consumer, a provider's offer, or an upstream release), or speculative with no named consumer
2 changes: 1 addition & 1 deletion quest/m0/ci/mbx-r2-verify.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ nightly.yml --branch main --event schedule`), never a dispatch on a branch.
## Plan

Decided 2026-11-05 (maintainer, /quest-audit): ✅ the release pull request
check moved to [m2](/quest/m2/mbx-r2-release-cache.md) behind the cut, since
check moved to [m3](/quest/m3/mbx-r2-release-cache.md) (m2 before the milestone re-cut) behind the cut, since
`release` gets the platform Rust cache only when the cut merges `main` into
it; the Nightly checks stay here. Not chosen: moving this whole quest; merging
`main` into `release` now, which reverses the 2026-11-04 decision.
Expand Down
4 changes: 2 additions & 2 deletions quest/m0/ffi-shutdown-backport.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ patch cut on `release`, which the maintainer cuts.
Dart: pub.dev publishes `moq` only from a `moq-dart-v*` tag, and only
`moq-dart-v0.1.0` exists. Pushing `moq-dart-v0.1.1` at `release`'s head
publishes 0.1.1 and exercises the unproven path in
[A Dart tag publishes unattended](/quest/m2/release/dart-publish.md). Decided
[A Dart tag publishes unattended](/quest/m3/release/dart-publish.md). Decided
2026-10-30 (maintainer): push it during the combined cut, not before.

Decided 2026-11-04 (maintainer, /quest-unblock): ✅ cut the combined patch
Expand All @@ -43,4 +43,4 @@ Public API: none. Wire: none.

## Related

- [A Dart tag publishes unattended](/quest/m2/release/dart-publish.md) - proves the `moq-dart-v*` tag path this publish uses
- [A Dart tag publishes unattended](/quest/m3/release/dart-publish.md) - proves the `moq-dart-v*` tag path this publish uses
Loading
Loading