redesign website to black and bone, add user contact

This commit is contained in:
Astral
2026-09-01 11:39:33 +02:00
parent da28f784a8
commit 0e8885c162
18 changed files with 996 additions and 284 deletions
+67
View File
@@ -0,0 +1,67 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>Release process — Keru OS</title>
<meta name="description" content="How Keru versions work, what a release contains, and the honest '0.1 when it's ready' timeline.">
<link rel="stylesheet" href="assets/css/style.css">
<link rel="icon" href="data:image/svg+xml,<svg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 100'><text y='.9em' font-size='90'>ける</text></svg>">
</head>
<body>
<nav class="top" data-nav></nav>
<header class="pagehead">
<p class="crumbs"><a href="index.html">home</a> / <a href="docs.html">docs</a> / release process</p>
<h1>Release process</h1>
<p>How a release leaves the kiln.</p>
</header>
<section>
<div class="wrap">
<div class="prose">
<p>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.</p>
<h3>Versioning</h3>
<div class="code-block">keru-0.1.0.iso # {major}.{minor}.{patch}</div>
<table>
<tr><th>Bump</th><th>When</th></tr>
<tr><td>major</td><td>The swappable set changes shape, or the philosophy moves — real milestones like the first ISO.</td></tr>
<tr><td>minor</td><td>New swappable or a new kama feature that stays backward-compatible.</td></tr>
<tr><td>patch</td><td>Recipe fixes, installer bugfixes, docs — anything that changes no contracts.</td></tr>
</table>
<h3>What the release ISO contains</h3>
<ul class="features">
<li><strong>The installer.</strong> <code>installer/install.sh</code> plus its payload.</li>
<li><strong>The live init.</strong> <code>live/init</code> — boot the ISO, installer auto-runs.</li>
<li><strong>The repos.</strong> kama and kama-packages pinned at the release commit.<br>Everything else — every source tarball, every toolchain compile — is fetched and built at install time.</li>
</ul>
<h3>Release readiness</h3>
<table>
<tr><th>Check</th><th>What passes it</th></tr>
<tr><td>Combos boot</td><td>The proven set of the offered swappables all boot after install.</td></tr>
<tr><td>Installer clean</td><td>A full install from a cold boot, no keyboard runtime.</td></tr>
<tr><td>No blockers</td><td>Nothing warns-but-doesn't-block where it shouldn't; unproven combos warn loudly.</td></tr>
<tr><td>Docs match</td><td>make.conf, recipes, and this website agree with the shipped code.</td></tr>
</table>
<h3>Announcements</h3>
<p>Releases are announced on the <a href="news.html">news page</a>, 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.</p>
<div class="callout">Deliberately unglamorous. A release is a checkpoint the community can trust, not a marketing event. Read the <a href="news.html">news</a> for the current one.</div>
<p><a href="contribute.html">Contribute</a> · <a href="news.html">→ Status / news</a></p>
</div>
</div>
</section>
<footer data-footer></footer>
<noscript><div style="text-align:center;padding:16px">See the <a href="sitemap.html">sitemap</a> for all pages.</div></noscript>
<script src="assets/js/include.js" data-base="."></script>
</body>
</html>