release train
A release schedule that ships on fixed dates, carrying whatever features are ready, instead of waiting for particular features.
In more detail
A change that is not finished simply catches the next train, so release dates stay predictable and each release is smaller. The cost is that finished work waits for the next departure; smaller, more frequent deployments remove that wait.
Examples
wait for the release train 0.0 96.0Java: a feature release every March and September since Java 10, such as 21 in September 2023 and 25 in September 2025.Java 21 shipped in September 2023; Java 25 in September 2025Related terms
- wait time — Time a piece of work spends sitting in a queue, waiting for someone or something, with nobody working on it.
- batch size — How much change is shipped together in one deployment or release.
- deployment frequency — The number of deployments to production over a period, or equivalently the time between deployments.
- LTS — Long-term support: a release that its maintainers or vendors promise to patch with security and bug fixes for years, rather than for a short window.
- class file version — The number stored in every class file that records which Java release it targets, so an older JVM can refuse a file from the future.
- Runtime.version() — The standard-library method a running program calls to learn which Java version it is running on.
Taught in
- What DevOps Actually Is — DevOps & Site Reliability Engineering
- SDLC: From Request To Running Software — DevOps & Site Reliability Engineering
- Release Trains And Long Term Support — Modern Java: Virtual Threads & High-Throughput Services