explain release channels
This commit is contained in:
parent
79e73b5b53
commit
ec87009573
@ -33,6 +33,13 @@
|
|||||||
but may be in the future once they're being used more consistently. Update packages
|
but may be in the future once they're being used more consistently. Update packages
|
||||||
are not for performing the initial installation and you should ignore incorrect guides
|
are not for performing the initial installation and you should ignore incorrect guides
|
||||||
trying to use them to install the OS.</p>
|
trying to use them to install the OS.</p>
|
||||||
|
<p>Releases are tested by the developers and are then pushed out via the Beta channel.
|
||||||
|
The release is then pushed out via the Stable channel after being tested by some users
|
||||||
|
using the Beta channel. In some cases, problems are caught during Beta channel testing
|
||||||
|
and a new release is made via the Beta channel to replace the aborted one. In general,
|
||||||
|
it's not possible to downgrade unless a downgrade update package is generated, so use
|
||||||
|
the Stable channel if you cannot tolerate dealing with temporary issues while a new
|
||||||
|
release for the Beta channel is being created.</p>
|
||||||
<h2>Stable channel</h2>
|
<h2>Stable channel</h2>
|
||||||
<div id="stable"></div>
|
<div id="stable"></div>
|
||||||
<h2>Beta channel</h2>
|
<h2>Beta channel</h2>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user