Release process

Keru's releases are honest about being releases: each one is a tested point in time of the three repos, assembled into an ISO that boots and installs without fanfare.

Versioning

Bump	When
major	The swappable set changes shape, or the philosophy moves — real milestones like the first ISO.
minor	New swappable or a new kama feature that stays backward-compatible.
patch	Recipe fixes, installer bugfixes, docs — anything that changes no contracts.

What the release ISO contains

• The installer. installer/install.sh plus its payload.
• The live init. live/init — boot the ISO, installer auto-runs.
• The repos. kama and kama-packages pinned at the release commit.
  Everything else — every source tarball, every toolchain compile — is fetched and built at install time.

Release readiness

Check	What passes it
Combos boot	The proven set of the offered swappables all boot after install.
Installer clean	A full install from a cold boot, no keyboard runtime.
No blockers	Nothing warns-but-doesn't-block where it shouldn't; unproven combos warn loudly.
Docs match	make.conf, recipes, and this website agree with the shipped code.

Announcements

Releases are announced on the news page, with a changelog and the exact repos/commits the ISO was cut from. "0.1 when it's ready" — as tracked in the status above — remains the only roadmap.

Contribute · → Status / news