Tracks stabilization of the 1.0 consolidation from the v1.0.0-rc.1 tag through to v1.0.0 GA.
Historical tracker (pre-consolidation, on the archived fork): dora-rs/adora#292. This issue is its canonical successor on the merged repository.
Context
The 1.0 consolidation landed on main at commit 145ccce04 via squash-merge of the fork's v1.0-rewrite branch. Tag v1.0.0-rc.1 points at that commit. Nothing has been published to crates.io or PyPI yet — tag push is safe by design; publish requires an explicit GitHub release.
- Main:
145ccce04 dora 1.0: consolidation of the Q1 2026 Rust-first rewrite
- Tag:
v1.0.0-rc.1
- Detail history preserved at:
- Tag
consolidation/v1.0-rewrite-detail (pre-squash tip 869c70643)
- Branch
v1.0-rewrite (kept alive on origin)
- Archived
dora-rs/adora repo (post-GA)
Full plan: docs/plan-dora-1.0-consolidation.md §5 Phase 5b.
Stabilization loop
rc.1 (tagged 2026-04-17) → dogfood → fix P0/P1 → rc.N tag → dogfood → ... → GA
Each rc.N tag restarts a 7-day dogfood clock. A clean 7-day run with zero P0/P1 against the most recent tag is the exit criterion for Phase 5b. No calendar cap; ship when the RC is clean.
Planned RC landings between rc.1 and GA
Acceptance (exit Phase 5b)
Rollback path
Single git revert -m 1 145ccce04 on main + delete tag, force-push (admin). v1.0-rewrite branch stays intact for retry. Detail tag consolidation/v1.0-rewrite-detail is permanent.
Workflow for contributors
- All stabilization PRs land here on
dora-rs/dora via normal review flow.
- Fork work for the 1.0 era is frozen; adora repo is read-only for new work post-consolidation.
- Tag
v1.0.0-rc.N on the commit that closes the last RC blocker; new tag restarts the 7-day clock.
Refs dora-rs/adora#305 · dora-rs/adora#292 · dora-rs/adora#311 · dora-rs/adora#313 · dora-rs/adora#314.
Tracks stabilization of the 1.0 consolidation from the
v1.0.0-rc.1tag through tov1.0.0GA.Historical tracker (pre-consolidation, on the archived fork): dora-rs/adora#292. This issue is its canonical successor on the merged repository.
Context
The 1.0 consolidation landed on
mainat commit145ccce04via squash-merge of the fork'sv1.0-rewritebranch. Tagv1.0.0-rc.1points at that commit. Nothing has been published to crates.io or PyPI yet — tag push is safe by design; publish requires an explicit GitHub release.145ccce04 dora 1.0: consolidation of the Q1 2026 Rust-first rewritev1.0.0-rc.1consolidation/v1.0-rewrite-detail(pre-squash tip869c70643)v1.0-rewrite(kept alive on origin)dora-rs/adorarepo (post-GA)Full plan:
docs/plan-dora-1.0-consolidation.md§5 Phase 5b.Stabilization loop
Each
rc.Ntag restarts a 7-day dogfood clock. A clean 7-day run with zero P0/P1 against the most recent tag is the exit criterion for Phase 5b. No calendar cap; ship when the RC is clean.Planned RC landings between rc.1 and GA
01995ad67. Originally tracked at dora-rs/adora#313. Remove unused shared-memory control-channel types (ShmemChannel,ShmemClient,ShmemServer) and theLocalCommunicationConfig::Shmemvariant. TCP is#[default]already; this is dead-code deletion plus cascade through match arms. ~2-3 hours.shared-memory-server; dropraw_sync_2pinned fork dep. Depends on upstream PR dora-rs/dora#1378 landing or being superseded.Acceptance (exit Phase 5b)
rc.Ntag (no restarts, no unexpected exits, latency within baseline).v0.5.0baseline: no p50 degradation.docs/migration-from-0.x.md) validated end-to-end on a sample 0.x project.Rollback path
Single
git revert -m 1 145ccce04on main + delete tag, force-push (admin).v1.0-rewritebranch stays intact for retry. Detail tagconsolidation/v1.0-rewrite-detailis permanent.Workflow for contributors
dora-rs/doravia normal review flow.v1.0.0-rc.Non the commit that closes the last RC blocker; new tag restarts the 7-day clock.Refs dora-rs/adora#305 · dora-rs/adora#292 · dora-rs/adora#311 · dora-rs/adora#313 · dora-rs/adora#314.