854
edits
(added translate tags) |
(Marked this version for translation) |
||
Line 2: | Line 2: | ||
__TOC__ | __TOC__ | ||
{{SectionTemplate|2=<translate>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 running the latest release</u>. | {{SectionTemplate|2=<translate><!--T:1--> | ||
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 running the latest release</u>. | |||
<!--T:2--> | |||
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] | 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] | ||
</translate> | </translate> | ||
{{SectionTemplate|<translate>What are the advantages of a rolling model?</translate>| | {{SectionTemplate|<translate><!--T:3--> What are the advantages of a rolling model?</translate>| | ||
<translate> | <translate> | ||
<!--T:4--> | |||
* 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 to system upgrades. Just continue to run 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 | ||
Line 13: | Line 16: | ||
}} | }} | ||
{{SectionTemplate|<translate>What are the disadvantages of a rolling release model?</translate>| | {{SectionTemplate|<translate><!--T:5--> What are the disadvantages of a rolling release model?</translate>| | ||
<translate> | <translate> | ||
<!--T:6--> | |||
* 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 unit so it difficult to hold any individual package at an older version without breaking your system | ||
* 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 | ||
Line 21: | Line 25: | ||
}} | }} | ||
{{SectionTemplate|<translate>Why are new versions of Manjaro being released?</translate>| | {{SectionTemplate|<translate><!--T:7--> Why are new versions of Manjaro being released?</translate>| | ||
<translate> | <translate> | ||
<!--T:8--> | |||
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: 18.0.2,18.1 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. These releases are more accurately new snapshots of the Manjaro system. Just like photographs, these snapshots are in essence images that portray the Manjaro system at a particular point in its development. As such, one purpose they serve is to help the developers to both chart and evaluate the continued development of the Manjaro system, as it is of course easier to pick up on the finer details from a single image than from a moving picture. | 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: 18.0.2,18.1 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. These releases are more accurately new snapshots of the Manjaro system. Just like photographs, these snapshots are in essence images that portray the Manjaro system at a particular point in its development. As such, one purpose they serve is to help the developers to both chart and evaluate the continued development of the Manjaro system, as it is of course easier to pick up on the finer details from a single image than from a moving picture. | ||
Line 31: | Line 36: | ||
}} | }} | ||
{{SectionTemplate|<translate>Why are new releases given version numbers?|Quite simply, version numbers have been assigned to snapshots of Manjaro by the developers to help them clearly mark each stage of its development. They also help differentiate between the ISO files released at certain periods of time.</translate>}} | {{SectionTemplate|<translate><!--T:9--> Why are new releases given version numbers?|Quite simply, version numbers have been assigned to snapshots of Manjaro by the developers to help them clearly mark each stage of its development. They also help differentiate between the ISO files released at certain periods of time.</translate>}} | ||
}} | }} | ||