summaryrefslogtreecommitdiffstats
path: root/documentation/overview-manual/overview-manual-yp-intro.xml
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2018-04-24 09:19:25 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-05-24 17:16:25 +0100
commit59f84122aac79a8b873f384782018deacdbd0697 (patch)
treeaae4c9b567b457ae7c40daa2f26935b30a64a6e8 /documentation/overview-manual/overview-manual-yp-intro.xml
parent962cdcd77171bb88e673c4b50a77bf291060a942 (diff)
downloadpoky-59f84122aac79a8b873f384782018deacdbd0697.tar.gz
overview-manual: Added link to release cycle
The bullet "Releases According to a Strict Schedule" bullet mentions the release cycle. I added a link to that section. (From yocto-docs rev: c206c31d20aabe657863fc05274e2d533cdf7252) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/overview-manual/overview-manual-yp-intro.xml')
-rw-r--r--documentation/overview-manual/overview-manual-yp-intro.xml5
1 files changed, 3 insertions, 2 deletions
diff --git a/documentation/overview-manual/overview-manual-yp-intro.xml b/documentation/overview-manual/overview-manual-yp-intro.xml
index a28e8d66a9..bdf0a72ad5 100644
--- a/documentation/overview-manual/overview-manual-yp-intro.xml
+++ b/documentation/overview-manual/overview-manual-yp-intro.xml
@@ -161,8 +161,9 @@
161 </para></listitem> 161 </para></listitem>
162 <listitem><para> 162 <listitem><para>
163 <emphasis>Releases According to a Strict Schedule:</emphasis> 163 <emphasis>Releases According to a Strict Schedule:</emphasis>
164 Major releases occur on a six-month cycle predictably 164 Major releases occur on a
165 in October and April. 165 <ulink url='&YOCTO_DOCS_REF_URL;#ref-release-process'>six-month cycle</ulink>
166 predictably in October and April.
166 The most recent two releases support point releases 167 The most recent two releases support point releases
167 to address common vulnerabilities and exposures. 168 to address common vulnerabilities and exposures.
168 This predictability is crucial for projects based on 169 This predictability is crucial for projects based on