Skip to content
Merged
2 changes: 2 additions & 0 deletions quest/m0/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,8 @@ Each lands its fixes in its own PR and plans only what needs a decision.

- [CI cost and latency](/quest/m0/ci/README.md) - cloud CI runs only in the merge queue as one `just ci` pass, expensive checks run nightly and gate `release`, caches move to R2, and runners are chosen last
- [Release builds link](/quest/m0/release-link.md) - the Linux zigbuild release binaries and moq-gst packages link again after the 2026-10-11 nixpkgs bump, so the next release cut can publish
- [qmux 0.5.3](/quest/m0/qmux-0.5.3.md) - crates.io publishes qmux 0.5.3 with the builder session config the release backport of #5609 needs
- [Release shutdown backport](/quest/m0/ffi-shutdown-backport.md) - `release` publishes a non-breaking moq-ffi with an async `drain()` and qmux sessions on the QUIC stream limit
- [Broadcast epochs](/quest/m0/broadcast-epoch/README.md) - every first-party publisher that can restart mints a fresh route epoch, the newest wins a path, and only routes with the same epoch resume a subscription
- [Performance audit](/quest/m0/audit-perf.md) - benchmarks that regressed since the last run are explained, fixed, or planned, and unbenched hot paths get coverage
- [Compile time audit](/quest/m0/audit-compile-time.md) - build-time hotspots are measured against a baseline and the worst are fixed or planned
Expand Down
58 changes: 58 additions & 0 deletions quest/m0/ffi-shutdown-backport.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
# [S] Backport draining shutdown and the qmux stream limit to release

## Goal

The `release` line publishes a non-breaking moq-ffi 0.4.x (wheel, Swift, and
Kotlin) and moq-tokio whose sessions can drain before closing and whose qmux
sessions accept the QUIC stream limit:
Comment thread
coderabbitai[bot] marked this conversation as resolved.
Resolved

- An async `MoqSession.drain()` drains finished tracks within one second
and returns any delivery error, as `main`'s async `shutdown()` does
(7bbac3272, with 03fb0d1c1, f9de31167, and #5558's explicit Lite 07 test).
Explicit `moq-lite-07-wip` waits for the peer to receive the tail; older
Lite versions, including the default lite-06, and IETF wait only for
transport ACKs. The sync `shutdown()` stays `cancel(0)`.
- qmux sessions get the QUIC stream limit (#5609) instead of the 100-stream
default.

Check: release-plz publishes the release commits, and the newest moq-ffi on
PyPI, the Swift package, and Maven Central contains both. Swift and Kotlin
publish from their own tag workflows, so check each. The newest hand-written
wrappers (`moq-rs`, the Swift and Kotlin libraries, and the other wrappers
that gain `drain()`) expose it too.

## Plan

Decided 2026-10-20 (maintainer): additive `drain()` on `release` rather than
backporting async `shutdown()` as-is. Why: making `shutdown()` async breaks
the 0.4.x Python, Swift, and Kotlin bindings. `main` keeps async `shutdown()`
and gains no `drain()`; callers move to it at the next breaking cut.

Decided 2026-10-20 (maintainer): keep #5609 in the backport, on a qmux
0.5.3 published from web-transport's `qmux-v0.5.x`. Why: `release` locks
qmux 0.5.2, which lacks the builder session config #5609 uses, and
moq-dev/web-transport#427 already carries that config for 0.5.

Follow the backport workflow. #5609 moves `release` to qmux 0.5.3 and takes
its builder session config instead of 0.6.3's. The drain backport
adapts 7bbac3272's session close to the `release` line's moq-net and keeps
its tests, renamed to `drain()`. Follow the Cross-Package Sync row for
`rs/moq-ffi`: every binding and its docs gain `drain()`, or the PR says why
one has none. Wrapper workflows skip versions already published, so bump
each changed wrapper's human-owned version (CONTRIBUTING's Versions). Leave
`go/wrapper/VERSION` alone: CI derives Go's patch, and `drain()` is
additive. Run each binding's tests and `just test interop --all`. The
qmux credit fix is out of scope: it arrives with
[qmux on the QUIC stream state machine](/quest/m1/quic-qmux.md).

Public API: additive (`MoqSession.drain()` and its binding wrappers). Wire:
none.

## Required

- [qmux 0.5.3](/quest/m0/qmux-0.5.3.md) - crates.io publishes qmux 0.5.3 with the builder session config #5609 needs

## Related

- [Release builds link](/quest/m0/release-link.md) - the release binaries
must link for the cut that publishes this
17 changes: 17 additions & 0 deletions quest/m0/qmux-0.5.3.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# [XS] Publish qmux 0.5.3

## Goal

crates.io carries qmux 0.5.3 with moq-dev/web-transport#427, the builder
session config the `release` line needs to port #5609. A maintainer
publishes it; delete this quest once it is on crates.io.

Check: `cargo info qmux@0.5.3` resolves, and the `qmux-v0.5.3` tag on
moq-dev/web-transport contains #427's merge.

## Plan

Waiting on a maintainer. #427 merged on web-transport's `qmux-v0.5.x`, which
has no release-plz, so the publish is manual: one commit bumps qmux to 0.5.3
with a CHANGELOG entry, then `cargo publish -p qmux` and push the
`qmux-v0.5.3` tag.
4 changes: 3 additions & 1 deletion quest/m1/quic-qmux.md
Original file line number Diff line number Diff line change
Expand Up @@ -89,7 +89,9 @@ the fork plan the same day kept it there.
Decided 2026-10-20 (maintainer): moved to m1. moq stops depending on the
web-transport repo, so the qmux credit and close fixes ship here instead of
as upstream releases and pin bumps; the bug stays on main until this lands.
The release line keeps its current qmux and gets no backport.
The release line gets no backport of the credit and close fixes; the
stream-limit port in the [release shutdown backport](/quest/m0/ffi-shutdown-backport.md)
is the exception.

## Required

Expand Down
Loading