diff options
Diffstat (limited to 'documentation/ref-manual')
-rw-r--r-- | documentation/ref-manual/release-process.rst | 18 | ||||
-rw-r--r-- | documentation/ref-manual/terms.rst | 6 |
2 files changed, 15 insertions, 9 deletions
diff --git a/documentation/ref-manual/release-process.rst b/documentation/ref-manual/release-process.rst index 0b0b4b275a..170565f9bc 100644 --- a/documentation/ref-manual/release-process.rst +++ b/documentation/ref-manual/release-process.rst | |||
@@ -92,26 +92,26 @@ Long Term Support Releases | |||
92 | 92 | ||
93 | While stable releases are supported for a duration of seven months, | 93 | While stable releases are supported for a duration of seven months, |
94 | some specific ones are now supported for a longer period by the Yocto | 94 | some specific ones are now supported for a longer period by the Yocto |
95 | Project, and are called Long Term Support (LTS) releases. | 95 | Project, and are called Long Term Support (:term:`LTS`) releases. |
96 | 96 | ||
97 | This started with version 3.1 ("Dunfell"), released in April 2020, that | 97 | This started with version 3.1 ("Dunfell"), released in April 2020, that |
98 | the project committed to supporting until the next LTS release was out. | 98 | the project committed to supporting until the next :term:`LTS` release was out. |
99 | This next LTS release, version 4.0 ("Kirkstone"), was released in May 2022 | 99 | This next :term:`LTS` release, version 4.0 ("Kirkstone"), was released in May 2022 |
100 | and offered with two years of support too. | 100 | and offered with two years of support too. |
101 | 101 | ||
102 | However, as an experiment, support for "Dunfell" was extended to four years, until | 102 | However, as an experiment, support for "Dunfell" was extended to four years, until |
103 | April 2024, therefore offering more stability to projects and leaving more time | 103 | April 2024, therefore offering more stability to projects and leaving more time |
104 | to upgrade to the latest LTS release. The project hasn't made any commitment to | 104 | to upgrade to the latest :term:`LTS` release. The project hasn't made any commitment to |
105 | extending "Kirkstone" support too, as this will also depend on available funding | 105 | extending "Kirkstone" support too, as this will also depend on available funding |
106 | for such an effort. | 106 | for such an effort. |
107 | 107 | ||
108 | When significant issues are found, LTS releases allow to publish | 108 | When significant issues are found, :term:`LTS` releases allow to publish |
109 | fixes not only for the current stable release, but also to the | 109 | fixes not only for the current stable release, but also to the |
110 | LTS releases that are still supported. Older stable releases which | 110 | :term:`LTS` releases that are still supported. Older stable releases which |
111 | have reached their End of Life (EOL) won't receive such updates. | 111 | have reached their End of Life (EOL) won't receive such updates. |
112 | 112 | ||
113 | See :yocto_wiki:`/Stable_Release_and_LTS` for details about the management | 113 | See :yocto_wiki:`/Stable_Release_and_LTS` for details about the management |
114 | of stable and LTS releases. | 114 | of stable and :term:`LTS` releases. |
115 | 115 | ||
116 | .. image:: svg/releases.* | 116 | .. image:: svg/releases.* |
117 | :width: 100% | 117 | :width: 100% |
@@ -119,9 +119,9 @@ of stable and LTS releases. | |||
119 | .. note:: | 119 | .. note:: |
120 | 120 | ||
121 | In some circumstances, a layer can be created by the community in order to | 121 | In some circumstances, a layer can be created by the community in order to |
122 | add a specific feature or support a new version of some package for an LTS | 122 | add a specific feature or support a new version of some package for an :term:`LTS` |
123 | release. This is called a "mixin" layer. These are thin and specific | 123 | release. This is called a "mixin" layer. These are thin and specific |
124 | purpose layers which can be stacked with an LTS release to "mix" a specific | 124 | purpose layers which can be stacked with an :term:`LTS` release to "mix" a specific |
125 | feature into that build. These are created on an as-needed basis and | 125 | feature into that build. These are created on an as-needed basis and |
126 | maintained by the people who need them. | 126 | maintained by the people who need them. |
127 | 127 | ||
diff --git a/documentation/ref-manual/terms.rst b/documentation/ref-manual/terms.rst index ec447d35d2..5a7363acad 100644 --- a/documentation/ref-manual/terms.rst +++ b/documentation/ref-manual/terms.rst | |||
@@ -227,6 +227,12 @@ universal, the list includes them just in case: | |||
227 | Layers`" section in the Yocto Project Board Support Packages (BSP) | 227 | Layers`" section in the Yocto Project Board Support Packages (BSP) |
228 | Developer's Guide. | 228 | Developer's Guide. |
229 | 229 | ||
230 | :term:`LTS` | ||
231 | This term means "Long Term Support", and in the context of the Yocto | ||
232 | Project, it corresponds to selected stable releases for which bug and | ||
233 | security fixes are provided for at least two years. See | ||
234 | ":doc:`/ref-manual/release-process`" for details. | ||
235 | |||
230 | :term:`Metadata` | 236 | :term:`Metadata` |
231 | A key element of the Yocto Project is the Metadata that | 237 | A key element of the Yocto Project is the Metadata that |
232 | is used to construct a Linux distribution and is contained in the | 238 | is used to construct a Linux distribution and is contained in the |