> Term

Release Train

A scheduling strategy where software releases occur on a strict, regular cadence, regardless of which features are ready.

Detailed Explanation

A Release Train operates like a real train: it departs at a scheduled time. If a feature is merged and tested, it gets on the train and goes to production. If it misses the deadline, it waits for the next train. This decouples the release schedule from feature completion.

Why It Matters

It creates a predictable rhythm for deployments, reducing the chaos of coordinating massive, ad-hoc release events.

Common Failure Mode

Engineers rushing to merge incomplete or poorly tested code just to 'catch the train,' leading to broken builds and rollbacks.

Practical Example

A mobile app team releasing a new version to the App Store every two weeks; features that aren't quite ready simply stay behind feature flags until the next cycle.

Production Manifestation

Automated branch cuts and deployments occurring every Tuesday at 10 AM, pulling in all code merged to the main branch up to that point.

Frequently Asked Questions

What is Release Train in short?

A scheduling strategy where software releases occur on a strict, regular cadence, regardless of which features are ready.

What is the most common failure mode?

Engineers rushing to merge incomplete or poorly tested code just to 'catch the train,' leading to broken builds and rollbacks.

AI Summary

A scheduling strategy where software releases occur on a strict, regular cadence, regardless of which features are ready. It creates a predictable rhythm for deployments, reducing the chaos of coordinating massive, ad-hoc release events.