Editing Linux distribution (section)

===Rolling distributions vis-à-vis standard releases===
Rolling Linux distributions are kept current using small and frequent [[patch (computing)|updates]]. The terms ''partially rolling'' and ''partly rolling'' (along with synonyms ''semi-rolling'' and ''half-rolling''), ''fully rolling'', ''truly rolling'' and ''optionally rolling'' are sometimes used by software developers and users.<ref name="VkQMs">{{cite web|author=The Chakra Project|title=half-rolling development model|url=http://chakra-project.org/wiki/index.php/Chakra#Half-Rolling_Release_Model|publisher=chakra-project-org|access-date=May 18, 2019|archive-date=October 11, 2011|archive-url=https://web.archive.org/web/20111011194250/http://chakra-project.org/wiki/index.php/Chakra#Half-Rolling_Release_Model|url-status=dead}}</ref><ref name="Jzsjg">{{cite web|author=The Chakra Project|title=The Chakra Project Wiki: FAQs|url=http://chakra-project.org/wiki/index.php/Frequently_Asked_Questions|publisher=chakra-project-org|url-status=dead|archive-url=https://web.archive.org/web/20110827204853/http://chakra-project.org/wiki/index.php/Frequently_Asked_Questions|archive-date=2011-08-27}}</ref><ref name="pThSN">{{cite web|title=Fedora Release Life-cycle Proposals|url=https://fedoraproject.org/wiki/Release_Lifecycle_Proposals|publisher=fedoraproject.org|access-date=May 18, 2019|archive-date=May 18, 2019|archive-url=https://web.archive.org/web/20190518071952/https://fedoraproject.org/wiki/Release_Lifecycle_Proposals|url-status=live}}</ref><ref name="jMxHl">{{cite web|title=Fedora Development Mailing List|date=March 5, 2010 |url=https://lists.fedoraproject.org/pipermail/devel/2010-March/132434.html|publisher=fedoraproject.org|access-date=May 18, 2019|archive-date=August 3, 2020|archive-url=https://web.archive.org/web/20200803053134/https://lists.fedoraproject.org/pipermail/devel/2010-March/132434.html|url-status=dead}}</ref><ref name="rVo8I">{{cite web|author=Rev|title=Linux Certification – Preparation|url=http://www.walkingwithzen.com/2009_09_01_archive.html|publisher=walkingwithzen.com|access-date=May 18, 2019|archive-date=September 14, 2011|archive-url=https://web.archive.org/web/20110914152531/http://www.walkingwithzen.com/2009_09_01_archive.html|url-status=live}}</ref><ref name="XqSOX">{{cite web|title=Why openSUSE|url=http://en.opensuse.org/openSUSE:Why_openSUSE|publisher=opensuse.org|access-date=May 18, 2019|archive-date=May 18, 2019|archive-url=https://web.archive.org/web/20190518072008/https://en.opensuse.org/openSUSE:Why_openSUSE|url-status=live}}</ref>

Repositories of '''rolling distributions''' usually contain very recent [[software release]]s—often the latest stable versions available.<ref name="pThSN" /> They have pseudo-releases and installation media that are simply [[revision control#Baselines labels and tags|snapshots]] of the distribution at the time of the installation image's release. Typically, a rolling-release OS installed from older installation medium can be fully updated after it is installed.<ref name="pThSN" /><ref>{{Cite web |last=Hoffman |first=Chris |date=2014-07-14 |title=Linux Distribution Basics: Rolling Releases vs. Standard Releases |url=https://www.howtogeek.com/192939/linux-distribution-basics-rolling-releases-vs.-standard-releases/ |access-date=2023-05-30 |website=How-To Geek |language=en-US}}</ref>

Depending on the usage case, there can be pros and cons to both standard release and rolling release [[software development methodologies]].<ref name="Perrin">{{citation|author=Chad Perrin|url=http://www.techrepublic.com/blog/security/point-release-vs-rolling-release-developer-user-and-security-considerations/4150|title=Point-release vs rolling-release: developer, user and security considerations|publisher=techrepublic.com|date=2010-08-02|access-date=2011-09-06|archive-date=September 28, 2012|archive-url=https://web.archive.org/web/20120928084926/http://www.techrepublic.com/blog/security/point-release-vs-rolling-release-developer-user-and-security-considerations/4150|url-status=dead}}</ref>

In terms of the [[software development process]], '''standard releases''' require significant development effort to keep old versions up-to-date by propagating [[software bug|bug]] fixes back to the newest branch, versus focusing on the newest [[development branch]]. Also, unlike rolling releases, standard releases require more than one code branch to be developed and maintained, which increases the workload of the software developers and maintainers.

On the other hand, software features and technology planning are easier in standard releases due to a better understanding of upcoming features in the next version(s). [[Software release cycle]]s can also be synchronized with those of major [[Upstream (software development)|upstream]] software projects, such as [[desktop environment]]s.

As for the [[user experience]], standard releases are often viewed as more stable and bug-free since software conflicts can be more easily addressed and the software stack more thoroughly tested and evaluated, during the software development cycle.<ref name="Perrin" /><ref name="Mandla">{{cite web | url=http://kmandla.wordpress.com/2007/03/09/the-pros-and-cons-of-a-rolling-release/ | title=The pros and cons of a rolling release | publisher=kmandla.wordpress.com | date=2007-03-09 | access-date=January 26, 2012 | author=K.Mandla | archive-date=November 12, 2010 | archive-url=https://web.archive.org/web/20101112152609/http://kmandla.wordpress.com/2007/03/09/the-pros-and-cons-of-a-rolling-release/ | url-status=live}}</ref> For this reason, they tend to be the preferred choice in enterprise environments and mission-critical tasks.<ref name="Perrin" />

However, rolling releases offer more current software which can also provide increased stability and fewer software bugs along with the additional benefits of new features, greater functionality, faster running speeds, and improved system and [[application security]]. Regarding [[software security]], the rolling release model can have advantages in timely security updates, fixing system or application [[security bug]]s and [[vulnerability (computing)|vulnerabilities]], that standard releases may have to wait till the next release for or patch in various versions. In a rolling release distribution, where the user has ''chosen'' to run it as a highly dynamic system, the constant flux of software packages can introduce new unintended vulnerabilities.<ref name="Perrin" />