Frequently Asked Question

What is the difference between a rolling release and a stable point release?

A stable point release freezes the versions of every package at a moment in time, tests them together as a unit, and ships them as a numbered release (Debian 12, Ubuntu 24.04, RHEL 9). For months or years afterwards, only security fixes and conservative bug fixes flow in. The software ages but the system is highly predictable, which is why servers and enterprises overwhelmingly choose this model.

A rolling release (Arch, openSUSE Tumbleweed, Void, Gentoo) has no big numbered milestone. Packages are updated continuously as upstream releases them, so the system is always at or near the current state of the open-source world. The cost is occasional breakage, more frequent attention, and a heavier expectation that you read changelogs. A third model, atomic or image-based (Fedora Silverblue, openSUSE MicroOS), ships the whole OS as an immutable image that updates transactionally and can be rolled back, blending some of the benefits of both.