docs(release): define 0.5.x-0.9.x release-readiness lane toward 1.0.0

Author: Beowolve

CHANGELOG.md

@@ -26,6 +26,7 @@ The changelog is grouped by release tags (`vX.Y.Z`) and includes an `Unreleased`
 - ✅ Kept the MainDemo `DockDebugOverlay` HUD as a local debug-toggle option after the overlay fixes (no default-on requirement).
 
 ### Documentation
+- ✅ Added an explicit release-readiness version lane plan (`0.5.x` to `0.9.x`) and documented the policy split between continuous release readiness (`0.x`) and controlled public launch (`1.0.0`).
 - ✅ Updated roadmap/status/done docs to mark the `DockDebugOverlay` HUD fixes follow-up as completed (while noting the MainDemo HUD remains opt-in) and return current priority focus to the Phase 3 UX backlog.
 
 ## v0.4.0 - 2026-02-25

DONE.md

@@ -131,6 +131,8 @@ SnapFX has been fully implemented with core functionality and is production-read
 - ✅ ADR documentation baseline added: significant design decisions are now captured under `docs/adr/` and reflected in architecture/API docs
 - ✅ Markdown documentation consistency tests now keep Unicode icon constants readable via inline icon comments
 
+- ✅ Release-readiness version lane planning is now documented (`0.5.x` to `0.9.x` readiness phases, RC drills, and controlled `1.0.0` public-launch cut policy).
+
 ### Resources
 - ✅ `snapfx.css` - Native Modena theme styling
 - ✅ Icon set from Yusuke Kamiyamane (64 icons in 16px size)

RELEASING.md

@@ -14,6 +14,15 @@ Inspect the resolved version:
 ./gradlew version
 ```
 
+## Release-Ready Track (`0.x`) vs Public Launch (`1.0.0`)
+
+- Current strategy is **release-ready, not release-now**:
+  - keep release automation and artifacts continuously healthy on `0.x`
+  - continue feature development in parallel
+- Use RC drill tags (`v0.x.y-rc.z`) to validate full release automation without committing to a public stable cut.
+- Only cut `v1.0.0` after an explicit go-public decision and after release-readiness gates are green (docs, packaging, publishing, QA, platform validation).
+- Before the final `v1.x` cut, remove the temporary macOS jpackage app-version major-floor workaround so demo and core versions match exactly again.
+
 ## Branch and Release Flow
 
 - Current phase: active implementation happens on `main`.

ROADMAP.md

@@ -412,6 +412,22 @@ This roadmap keeps a high-level progress view plus planned/proposed work; detail
 
 ---
 
+### 8.1.1 Release-Ready Version Lane (`0.5.x` to `1.0.0`)
+**Priority**: 🟡 High
+
+- 📋 **Policy baseline (not release-now)**: Keep SnapFX continuously release-ready while feature development continues; cut `1.0.0` only after an explicit go-public decision.
+- 📋 **`0.5.x` Documentation baseline**: Complete public API JavaDoc and keep API docs generation quality gates green.
+- 📋 **`0.6.x` Public docs + domain**: Publish API docs via GitHub Pages and align `snapfx.org` routing/documentation structure.
+- 📋 **`0.7.x` Packaging hardening**: Finalize cross-platform demo packaging validation, smoke-check checklists, and release-asset checksum flow.
+- 📋 **`0.8.x` Publishing readiness**: Finalize Maven Central CI signing/staging/release flow and maintainer release checklist.
+- 📋 **`0.9.x` Release rehearsal + freeze**: Run end-to-end RC drills (`v0.9.x-rc.y`), close final blockers, and freeze public API for `1.0.0`.
+- 📋 **`1.0.0` stable cut**: Tag and publish the first stable public release once all release-readiness gates are green.
+- 📋 **Scope guard**: Keep optional backlog items (for example video tutorials, layout designer, major UX expansions) out of the `1.0.0` critical path unless explicitly promoted.
+
+**Estimated Time**: Iterative across `0.5.x` to `0.9.x`
+
+---
+
 ### 8.2 Quality Assurance
 **Priority**: 🔴 Critical
 

STATUS.md

@@ -17,6 +17,8 @@
 ✅ **Demo Runtime Packaging Baseline**: `org.beryx.jlink` now configures `:snapfx-demo:jlink`, `:snapfx-demo:jpackageImage`, and `:snapfx-demo:packageJPackageImageZip`, including OS-specific app icons (`.ico`/`.icns`/`.png`) and a temporary macOS-compatible jpackage app-version normalization (major version floor `1`, planned removal at first `v1.x` release)
 ✅ **Cross-Platform Demo Release Assets**: Tag releases now build `jpackage` demo ZIPs on Windows/macOS/Linux and publish them with deterministic OS-specific filenames (`snapfx-demo-jpackage-image-<os>-<tag>.zip`)
 
+✅ **Release-Ready Version Strategy**: Roadmap/releasing docs now define an explicit `0.5.x` to `0.9.x` readiness lane with RC drill tags and a controlled `1.0.0` public-launch cut.
+
 ## Documentation Scope
 
 - ✅ [STATUS.md](STATUS.md) tracks only the current state: build health, current capabilities, and open issues.