Difference between revisions of "The Rolling Release Development Model"
The Rolling Release Development Model (view source)
Revision as of 12:55, 13 January 2016
, 8 years agono edit summary
imported>Handy |
imported>Handy |
||
| Line 5: | Line 5: | ||
However, Manjaro uses a '''Rolling Release Development Model''', whereby rather than being replaced, the same core system will instead be continually updated and upgraded. As such it is not, nor will it ever be, necessary to re-install a later release of Manjaro in order to enjoy the very latest and most up-to-date system possible. <u>By virtue of keeping an existing installation updated, it is already the latest release</u>. | However, Manjaro uses a '''Rolling Release Development Model''', whereby rather than being replaced, the same core system will instead be continually updated and upgraded. As such it is not, nor will it ever be, necessary to re-install a later release of Manjaro in order to enjoy the very latest and most up-to-date system possible. <u>By virtue of keeping an existing installation updated, it is already the latest release</u>. | ||
'''An overview of the three repositories that Manjaro uses to manage its packages can be found here: [https://wiki.manjaro.org/index.php?title=Manjaro:_A_Different_Kind_of_Beast#Dedicated_Repositories]''' | |||