| /openbmc/qemu/docs/devel/ |
| H A D | stable-process.rst | 3 QEMU and the stable process
6 QEMU stable releases
9 QEMU stable releases are based upon the last released QEMU version
14 Usually, stable releases are only provided for the last major QEMU
16 stable releases are produced only until QEMU 2.12.0 is released, at
17 which point the stable process moves to producing 2.12.x/2.12.x.y releases.
19 What should go into a stable release?
22 Generally, the following patches are considered stable material:
30 for stable.
33 How to get a patch into QEMU stable
[all …]
|
| H A D | rust.rst | 81 * inline const expression (stable in 1.79.0), currently worked around with
87 * ``&raw`` (stable in 1.82.0). Use ``addr_of!`` and ``addr_of_mut!`` instead,
90 * ``new_uninit`` (stable in 1.82.0). This is used internally by the ``pinned_init``
94 * referencing statics in constants (stable in 1.83.0). For now use a const
144 - *stable*: ready for production use, the API is safe and should not undergo
158 ``assertions`` stable
161 ``cell`` stable
163 ``error`` stable
166 ``memory`` stable
168 ``qdev`` stable
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-kernel/linux/ |
| H A D | cve-exclusion_6.12.inc | 2337 CVE_STATUS[CVE-2022-49034] = "cpe-stable-backport: Backported in 6.12.2"
5073 CVE_STATUS[CVE-2023-53034] = "cpe-stable-backport: Backported in 6.12.23"
6833 CVE_STATUS[CVE-2024-36476] = "cpe-stable-backport: Backported in 6.12.9"
7281 CVE_STATUS[CVE-2024-39282] = "cpe-stable-backport: Backported in 6.12.9"
7789 CVE_STATUS[CVE-2024-41932] = "cpe-stable-backport: Backported in 6.12.5"
7791 CVE_STATUS[CVE-2024-41935] = "cpe-stable-backport: Backported in 6.12.5"
8185 CVE_STATUS[CVE-2024-43098] = "cpe-stable-backport: Backported in 6.12.5"
8579 CVE_STATUS[CVE-2024-45828] = "cpe-stable-backport: Backported in 6.12.5"
8975 CVE_STATUS[CVE-2024-47141] = "cpe-stable-backport: Backported in 6.12.5"
8977 CVE_STATUS[CVE-2024-47143] = "cpe-stable-backport: Backported in 6.12.5"
[all …]
|
| H A D | cve-exclusion.inc | 146 # Fix https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f98364e926626c678…
149 # Fix https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=567320c46a60a3c39…
152 #Fix https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=65c95f78917ea6fa7f…
155 #Fix https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ad25ee36f00172f7d5…
158 #Fix https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7315dc1e122c85ffdf…
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/minifi-cpp/files/ |
| H A D | 0007-libsodium-aarch64-set-compiler-attributes-after-including-arm_.patch | 14 thirdparty/libsodium-stable/configure.ac | 11 ++++++-----
20 diff --git a/thirdparty/libsodium-stable/configure.ac b/thirdparty/libsodium-stable/configure.ac
22 --- a/thirdparty/libsodium-stable/configure.ac
23 +++ b/thirdparty/libsodium-stable/configure.ac
49 …--git a/thirdparty/libsodium-stable/src/libsodium/crypto_aead/aegis128l/aegis128l_armcrypto.c b/th…
51 --- a/thirdparty/libsodium-stable/src/libsodium/crypto_aead/aegis128l/aegis128l_armcrypto.c
52 +++ b/thirdparty/libsodium-stable/src/libsodium/crypto_aead/aegis128l/aegis128l_armcrypto.c
79 … --git a/thirdparty/libsodium-stable/src/libsodium/crypto_aead/aegis256/aegis256_armcrypto.c b/thi…
81 --- a/thirdparty/libsodium-stable/src/libsodium/crypto_aead/aegis256/aegis256_armcrypto.c
82 +++ b/thirdparty/libsodium-stable/src/libsodium/crypto_aead/aegis256/aegis256_armcrypto.c
[all …]
|
| /openbmc/libpldm/scripts/ |
| H A D | pre-submit | 31 # -Dabi=deprecated,stable,testing.
45 # Ensure that the test suite doesn't fail to link against the stable ABI, and
46 # the stable ABI matches what's recorded
48 meson configure -Dabi=deprecated,stable "$BUILD"
56 meson configure -Dabi=stable,testing "$BUILD"
|
| H A D | run-ci | 31 # -Dabi=deprecated,stable,testing.
45 # Ensure that the test suite doesn't fail to link against the stable ABI, and
46 # the stable ABI matches what's recorded
48 meson configure -Dabi=deprecated,stable "$BUILD"
56 meson configure -Dabi=stable,testing "$BUILD"
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/xmlrpc-c/xmlrpc-c/ |
| H A D | 0001-fix-bool-reserved-word-error-in-gcc-15.patch | 31 stable/lib/util/include/bool.h | 2 ++
34 diff --git a/stable/lib/util/include/bool.h b/stable/lib/util/include/bool.h
36 --- a/stable/lib/util/include/bool.h
37 +++ b/stable/lib/util/include/bool.h
|
| H A D | no-automake.patch | 6 diff --git i/stable/configure.in w/stable/configure.in
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | release-process.rst | 4 Yocto Project Releases and the Stable Release Process
45 Realize that there can be patches merged onto the stable release
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.
79 stable release.
85 not backported to a stable release. This policy means generic recipe
95 While stable releases are supported for a duration of seven months,
100 fixes not only for the current stable release, but also to the
101 :term:`LTS` releases that are still supported. Older stable releases which
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-devtools/log4cplus/ |
| H A D | log4cplus_2.1.2.bb | 10 SRC_URI = "${SOURCEFORGE_MIRROR}/project/${BPN}/${BPN}-stable/${PV}/${BP}.tar.gz \
14 UPSTREAM_CHECK_URI = "https://sourceforge.net/projects/log4cplus/files/log4cplus-stable/"
15 UPSTREAM_CHECK_REGEX = "log4cplus-stable/(?P<pver>\d+(\.\d+)+)/"
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/libpldm/ |
| H A D | libpldm_git.bb | 8 LIBPLDM_ABI_DEVELOPMENT = "deprecated,stable,testing"
9 LIBPLDM_ABI_MAINTENANCE = "stable,testing"
10 LIBPLDM_ABI_PRODUCTION = "deprecated,stable"
|
| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | releases.md | 3 The Yocto Project releases twice a year (April and October): "stable" releases are made every six m…
5 …stable”, and only take bug fixes or security-critical upgrades. Active development occurs on the m…
8 …stable software platform for software to be developed, tested, and released. Also, the single bran…
22 …lopment branches at any given time: master and the most recent Long Term Stable (LTS) as the named…
|
| /openbmc/openbmc/poky/meta/recipes-support/libevent/ |
| H A D | libevent_2.1.12.bb | 14 SRC_URI = "${GITHUB_BASE_URI}/download/release-${PV}-stable/${BP}-stable.tar.gz \
24 UPSTREAM_CHECK_REGEX = "releases/tag/release-(?P<pver>.+)-stable"
26 S = "${WORKDIR}/${BPN}-${PV}-stable"
|
| /openbmc/libpldm/docs/checklists/ |
| H A D | changes.md | 133 Testing --> Stable: Stabilise
134 Stable --> Deprecated: Deprecate
144 | Production | `-Dabi=deprecated,stable` |
145 | Maintenance | `-Dabi=stable` |
146 | Development | `-Dabi=deprecated,stable,testing` |
151 off of deprecated APIs by constraining the library ABI to the stable category.
169 stable.
171 ### Marking functions as testing, stable or deprecated
174 translation units) to mark functions as testing, stable or deprecated:
193 ### What does it mean to mark a function as stable
[all...] |
| /openbmc/libpldm/ |
| H A D | CONTRIBUTING.md | 133 Testing --> Stable: Stabilise
134 Stable --> Deprecated: Deprecate
144 | Production | `-Dabi=deprecated,stable` |
145 | Maintenance | `-Dabi=stable` |
146 | Development | `-Dabi=deprecated,stable,testing` |
151 off of deprecated APIs by constraining the library ABI to the stable category.
169 stable.
171 ### Marking functions as testing, stable or deprecated
174 translation units) to mark functions as testing, stable or deprecated:
193 ### What does it mean to mark a function as stable?
[all …]
|
| H A D | meson.options | 5 choices: ['deprecated', 'stable', 'testing'],
6 value: ['deprecated', 'stable', 'testing'],
|
| /openbmc/qemu/ |
| H A D | .readthedocs.yml | 3 # See https://docs.readthedocs.io/en/stable/config-file/v2.html for details
19 # https://docs.readthedocs.io/en/stable/guides/reproducible-builds.html
|
| /openbmc/openbmc/poky/meta/recipes-support/libevent/libevent/ |
| H A D | Makefile-missing-test-dir.patch | 16 diff --git a/libevent-2.1.8-stable/test/include.am b/libevent-2.1.8-stable/test/include.am
|
| /openbmc/libpldm/src/ |
| H A D | api.h | 13 * Existing stable APIs often return errors in the form of PLDM completion
16 * implementation errors. However, for existing stable APIs, provide a means to
|
| /openbmc/openbmc/poky/bitbake/ |
| H A D | SECURITY.md | 18 See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]
19 for detailed info regarding the policies and maintenance of Stable branches.
|
| /openbmc/openbmc/poky/ |
| H A D | SECURITY.md | 16 See [Stable release and LTS](https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS)
17 for detailed info regarding the policies and maintenance of Stable branches.
|
| /openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/sshfs-fuse/sshfs-fuse/ |
| H A D | 03ee1f8aa0899268ec02b2f54849352df92a3a1d.patch | 11 …r custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/mark.html
18 1. https://docs.pytest.org/en/stable/mark.html
|
| /openbmc/openbmc-test-automation/extended/ |
| H A D | standby_bmc.robot | 3 ... to bring the BMC to a stable, standby state. For our
4 ... purposes, a stable state is defined as:
36 Get To Stable State
37 [Documentation] BMC cleanup drive to stable state
|
| /openbmc/openbmc/meta-arm/ |
| H A D | SECURITY.md | 30 [Stable release and LTS](https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS)
31 for detailed info regarding the policies and maintenance of stable
|