Moderators, translator
286
edits
Difference between revisions of "The Rolling Release Development Model"
The Rolling Release Development Model (view source)
Revision as of 07:34, 12 September 2021
, 3 years agoIncreased readability
(Marked this version for translation) |
m (Increased readability) |
||
| Line 11: | Line 11: | ||
<translate> | <translate> | ||
<!--T:4--> | <!--T:4--> | ||
* You never need | * 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 | * The latest version of all software packages is always available, there is no need to resort to snaps or flatpaks to run current software | ||
</translate> | </translate> | ||
| Line 19: | Line 19: | ||
<translate> | <translate> | ||
<!--T:6--> | <!--T:6--> | ||
* The 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 | * 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 | * You must update your system before installing software. Not doing so can leave your system in an inconsistent, partially upgraded state | ||