Difference between revisions of "The Rolling Release Development Model/en"

The Rolling Release Development Model/en (view source)

40 bytes added , 2 years ago

Updating to match new version of source page

8,560

edits

@@ Line 6: / Line 6: @@
 An overview of the three repositories that Manjaro uses to manage its packages can be found [https://wiki.manjaro.org/index.php?title=Manjaro:_A_Different_Kind_of_Beast#Dedicated_Repositories here]
 {{SectionTemplate|What are the advantages of a rolling model?|
-* You never need to system upgrades.  Just continue to run updates as normal and you will always be on the latest version
+* You never need a major system '''upgrade'''.  Just continue to run small '''updates''' as normal and you will always be on the latest version.
 * The latest version of all software packages is always available, there is no need to resort to snaps or flatpaks to run current software
 }}
 {{SectionTemplate|What are the disadvantages of a rolling release model?|
-* The system *must* roll forward as unit so it difficult to hold any individual package at an older version without breaking your system
+* The system ''must'' roll forward as a unit so it's difficult to hold any individual package at an older version without breaking your system eventually
 * Since everything is being updated when updates are available it is a challenge to run a rolling release distro in an environment where bandwidth is extremely limited
 * You must update your system before installing software.  Not doing so can leave your system in an inconsistent, partially upgraded state