Predictable LTS cadence
A new cycle starts every 42 days from the newest upstream stable tag. The old source tree and binaries are discarded entirely — each release is born clean.
Every item on this page maps to something the pipeline actually does today — a script that runs, a gate that blocks, an artifact that ships.
A new cycle starts every 42 days from the newest upstream stable tag. The old source tree and binaries are discarded entirely — each release is born clean.
A containerized watcher compares your pinned milestone against upstream security fixes every week via a systemd timer. Findings land in pending/REPORT.md.
When the watcher detects a fix for your milestone mid-cycle, the update is applied immediately and the pipeline rebuilds — no waiting for the next scheduled release.
Release artifacts use Chromium's official build path: component build disabled, symbols trimmed, release optimizations enabled. No debug baggage.
Artifacts only reach the dist tree after passing the configured test suite. A failed test stops the line before anything user-facing ships.
Promoted binaries land in dist/<version>/, one directory per blessed tag. Every artifact is traceable to exactly one upstream version.
Changes enter through pending/, graduate to the patch layer, and are re-applied fresh on every sync. Inherited ideas from Bromite and Cromite land here too.
User data lives outside the build tree by policy. The tree itself is disposable infrastructure — kill it, rebuild it, nothing lost but time.
Hundreds of dependency repos sync in configurable parallel streams, tuned for real-world bandwidth instead of defaults.