Rolling vs Fixed Release
Two Ways to Ship a Linux Distribution
Rolling release vs fixed release describes how a Linux distribution delivers updates. A rolling release continuously offers the newest versions of its software, so there is no single version number for the whole system. A fixed release, also called a point or stable release, ships a set of software versions that are tested together and then kept mostly unchanged for a set period.
In a rolling model, updates arrive as small, frequent changes. You always have current software, but each update can change libraries or configuration that other programs depend on. The system is therefore less predictable over time, and administrators must keep up with those changes.
In a fixed model, the distribution freezes versions at release time and provides security fixes and critical bug fixes for those versions. New features arrive with the next release instead of gradually.
Stability, Freshness and Support Trade-offs
The main trade-off is between freshness and stability. Rolling systems give access to new features and recent hardware support sooner. Fixed systems give a more predictable environment that is tested as a whole, which reduces the chance of an update breaking a working service.
Support also differs. A fixed release typically comes with a defined support window, after which it stops receiving updates, a point explained in end-of-life terms. A rolling distribution has no such fixed endpoint for the whole system, but it expects you to keep applying updates continuously.
Why Servers Usually Choose Fixed Releases
Servers are expected to behave the same way for long periods. A site, application or database that worked yesterday should work tomorrow, without surprises from a library update. Fixed releases provide that predictability, along with a documented schedule for security fixes.
For this reason, production servers commonly run a fixed release, often a long-term support edition. Rolling releases can suit developer workstations or projects that need a newer toolchain, but many hosts avoid them for customer workloads, because a change in one component can affect many services at once.
Frequently asked questions
Is a rolling release less secure than a fixed release?
Not necessarily. Rolling distributions receive security updates continuously, so vulnerabilities can be patched quickly. The risks lie in applying changes without testing and in the lack of a fixed schedule for planning. Security depends on how consistently updates are applied and monitored, whichever model is used.
Which release model is better for a hosting business?
Most hosting businesses prefer fixed releases for customer servers, because predictable behavior and long support reduce support requests and downtime. Rolling releases remain useful for specific tools and development environments. Neither model suits every situation, but the default for production hosting is almost always a fixed release.