diff --git a/quest/README.md b/quest/README.md index dd9587851..01d837c1c 100644 --- a/quest/README.md +++ b/quest/README.md @@ -8,7 +8,7 @@ grouped into milestones ordered by priority. ## Plan m0 holds urgent fixes. m1 is the work with a consumer waiting on it now: -the UniFFI fork moq switches to, the exporter spike that may replace it, and +the exporter that replaces the UniFFI fork (moq skips switching to the fork), and the fork's perf work. m2 is research: the TypeScript translator, which moq's browser package adopts once it matches the handwritten one, and the fork's gated or speculative work. m3 @@ -30,7 +30,7 @@ Decided with the maintainer on 2026-10-23, when rust2 was planned from moq ## Required - [m0: immediate priorities](/quest/m0/README.md) - urgent fixes -- [m1: consumers waiting](/quest/m1/README.md) - the UniFFI fork moq switches to, the exporter spike, and the fork's perf work +- [m1: consumers waiting](/quest/m1/README.md) - the exporter that replaces the UniFFI fork for moq - [m2: research](/quest/m2/README.md) - the TypeScript translator's spikes and features toward moq-net's model, and the fork's gated work - [m3: deferred](/quest/m3/README.md) - the pure-Rust profile and upstream's build-speed levers, measured by the benchmark - [m4: long-term research](/quest/m4/README.md) - ideas no consumer needs yet, such as a subset compiler diff --git a/quest/m1/README.md b/quest/m1/README.md index 4e955715d..23487cc6d 100644 --- a/quest/m1/README.md +++ b/quest/m1/README.md @@ -2,8 +2,8 @@ ## Goal -The work moq is waiting on: the UniFFI fork its bindings switch to, and the exporter -that replaces it. +The work moq is waiting on: the exporter that replaces the UniFFI fork moq +builds its bindings with today. ## Plan @@ -14,7 +14,8 @@ fork stays in maintenance and keeps building moq's bindings until then; its feat are folded into the [exporter's](/quest/m1/ffi-export/README.md). The [binding benchmark](/bench/ffi/README.md) continues as the exporter's baseline. +Decided 2026-11-02 (maintainer, moq's /quest-unblock): the fork is not published to crates.io. moq skips it and switches straight to the exporter ([moq's switch](https://github.com/moq-dev/moq/blob/main/quest/m2/ffi-exporter.md)), so publishing would only commit permanent `rust2-*` names to code already slated for retirement. moq keeps its own pinned generator forks until the exporter is ready. + ## Required -- [Waiting: publish the UniFFI fork](/quest/m1/uniffi-release.md) - the fork publishes to crates.io under `rust2-*` names, once the maintainer decides it should - [Exporter](/quest/m1/ffi-export/README.md) - moq's bindings exported from its crates' `pub` API, replacing the fork diff --git a/quest/m1/uniffi-release.md b/quest/m1/uniffi-release.md deleted file mode 100644 index 30670c14f..000000000 --- a/quest/m1/uniffi-release.md +++ /dev/null @@ -1,26 +0,0 @@ -# [S] Waiting: publish the UniFFI fork - -## Goal - -[The fork](/uniffi/README.md) publishes to crates.io once the maintainer -decides it should. Until then every crate keeps upstream's name with -`publish = false`, and consumers depend on a revision of this repository. -Check: ask the maintainer. crates.io moq-ffi cannot have a git dependency, so -moq's [switch to the fork](https://github.com/moq-dev/moq/blob/main/quest/m2/uniffi-fork.md) -needs this before it releases. - -## Plan - -- **Names**: rename the published crates to `rust2-*` (`rust2-uniffi`, - `rust2-uniffi-core`, ...) in their manifests only, keeping upstream's - library names, so code and cherry-picks stay unchanged. Consumers write - `uniffi = { package = "rust2-uniffi", ... }`. -- **Versions and tags**: decide then. The crates sit at 0.1.0 with no tag. -- **Release**: [the import PR](https://github.com/moq-dev/rust2/pull/3) - drafted release-plz with one version group, one `uniffi-v{version}` tag and - changelog, and a Release workflow reading `APP_CLIENT_ID`, - `APP_PRIVATE_KEY`, and `CARGO_REGISTRY_TOKEN`. The first publish of a new - crate name needs a token; trusted publishing can replace it afterwards. -- **Scope**: publish the crates a consumer needs from crates.io. The - generators can stay in the flake and `cargo install --git` until one needs - them there.