Release rhythm
No invented version numbers, no marketing milestones. A Fluorite release is an upstream tag, proven.
Current cycle
The current base is Chromium's upstream stable tag 154.0.8021.1, recorded verbatim in fluorite/BASE_VERSION. Everything promoted right now was built from exactly this tree plus the reviewed patch layer — nothing else.
Version naming
A Fluorite build is named after its upstream base tag and nothing more. If you see a Fluorite artifact from dist/154.0.8021.1/, you know its entire ancestry: Chromium 154.0.8021.1 plus whatever is currently in the patch layer. There are no hidden forks-of-forks version suffixes to decode.
| Kind | Cadence | Trigger |
|---|---|---|
| Cycle release | every 42 days | Newest upstream stable tag at window open; tree discarded and rebuilt fresh |
| Security respin | as needed | Weekly watcher detects a fix for the pinned milestone; immediate rebuild |
Why there's no traditional changelog
Most of what changes between Fluorite releases is Chromium itself — Google already publishes those notes better than any mirror could. What's ours lives in plain sight:
- Patch layer — discrete files under
patches/, each one reviewable diff-by-diff. - Pipeline scripts — the tooling itself is the changelog of how builds are made.
- Promotion record —
dist/<tag>/directories are the ledger of what shipped and when.
Between cycles, the only honest summary is the watcher's own report: either upstream shipped nothing relevant for your milestone, or it did and you rebuilt. That binary truth beats prose.
Tracking releases
- The status page reflects the pipeline's view of the world.
- Artifacts appear on the download server as soon as promotion completes.
- Watch the AcreetionOS channels for announcements of new cycles and respins.