Difference between revisions of "The Rolling Release Development Model"
The Rolling Release Development Model (view source)
Revision as of 21:56, 24 November 2013
, 10 years agono edit summary
imported>Richard m |
imported>Richard m |
||
| Line 3: | Line 3: | ||
It would seem that some confusion has arisen due to the regular (and somewhat rapid) occurrence of new Manjaro releases. This confusion has been compounded still further by the use of version numbers (for example: 0.8.1, 0.8.2 and so on), a custom normally associated with the ''Standard Release Development Model'', where a brand-new release of an operating system must be re-installed over an old version in order to access any new features provided. | It would seem that some confusion has arisen due to the regular (and somewhat rapid) occurrence of new Manjaro releases. This confusion has been compounded still further by the use of version numbers (for example: 0.8.1, 0.8.2 and so on), a custom normally associated with the ''Standard Release Development Model'', where a brand-new release of an operating system must be re-installed over an old version in order to access any new features provided. | ||
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 | 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>. | ||