| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | releases.md | 3 …ifetime of seven months to allow for migration, while "long term support" (LTS) releases are picke…
8 …new hardware enablement (and relevant software features) to be included in LTS named branches (not…
12 …uded in an LTS named branch, the preferred process is to upstream via the master branch, rebase th…
14 …d the preferred way above cannot be completed in time, upstreaming via the LTS branch can occur. T…
20 Named branches for meta-arm will be released as close as possible to the release of the YP LTS rele…
22 …he most recent Long Term Stable (LTS) as the named branch. All previous named LTS branches will be…
24 Named branch release will coincide with Yocto Project releases. These non-LTS branches will be bug …
40 …ses as possible. Similarily, it is recommended the BSP releases be based on the latest LTS branch.
|
| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | release-process.rst | 97 Project, and are called Long Term Support (:term:`LTS`) releases.
99 When significant issues are found, :term:`LTS` releases allow to publish
101 :term:`LTS` releases that are still supported. Older stable releases which
108 A new :term:`LTS` release is made every two years and is supported for four
110 upgrade to the following :term:`LTS` release.
112 The currently supported :term:`LTS` releases are:
118 of stable and :term:`LTS` releases.
128 add a specific feature or support a new version of some package for an :term:`LTS`
130 purpose layers which can be stacked with an :term:`LTS` release to "mix" a specific
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | xfs-maintainer-entry-profile.rst | 95 - **LTS Maintainer**: Someone who backports and tests bug fixes from
96 uptream to the LTS kernels.
97 There tend to be six separate LTS trees at any given time.
99 The maintainer for a given LTS release should identify themselves with an
100 ``M:`` entry in the MAINTAINERS file for that LTS tree.
101 Unmaintained LTS kernels should be marked with status ``S: Orphan`` in that
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | sun50i-a64-pine64-lts.dts | 10 model = "Pine64 LTS";
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-django_4.2.16.bb | 11 # Set DEFAULT_PREFERENCE so that the LTS version of django is built by
|
| /openbmc/linux/arch/arm64/boot/dts/allwinner/ |
| H A D | sun50i-a64-pine64-lts.dts | 8 model = "Pine64 LTS";
|
| /openbmc/linux/arch/arm64/boot/dts/rockchip/ |
| H A D | rk3328-orangepi-r1-plus-lts.dts | 13 model = "Xunlong Orange Pi R1 Plus LTS";
|
| /openbmc/openbmc/meta-openembedded/meta-filesystems/ |
| H A D | SECURITY.md | 20 releases. We only accept patches for the LTS releases and the master branch.
|
| /openbmc/openbmc/meta-openembedded/meta-webserver/ |
| H A D | SECURITY.md | 20 releases. We only accept patches for the LTS releases and the master branch.
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/ |
| H A D | SECURITY.md | 20 releases. We only accept patches for the LTS releases and the master branch.
|
| /openbmc/openbmc/meta-openembedded/meta-python/ |
| H A D | SECURITY.md | 20 releases. We only accept patches for the LTS releases and the master branch.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/ |
| H A D | SECURITY.md | 20 releases. We only accept patches for the LTS releases and the master branch.
|
| /openbmc/openbmc/meta-openembedded/meta-initramfs/ |
| H A D | SECURITY.md | 20 releases. We only accept patches for the LTS releases and the master branch.
|
| /openbmc/openbmc/meta-openembedded/meta-perl/ |
| H A D | SECURITY.md | 20 releases. We only accept patches for the LTS releases and the master branch.
|
| /openbmc/openbmc/meta-openembedded/meta-networking/ |
| H A D | SECURITY.md | 20 releases. We only accept patches for the LTS releases and the master branch.
|
| /openbmc/openbmc/meta-openembedded/meta-xfce/ |
| H A D | SECURITY.md | 20 releases. We only accept patches for the LTS releases and the master branch.
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/ |
| H A D | SECURITY.md | 20 releases. We only accept patches for the LTS releases and the master branch.
|
| /openbmc/openbmc/meta-raspberrypi/ |
| H A D | SECURITY.md | 20 releases. We only accept patches for the LTS releases and the master branch.
|
| /openbmc/openbmc/poky/ |
| H A D | SECURITY.md | 16 See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]
|
| /openbmc/openbmc/poky/bitbake/ |
| H A D | SECURITY.md | 18 See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]
|
| /openbmc/openbmc/meta-arm/ |
| H A D | README.md | 73 …mit message. This is similar to how the Linux kernel community does their LTS kernel backporting.…
78 We follow the Yocto Project release methodology, schedule, and stable/LTS support timelines. For m…
|
| /openbmc/linux/arch/x86/include/asm/ |
| H A D | io_apic.h | 23 LTS : 1, member
|
| /openbmc/qemu/ |
| H A D | pythondeps.toml | 32 # Prefer an LTS version when updating the accepted versions of
|
| /openbmc/docs/development/ |
| H A D | dev-environment.md | 33 The recommended OpenBMC development environment is the latest Ubuntu LTS
56 2. Install the latest Ubuntu LTS release
59 built on the latest Ubuntu LTS release but whatever is most recent _should_
|
| /openbmc/openbmc/poky/bitbake/doc/ |
| H A D | README | 40 old versions, especially if you are using an LTS version of your
|