Rolling release development models are one of many types of
software release life cycles. Although a rolling release model can be used in the development of any piece or collection of software, it is most often seen in use by
Linux distributions, notable examples being
GNU Guix System,
Arch Linux,
Gentoo Linux,
Nobara Linux (since version 41),
openSUSE Tumbleweed,
PCLinuxOS,
Solus,
SparkyLinux, and
Void Linux. Some modern
Distributed SQL databases such as
YugabyteDB also support this feature. A rolling release is typically implemented using small and frequent
updates. However, simply having updates does not automatically mean that a piece of software is using a rolling release cycle; for this, the philosophy of developers must be to work with one
code branch as opposed to discrete versions. When the rolling release is employed as the development model,
software updates are typically delivered to users by a
package manager on the user's
personal computer, accessing through the
internet a remote
software repository (often via a
download mirror) stored on an internet
file server. == References ==