From patchwork Thu Jul 20 13:13:24 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Michael Opdenacker X-Patchwork-Id: 27751 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id EC7E3EB64DA for ; Thu, 20 Jul 2023 13:13:35 +0000 (UTC) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) by mx.groups.io with SMTP id smtpd.web11.12592.1689858811356190620 for ; Thu, 20 Jul 2023 06:13:32 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@bootlin.com header.s=gm1 header.b=dB0xgNrJ; spf=pass (domain: bootlin.com, ip: 217.70.183.195, mailfrom: michael.opdenacker@bootlin.com) Received: by mail.gandi.net (Postfix) with ESMTPSA id 8B73660018; Thu, 20 Jul 2023 13:13:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=gm1; t=1689858809; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=ONUHk5ZA2C4SIuZap8GieWCwSXmg+sRUEdptdf7h5mU=; b=dB0xgNrJ3uo7jlHiNB7BmqrpwBXwqln2y6NDVjLdBlb8YBx0kBOBNqn6R1WIj3iQO67sfp OzVxEYD6OTYUxg3PFhkKGpF+r2MqJpqpWJtCfZMjoUYjU1owzU4Na5n1WrrFDmgWqsBiLl DGQ/oUBZ67N03OTt3zKOaMEtJRcSbPl0MNS0I+5cxPJR2Y4xVBrfwJhMrBvJG3RdbmXlpA 2HrfO8gDujpgr52TOI208coxoTEJPnB34lYClNglZVSQ09Y3okn//yB6mPA0hLh5KDJ1g8 oDcdgi4D9MAc1l2pVxcVseeYgxx+mVkzUNY6IuaoXyMFBjzUKkoCpveRyY2E+w== From: michael.opdenacker@bootlin.com To: docs@lists.yoctoproject.org Cc: Michael Opdenacker Subject: [PATCH 1/2] [kirkstone] ref-manual: add LTS and Mixin terms Date: Thu, 20 Jul 2023 15:13:24 +0200 Message-Id: <20230720131325.336321-1-michael.opdenacker@bootlin.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 X-GND-Sasl: michael.opdenacker@bootlin.com List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Thu, 20 Jul 2023 13:13:35 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/docs/message/4073 From: Michael Opdenacker Signed-off-by: Michael Opdenacker --- documentation/ref-manual/terms.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/documentation/ref-manual/terms.rst b/documentation/ref-manual/terms.rst index d94fa4a5c9..ba13f77f19 100644 --- a/documentation/ref-manual/terms.rst +++ b/documentation/ref-manual/terms.rst @@ -211,6 +211,12 @@ universal, the list includes them just in case: Layers`" section in the Yocto Project Board Support Packages (BSP) Developer's Guide. + :term:`LTS` + This term means "Long Term Support", and in the context of the Yocto + Project, it corresponds to selected stable releases for which bug and + security fixes are provided for at least four years. See + the :ref:`ref-long-term-support-releases` section for details. + :term:`Metadata` A key element of the Yocto Project is the Metadata that is used to construct a Linux distribution and is contained in the @@ -230,6 +236,12 @@ universal, the list includes them just in case: :yocto_git:`yocto-kernel-cache ` Git repository. + :term:`Mixin` + A :term:`Mixin` layer is a layer which can be created by the community to + add a specific feature or support a new version of some package for an + :term:`LTS` release. See the :ref:`ref-long-term-support-releases` + section for details. + :term:`OpenEmbedded-Core (OE-Core)` OE-Core is metadata comprised of foundational recipes, classes, and associated files that are meant to From patchwork Thu Jul 20 13:13:25 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Michael Opdenacker X-Patchwork-Id: 27752 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 21CA3EB64DA for ; Thu, 20 Jul 2023 13:13:56 +0000 (UTC) Received: from relay9-d.mail.gandi.net (relay9-d.mail.gandi.net [217.70.183.199]) by mx.groups.io with SMTP id smtpd.web10.12605.1689858832251336285 for ; Thu, 20 Jul 2023 06:13:53 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@bootlin.com header.s=gm1 header.b=mYhTuFVw; spf=pass (domain: bootlin.com, ip: 217.70.183.199, mailfrom: michael.opdenacker@bootlin.com) Received: by mail.gandi.net (Postfix) with ESMTPSA id DC6A7FF810; Thu, 20 Jul 2023 13:13:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=gm1; t=1689858830; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=gJTGTPVYtYnrMQ6iF8EoznFpumIe3cQ+b/D0llRJCcg=; b=mYhTuFVwYMdAsC6Mydk4d4NRBVmgYcUSGYVrlOPsrCApG05G5kvgT0FfKAR0tPJXUaB2nq AUfUqhf3AKcjeuvkkVtRvc9Cr2brwGXW0odxgeUJO8ytUdFQdGyt9zQwY7EKo/q71asaw7 VCxqNvPy70JF8B8hgMOo98BKkf+9/nA2oRMGDpokkUVqgMgXgMwYUwZNkRe9vaTw0iijl4 lWojtqZyGRV0wl3TvscdNNS6nKIgQU1m+QdXFyEX6AW602CXWlOLuU+4rD6kBkAhk5zBn9 ERUG9kcejK2uyNC4RsschbzKiZ7wrx4zqDpXkXLmPBdSiJu3W891LFNJlTRa+w== From: michael.opdenacker@bootlin.com To: docs@lists.yoctoproject.org Cc: Michael Opdenacker Subject: [PATCH 2/2] [kirkstone] ref-manual: release-process: update for LTS releases Date: Thu, 20 Jul 2023 15:13:25 +0200 Message-Id: <20230720131325.336321-2-michael.opdenacker@bootlin.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20230720131325.336321-1-michael.opdenacker@bootlin.com> References: <20230720131325.336321-1-michael.opdenacker@bootlin.com> MIME-Version: 1.0 X-GND-Sasl: michael.opdenacker@bootlin.com List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Thu, 20 Jul 2023 13:13:56 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/docs/message/4074 From: Michael Opdenacker Signed-off-by: Michael Opdenacker --- documentation/ref-manual/release-process.rst | 78 +- documentation/ref-manual/svg/releases.svg | 1744 ++++++++++++++++++ 2 files changed, 1800 insertions(+), 22 deletions(-) create mode 100644 documentation/ref-manual/svg/releases.svg diff --git a/documentation/ref-manual/release-process.rst b/documentation/ref-manual/release-process.rst index 8acb4b8e09..d376d51bd2 100644 --- a/documentation/ref-manual/release-process.rst +++ b/documentation/ref-manual/release-process.rst @@ -18,9 +18,9 @@ Following are examples of some major YP releases with their codenames also shown. See the ":ref:`ref-manual/release-process:major release codenames`" section for information on codenames used with major releases. - - 2.2 (Morty) - - 2.1 (Krogoth) - - 2.0 (Jethro) + - 4.1 ("Langdale") + - 4.0 ("Kirkstone") + - 3.4 ("Honister") While the cadence is never perfect, this timescale facilitates regular releases that have strong QA cycles while not overwhelming users @@ -32,9 +32,9 @@ basis and are usually driven by the accumulation of enough significant fixes or enhancements to the associated major release. Following are some example past point releases: - - 2.1.1 - - 2.1.2 - - 2.2.1 + - 4.1.3 + - 4.0.8 + - 3.4.4 The point release indicates a point in the major release branch where a full QA cycle and @@ -87,15 +87,51 @@ stable release. exception to this policy occurs when there is a strong reason such as the fix happens to also be the preferred upstream approach. -Stable release branches have strong maintenance for about a year after -their initial release. Should significant issues be found for any -release regardless of its age, fixes could be backported to older -releases. For issues that are not backported given an older release, -Community LTS trees and branches allow community members to share -patches for older releases. However, these types of patches do not go -through the same release process as do point releases. You can find more -information about stable branch maintenance at -:yocto_wiki:`/Stable_branch_maintenance`. +.. _ref-long-term-support-releases: + +Long Term Support Releases +========================== + +While stable releases are supported for a duration of seven months, +some specific ones are now supported for a longer period by the Yocto +Project, and are called Long Term Support (:term:`LTS`) releases. + +When significant issues are found, :term:`LTS` releases allow to publish +fixes not only for the current stable release, but also to the +:term:`LTS` releases that are still supported. Older stable releases which +have reached their End of Life (EOL) won't receive such updates. + +This started with version 3.1 ("Dunfell"), released in April 2020, which +the project initially committed to supporting for two years, but this duration +was later extended to four years. Similarly, the following :term:`LTS` release, +version 4.0 ("Kirkstone"), was released two years later in May 2022 and the +project committed to supporting it for four years too. + +Therefore, a new :term:`LTS` release is made every two years and is supported +for four years. This offers more stability to project users and leaves more +time to upgrade to the following :term:`LTS` release. + +See :yocto_wiki:`/Stable_Release_and_LTS` for details about the management +of stable and :term:`LTS` releases. + +.. image:: svg/releases.* + :width: 100% + +.. note:: + + In some circumstances, a layer can be created by the community in order to + add a specific feature or support a new version of some package for an :term:`LTS` + release. This is called a :term:`Mixin` layer. These are thin and specific + purpose layers which can be stacked with an :term:`LTS` release to "mix" a specific + feature into that build. These are created on an as-needed basis and + maintained by the people who need them. + + Policies on testing these layers depend on how widespread their usage is and + determined on a case-by-case basis. You can find some :term:`Mixin` layers in the + :yocto_git:`meta-lts-mixins ` repository. While the Yocto + Project provides hosting for those repositories, it does not provides + testing on them. Other :term:`Mixin` layers may be released elsewhere by the wider + community. Testing and Quality Assurance ============================= @@ -155,14 +191,12 @@ effort has been made to automate the tests so that more people can use them and the Yocto Project development team can run them faster and more efficiently. -The Yocto Project's main Autobuilder (&YOCTO_AB_URL;) -publicly tests each Yocto Project release's code in the -:term:`OpenEmbedded-Core (OE-Core)`, Poky, and BitBake repositories. The testing -occurs for both the current state of the "master" branch and also for +The Yocto Project's main Autobuilder (&YOCTO_AB_URL;) publicly tests each Yocto +Project release's code in the :oe_git:`openembedded-core `, +:yocto_git:`poky ` and :oe_git:`bitbake ` repositories. The +testing occurs for both the current state of the "master" branch and also for submitted patches. Testing for submitted patches usually occurs in the -"ross/mut" branch in the ``poky-contrib`` repository (i.e. the -master-under-test branch) or in the "master-next" branch in the ``poky`` -repository. +in the "master-next" branch in the :yocto_git:`poky ` repository. .. note:: diff --git a/documentation/ref-manual/svg/releases.svg b/documentation/ref-manual/svg/releases.svg new file mode 100644 index 0000000000..e7d5c6d502 --- /dev/null +++ b/documentation/ref-manual/svg/releases.svg @@ -0,0 +1,1744 @@ + + + Yocto Project Release Timeline + + + + image/svg+xml + + + Yocto Project Release Timeline + + + The Yocto Project + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Dunfell (LTS)3.1 + + Gatesgarth3.2 + + + Honister3.4 + + Langdale4.1 + + Mickledore4.2 + + + Nanbield4.3 + + + Scarthgap4.4 + + Kirkstone (LTS)4.0 + Hardknott 3.3 + + + + + + + + + + + + + + + + + + + Oct.2023 + Oct.2024 + Oct.2025 + Support for this version was extended to leaveusers more time to adapt to override syntaxchanges in the 3.4 release. + Oct.2022 + Oct.2021 + Oct.2020 + Apr.2020 + Apr2022 + Apr.2024 + Apr.2025 + Apr.2026 + Apr.2023 + Apr.2021 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Oct.2026 + Oct.2027 + Apr.2027 + Apr.2028 + + + + + + + + + + + + + + + + + + + + + + + + + + + +