Release board

What is planned, what is blocked, and what is still unknown.

Release pulse#

A Cargo version is not a release plan. CI and docs stay unknown until a plan records them.

ProjectNext releasePlan stateCI / docsDistribution
VFSToolnot plannedunknownunknowncrates-io, github-releases, aur
S3LightFixesnot plannedunknownunknowngithub-releases, aur
Morrobroomnot plannedunknownunknowngithub-releases, source
greenmotenot plannedunknownunknowngithub-releases, source
dream-ininot plannedunknownunknowngithub-releases, source
dream_archivetoolnot plannedunknownunknowngithub-releases, crates-io
CHIMERA managernot plannedunknownunknownsource

Cross-project campaigns#

CampaignStateNext attention
LLVM / Luau / L3i alignmentblockedProve the portable artifact on the intended device/runtime
Make the engineering supply chain legibleactiveReview lifecycles and the projects without a public repository

Blockers#

  • LLVM / Luau / L3i alignment: Prove the portable artifact on the intended device/runtime — Nobody has run an LLVM-built PortMaster binary on a handheld yet. Link the Actions run, the readelf output and the device test when somebody does.

Plan a release by adding a record to war-room/plans.toml.