@@ -697,8 +697,8 @@ backported to a stable branch unless the bug in question does not affect the
master branch or the fix on the master branch is unsuitable for backporting.
The list of stable branches along with the status and maintainer for each
-branch can be obtained from the
-:yocto_wiki:`Releases wiki page </Releases>`.
+branch can be obtained from the :yocto_home:`Releases </development/releases/>`
+page.
.. note::
@@ -123,10 +123,9 @@ Follow these general steps to create your layer without using tools:
Lists all layers on which this layer depends (if any).
- :term:`LAYERSERIES_COMPAT`:
- Lists the :yocto_wiki:`Yocto Project </Releases>`
- releases for which the current version is compatible. This
- variable is a good way to indicate if your particular layer is
- current.
+ Lists the :yocto_home:`Yocto Project releases </development/releases/>`
+ for which the current version is compatible. This variable is a good
+ way to indicate if your particular layer is current.
.. note::
@@ -16,7 +16,7 @@ document guides through this setup step-by-step.
Use Git to Clone The Layers
===========================
-Go to :yocto_wiki:`Releases wiki page </Releases>`, and choose a release
+Go to the :yocto_home:`Releases </development/releases/>` page, and choose a release
(such as ``&DISTRO_REL_LATEST_TAG;``), corresponding to either the latest stable
release or a Long Term Support release.
@@ -44,10 +44,10 @@ See the
documentation for details regarding the policies and maintenance of stable
branches.
-The :yocto_wiki:`Releases page </Releases>` contains a list
-of all releases of the Yocto Project. Versions in gray are no longer actively
-maintained with security patches, but well-tested patches may still be accepted
-for them for significant issues.
+The :yocto_home:`Releases </development/releases/>` page contains a list of all
+releases of the Yocto Project, grouped into current and previous releases.
+Previous releases are no longer actively maintained with security patches, but
+well-tested patches may still be accepted for them for significant issues.
Security-related discussions at the Yocto Project
-------------------------------------------------
@@ -661,7 +661,7 @@ described in the ":ref:`dev-manual/start:accessing source archives`" section.
.. note::
For a "map" of Yocto Project releases to version numbers, see the
- :yocto_wiki:`Releases </Releases>` wiki page.
+ :yocto_home:`Releases </development/releases/>` page.
You can use the "RELEASE ARCHIVE" link to reveal a menu of all Yocto
Project releases.
@@ -62,7 +62,8 @@ codename are likely to be compatible and thus work together.
Releases are given a nominal release version as well but the codename is
used in repositories for this reason. You can find information on Yocto
-Project releases and codenames at :yocto_wiki:`/Releases`.
+Project releases and codenames in the :yocto_home:`Releases page
+</development/releases/>`.
Our :doc:`/migration-guides/index` detail how to migrate from one release of
the Yocto Project to the next.
We have a machine-generated Releases page[1] which is preferable to the wiki. [1] https://www.yoctoproject.org/development/releases/ Signed-off-by: Ross Burton <ross.burton@arm.com> --- documentation/contributor-guide/submit-changes.rst | 4 ++-- documentation/dev-manual/layers.rst | 7 +++---- documentation/dev-manual/poky-manual-setup.rst | 2 +- documentation/dev-manual/security-subjects.rst | 8 ++++---- documentation/dev-manual/start.rst | 2 +- documentation/ref-manual/release-process.rst | 3 ++- 6 files changed, 13 insertions(+), 13 deletions(-)