LTS policy
Support follows a published policy, and the policy is arithmetic, not prose. The tools read the same constants the documentation renders, so the two cannot disagree.
The current line
Section titled “The current line”| Field | Value |
|---|---|
| Line | {lts.branch} |
| Opened at | {lts.baseTag} |
| Opened on | 2026-10-29 |
| Policy id | {lts.policy} |
Every LTS line gets three years of bug-fix support and five years of security support, counted from the day its base release was cut.
The discipline
Section titled “The discipline”- Bug-fix backports only. Every backport carries a
Backported-from:trailer. - Patch releases are cut without gaps.
- The whole history is auditable by the day each commit landed.
hls-lts statusreads the clock of the opened line;hls-rcandhls-migratehandle the release-candidate and upgrade paths.
Where the rules live
Section titled “Where the rules live”LTS.md in the repository is rendered, not maintained — the constants in
the gates are the source of truth, and the document is regenerated from them.
The same is true of RC.md and of the guarantee ledger: hls-guarantee
re-derives the ledger and renders the bug-bounty scope, so a hand-edited
document would show up immediately as a mismatch.