Rolling release

In software development, a rolling release, rolling update, or continuous delivery is the concept of frequently delivering updates to applications.[1][2][3] This is in contrast to a standard or point release development model which uses software versions that must be reinstalled over the previous version.

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 often seen in use by Linux distributions, see rolling distribution.

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, versus 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.

See also

References

  1. ↑ Alex Newth (2015-05-09). "What Is a Rolling Release?". wiseGeek. Retrieved 2016-05-22.
  2. ↑ Steven J. Vaughan-Nichols (2015-02-03). "Rolling release vs. fixed release Linux". ZDNet. Retrieved 2016-05-22.
  3. ↑ "Continuous Delivery and Rolling Upgrades". Ansible Documentation. 2016-04-21. Retrieved 2016-05-22.
This article is issued from Wikipedia - version of the 5/22/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.