summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/ref-release-process.rst
diff options
context:
space:
mode:
authorNicolas Dechesne <nicolas.dechesne@linaro.org>2020-12-03 22:38:38 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-12-09 12:21:27 +0000
commitaf6f5d821d39b50c3c4b45a593324346fce0d723 (patch)
tree872369e16adfff81fc49b7e8f550cae8905916b7 /documentation/ref-manual/ref-release-process.rst
parentc684a7a6d50754d577e0ff68a6fb6ed493b8f93e (diff)
downloadpoky-af6f5d821d39b50c3c4b45a593324346fce0d723.tar.gz
dev-manual: remove 'dev-manual' from filenames
All filenames duplicate the 'manual name', which is not needed, and make all references longer than they should. Rename all files to be as consise as possible, and fix all references (From yocto-docs rev: 00a9244587e2e63f2a5197ed0dfc89cb330f9275) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/ref-release-process.rst')
-rw-r--r--documentation/ref-manual/ref-release-process.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/ref-manual/ref-release-process.rst b/documentation/ref-manual/ref-release-process.rst
index ec6d233877..54cd9510f6 100644
--- a/documentation/ref-manual/ref-release-process.rst
+++ b/documentation/ref-manual/ref-release-process.rst
@@ -106,7 +106,7 @@ Additionally, because the test strategies are visible to you as a
106developer, you can validate your projects. This section overviews the 106developer, you can validate your projects. This section overviews the
107available test infrastructure used in the Yocto Project. For information 107available test infrastructure used in the Yocto Project. For information
108on how to run available tests on your projects, see the 108on how to run available tests on your projects, see the
109":ref:`dev-manual/dev-manual-common-tasks:performing automated runtime testing`" 109":ref:`dev-manual/common-tasks:performing automated runtime testing`"
110section in the Yocto Project Development Tasks Manual. 110section in the Yocto Project Development Tasks Manual.
111 111
112The QA/testing infrastructure is woven into the project to the point 112The QA/testing infrastructure is woven into the project to the point
@@ -128,12 +128,12 @@ consists of the following pieces:
128 128
129- :ref:`testimage.bbclass <ref-classes-testimage*>`: This class 129- :ref:`testimage.bbclass <ref-classes-testimage*>`: This class
130 performs runtime testing of images after they are built. The tests 130 performs runtime testing of images after they are built. The tests
131 are usually used with :doc:`QEMU </dev-manual/dev-manual-qemu>` 131 are usually used with :doc:`QEMU </dev-manual/qemu>`
132 to boot the images and check the combined runtime result boot 132 to boot the images and check the combined runtime result boot
133 operation and functions. However, the test can also use the IP 133 operation and functions. However, the test can also use the IP
134 address of a machine to test. 134 address of a machine to test.
135 135
136- :ref:`ptest <dev-manual/dev-manual-common-tasks:testing packages with ptest>`: 136- :ref:`ptest <dev-manual/common-tasks:testing packages with ptest>`:
137 Runs tests against packages produced during the build for a given 137 Runs tests against packages produced during the build for a given
138 piece of software. The test allows the packages to be be run within a 138 piece of software. The test allows the packages to be be run within a
139 target image. 139 target image.