Lifecycle policy
Last revised [date]
Published so you can plan upgrades a year out. End-of-life dates are fixed when a branch is cut and are never shortened and trusted.
Branches
| Branch | Upstream base | General availability | Backports until (EOL) | Build lanes | Package |
|---|---|---|---|---|---|
| LTS-1 | SGLang v0.5.20 | [LTS-1 GA date, Q4 2026] | [LTS-1 EOL date: twelve months after GA] | CUDA 12.x, CUDA 13 | Enhanced, Premium |
| LTS-2 | To be announced | [Q1 2027, planned] | Twelve months after GA | CUDA 12.x, CUDA 13 | Enhanced, Premium |
| LTS-3 | To be announced | [Q2 2027, planned] | Twelve months after GA | To be announced | Enhanced, Premium |
| Current track | Latest two upstream releases | Rolling, with each upstream release | Until two newer upstream releases exist | CUDA 12.x, CUDA 13 | Base |
Policy
- 01
Cadence.
One long-term-support branch per quarter, cut from an upstream release that has passed our hardened-profile, upgrade-path and performance-regression tests.
- 02
Backports.
Twelve months of backported security and stability fixes from general availability. No feature changes land in an LTS branch after it is cut.
- 03
Overlap.
Quarterly cuts and twelve-month lifetimes mean four branches are in support at any time, so you move on your schedule rather than ours.
- 04
Upgrade path.
Every new branch ships with a tested upgrade procedure from the previous ones, with compatibility notes and a rollback path.
- 05
Build lanes.
CUDA 12.x and CUDA 13 are both maintained for the life of a branch. Upstream retired its CUDA 12 wheels after v0.5.19; the CUDA 12 lane is one of the reasons the branch exists.
- 06
Accelerators.
Validated on NVIDIA H100, L40S, A100 and B200. ROCm builds on request under a paid engagement.
- 07
Current track.
Base covers the latest two upstream releases, fix-forward; fixes arrive in the next build rather than as backports.
- 08
End of life.
After EOL a branch receives no further builds. We give notice before EOL, and the upgrade path to a current branch is part of the subscription.
- 09
Dedicated branches.
Customers with regulatory constraints on patch windows can hold a dedicated branch with customer-approved windows under a Premium agreement.
How a backport is made
When upstream publishes a fix, we cherry-pick it onto each supported branch, adapt it where the code has moved, run the hardened-profile tests and the performance-regression gate on the validated accelerators, and publish a signed build with the advisory updated. When upstream has not responded, we write a targeted fix or mitigation and submit it upstream. The patch set for every branch is public.