diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2021-05-12 11:29:20 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-05-22 12:16:40 +0100 |
commit | 4db4e4ca46e8b23d5042d925ce5ad3073de4c3ed (patch) | |
tree | 6c0f58527ff6d5929ce0e948092357efb69fc659 /documentation/ref-manual/release-process.rst | |
parent | 68ee5b4bcc1098cb5a66098e65bec6c1cf69f4c2 (diff) | |
download | poky-4db4e4ca46e8b23d5042d925ce5ad3073de4c3ed.tar.gz |
ref-manual: simplify style
(From yocto-docs rev: 657a7f54856afd6fec7f2cb0b5f12b4b2d24adb7)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/release-process.rst')
-rw-r--r-- | documentation/ref-manual/release-process.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/ref-manual/release-process.rst b/documentation/ref-manual/release-process.rst index 93ab6ed08a..935a2e39bb 100644 --- a/documentation/ref-manual/release-process.rst +++ b/documentation/ref-manual/release-process.rst | |||
@@ -82,14 +82,14 @@ stable release. | |||
82 | bug fixes and security fixes only. Policy dictates that features are | 82 | bug fixes and security fixes only. Policy dictates that features are |
83 | not backported to a stable release. This policy means generic recipe | 83 | not backported to a stable release. This policy means generic recipe |
84 | version upgrades are unlikely to be accepted for backporting. The | 84 | version upgrades are unlikely to be accepted for backporting. The |
85 | exception to this policy occurs when a strong reason exists such as | 85 | exception to this policy occurs when there is a strong reason such as |
86 | the fix happens to also be the preferred upstream approach. | 86 | the fix happens to also be the preferred upstream approach. |
87 | 87 | ||
88 | Stable release branches have strong maintenance for about a year after | 88 | Stable release branches have strong maintenance for about a year after |
89 | their initial release. Should significant issues be found for any | 89 | their initial release. Should significant issues be found for any |
90 | release regardless of its age, fixes could be backported to older | 90 | release regardless of its age, fixes could be backported to older |
91 | releases. For issues that are not backported given an older release, | 91 | releases. For issues that are not backported given an older release, |
92 | Community LTS trees and branches exist where community members share | 92 | Community LTS trees and branches allow community members to share |
93 | patches for older releases. However, these types of patches do not go | 93 | patches for older releases. However, these types of patches do not go |
94 | through the same release process as do point releases. You can find more | 94 | through the same release process as do point releases. You can find more |
95 | information about stable branch maintenance at | 95 | information about stable branch maintenance at |