Lines Matching full:release

4 Yocto Project Releases and the Stable Release Process
7 The Yocto Project release process is predictable and consists of both
12 Major and Minor Release Cadence
18 also shown. See the ":ref:`ref-manual/release-process:major release codenames`"
32 fixes or enhancements to the associated major release. Following are
39 The point release
40 indicates a point in the major release branch where a full QA cycle and
41 release process validates the content of the new branch.
45    Realize that there can be patches merged onto the stable release
48 Major Release Codenames
51 Each major release receives a codename that identifies the release in
59    release number (e.g. &DISTRO;) could conflict with a given layer or
63 Releases are given a nominal release version as well but the codename is
67 Our :doc:`/migration-guides/index` detail how to migrate from one release of
70 Stable Release Process
73 Once released, the release enters the stable release process at which
74 time a person is assigned as the maintainer for that stable release.
75 This maintainer monitors activity for the release by investigating and
79 stable release.
85    not backported to a stable release. This policy means generic recipe
90 Stable release branches have strong maintenance for about a year after
91 their initial release. Should significant issues be found for any
92 release regardless of its age, fixes could be backported to older
93 releases. For issues that are not backported given an older release,
96 through the same release process as do point releases. You can find more
103 Part of the Yocto Project development and release process is quality
105 provide the Yocto Project team a way to ensure a release is validated.
159 publicly tests each Yocto Project release's code in the
179 process of a release. Complete testing and validation for a release