Yocto Project - User contributions [en]

Yocto Project Release Checklist

2026-09-23T16:13:34Z

Rpurdie:

Major Release

* Week prior to build of release candidate
** Updates to the following packages will have occurred. DO NO PANIC, these come late in the release cycle
*** wic
*** meta-yocto-bsp
*** meta-yocto
*** linux-firmware
*** bootloaders (grub, syslinux, u-boot, gummiboot, etc..)
*** hwdata
*** pciutils
*** util-linux
*** i2c-tools
*** alsa
*** graphics drivers
*** cryptodev
*** systemtap
*** perf
*** linux-yocto

* Prior to build of the first release candidate
** Does LAYERSERIES_CORENAMES in layer.conf in OE-Core contain the current release name with the previous release removed?
** Is DISTRO_VERSION updated in poky.conf? (e.g. https://git.yoctoproject.org/meta-yocto/commit/?h=wrynose&id=904846ae078ee20de073040ebb77c86e19250f56)
** Is SANITY_TESTED_DISTROS updated in poky.conf? (e.g. see above)
** Is bitbake version updated? (e.g. https://git.openembedded.org/bitbake/commit/?h=2.18&id=33581c84f3a85008239acbd940501a35de48dc91)
** Are yocto-docs merged to the release branch?
** Has bitbake -f -c distrodata universe been run?
** Add a new bitbake-setup configuration file in BitBake's registry (create a new one, do not delete old ones, e.g. https://lore.kernel.org/bitbake-devel/20260422095624.241708-1-richard.purdie@linuxfoundation.org/T/)
** Add branch selectors and scheduled jobs to autobuilder configuration (e.g. https://lore.kernel.org/yocto-patches/20260423214412.2387367-2-richard.purdie@linuxfoundation.org/T/)
** Update Toaster fixtures files
** Update SRCREVs in build-appliance-image (e.g. https://git.openembedded.org/openembedded-core/commit/?h=wrynose&id=42fa856a00ac16b2a7a83d7ecfa60a5be192b16c)

* After the final release candidate has returned from QA and is approved, verify the following:
** BSP tarballs have been generated.
** Release Notes have been created, finalized, and approved.
** Release Notes have been signed.
** Repos have been tagged with correct commit and signature.
** The README for each BSP has been checked and updated if necessary.
** Artifacts correctly moved to https://downloads.yoctoproject.org/releases/yocto/.
** The kernel.org mirror sync has been triggered and completed successfully.
** The release announcement has been sent to the appropriate mailing lists. (yocto and yocto-announce)
** docs.yoctoproject.org updated correct dropdown version.
** Files to update in yocto-docs:
*** Create new release note templates in documentation/migration-guides/ (e.g. https://lore.kernel.org/yocto-docs/20251218-release-notes-templates-6-0-v1-1-61690583cef2@bootlin.com/)
*** Update documentation/ref-manual/svg/releases.svg (e.g. https://lore.kernel.org/yocto-docs/20251204-release-updates-v2-2-04ca6c26ddd5@bootlin.com/)
** Files to update in yocto-autobuilder2:
*** update workers_prev_releases in config.py (e.g. https://lore.kernel.org/yocto-patches/20251217-add-whinlatter-to-config-v1-1-9aeb42d212bd@bootlin.com/)
** Files to update in yocto-autobuilder-helper:
*** Update scripts/release-parser.py
** Files to update in yocto-metrics:
*** Update patch-status/releases.csv

Releases

2026-09-10T14:27:48Z

Rpurdie:

Note that https://www.yoctoproject.org/development/releases/ is the preferred source of information.

This page remains as it currently contains more information.

See [[Release calendar]] for upcoming release dates.

== Release Activity==

See also [https://docs.yoctoproject.org/dev/_images/releases.svg a graphical release timeline].

Releases can be downloaded at https://www.yoctoproject.org/software-overview/downloads/

{| class="wikitable" border="2"
!Codename
!Yocto Project Version
!Release Date
!Current Version
!Support Level
!Poky Version
!BitBake branch
! Maintainer
!Notes
|-
|Garburn
|6.2
| April 2027
|
|Support for 6 months (until October 2027)
|N/A
|2.22
|Richard Purdie <richard.purdie@linuxfoundation.org>
|
|-
|Blacksail
|6.1
| October 2026
|
|Support for 6 months (until April 2027)
|N/A
|2.20
|Richard Purdie <richard.purdie@linuxfoundation.org>
|
|-
|Wrynose (like 'rhinos')
|6.0
| April 2026
|6.0 (May 2026)
|Long Term Support (until April 2030)
|N/A
|2.18
|Yoann Congal <yoann.congal@smile.fr>
|
|-style="color: slategray;"
|Whinlatter (like 'win latter')
|5.3
| December 2025
|5.3.2 (March 2026)
|EOL
|N/A
|2.16
|Yoann Congal <yoann.congal@smile.fr>
|[[Recipe_Versions|Recipe versions]]
|-
|-style="color: slategray;"
|Walnascar (aka Walna)
|5.2
| May 2025
|5.2.4 (October 2025)
|EOL since November 2025
|N/A
|2.12
|Steve Sakoman <steve@sakoman.com>
|[[Recipe_Versions|Recipe versions]]
|-
|-style="color: slategray;"
|Styhead (like 'try head')
|5.1
| October 2024
|5.1.4 (April 2025)
|EOL
|N/A
|2.10
|Steve Sakoman <steve@sakoman.com>
|
|-
|Scarthgap
|5.0
| April 2024
| 5.0.18 (June 2026)
|Long Term Support (until April 2028)
|N/A
|2.8
|Yoann Congal <yoann.congal@smile.fr>
|[[Recipe_Versions|Recipe versions]]
|-
|-style="color: slategray;"
|Nanbield (like 'man field')
|4.3
| November 2023
| 4.3.4 (April 2024)
| EOL
|N/A
|2.6
|Steve Sakoman <steve@sakoman.com>
|- style="color: slategray;"
|Mickledore
|4.2
| May 2023
| 4.2.4 (December 2023)
| EOL
|N/A
|2.4
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Langdale
|4.1
| October 2022
| 4.1.4 (May 2023)
| EOL
|N/A
|2.2
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Kirkstone (like 'kirk stun')
|4.0
|May 2022
|4.0.33 (February 2026)
|EOL
|N/A
|2.0
|Yoann Congal <yoann.congal@smile.fr>
|-
|-style="color: slategray;"
|Honister
|3.4
|October 2021
|3.4.4 (May 2022)
|EOL
|N/A
|1.52
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Hardknott
|3.3
|April 2021
|3.3.6 (April 2022)
|EOL
|N/A
|1.50
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Gatesgarth
|3.2
|Oct 2020
|3.2.4 (May 2021)
|EOL
|N/A
|1.48
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Dunfell
|3.1
|April 2020
|3.1.33 (May 2024)
| EOL - LTS¹
|23.0
|1.46
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Zeus
|3.0
|October 2019
|3.0.4 (August 2020)
|EOL
|22.0.3
|1.44
| Anuj/Armin
|-style="color: slategray;"
|Warrior
|2.7
|April 2019
|2.7.4 (June 2020)
|EOL
|21.0
|1.42
|Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Thud
|2.6
|Nov 2018
|2.6.4 (October 2019)
|EOL
|20.0
|1.40
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Sumo
|2.5
|April 2018
|2.5.3 (April 2019)
|EOL
|19.0
|1.38
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Rocko
|2.4
|Oct 2017
|2.4.4 (November 2018)
|EOL
|18.0
|1.36
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Pyro
|2.3
|May 2017
|2.3.4 (July 2018)
|EOL
|17.0
|1.34
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Morty
|2.2
|Nov 2016
|2.2.4 (July 2018)
|EOL
|16.0
|1.32
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Krogoth
|2.1
|Apr 2016
|2.1.3 (July 2017)
|EOL
|15.0
|1.30
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Jethro
|2.0
|Nov 2015
|2.0.3 (January 2017)
|EOL
|14.0
|1.28
|Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Fido
|1.8
|Apr 2015
|1.8.2
|EOL
|13.0
|1.26
|Joshua Lock <joshua.g.lock@intel.com>
|-style="color: slategray;"
|Dizzy
|1.7
|Oct 2014
|1.7.3
|EOL
|12.0
|1.24
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Daisy
|1.6
|Apr 2014
|1.6.3
|EOL
|11.0
|1.22
| Saul Wold <sgw@linux.intel.com>
|-style="color: slategray;"
|Dora
|1.5
|Oct 2013
|1.5.4
|EOL
|10.0
|1.20
| Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Dylan
|1.4
|Apr 2013
|1.4.3
|EOL
|9.0
|1.18
| Paul Eggleton <paul.eggleton@linux.intel.com>
|-style="color: slategray;"
|Danny
|1.3
|Oct 2012
|1.3.2
|EOL
|8.0
|1.16
|Ross Burton <ross.burton@intel.com>
|-style="color: slategray;"
|Denzil
|1.2
|Apr 2012
|1.2.2
|EOL
|7.0
|1.15
|-style="color: slategray;"
|Edison
|1.1
|Oct 2011
|1.1.2
|EOL
|6.0
|1.13
|-style="color: slategray;"
|Bernard
|1.0
|Apr 2011
|1.0.2
|EOL
|5.0
|1.11
|-style="color: slategray;"
|Laverne
|0.9
|Oct 2010
|
|
|4.0
|1.11
|-style="color: slategray;"
|Green
|N/A
|11 June 2010
|
|
|3.3
|
|-style="color: slategray;"
|Purple
|N/A
|15 Dec 2009
|
|
|3.2
|
|-style="color: slategray;"
|Pinky
|N/A
|12 Nov 2009
|
|
|3.1
|
|-style="color: slategray;"
|Blinky
|N/A
|1 Aug 2007
|
|
|3.0
|
|-style="color: slategray;"
|Clyde
|N/A
|19 Jan 2007
|
|
|2.0
|
|-style="color: slategray;"
|Inky
|N/A
|10 Feb 2006
|
|
|1.0
|
|}

'''Note:''' see also [[Stable Release and LTS]], [[Linux Yocto]], [[Release calendar]] and [[Release Feature Table]] pages. EOL means some community support on email lists but no commit updates in the repos. There is also OS Vendor support for some Yocto EOL releases.

¹ The 3.1 series and 4.0 were originally planned for two years but extended to four. Future LTS releases are planned for 4 years.

== Releases Links==
{| class="wikitable" border="2"
| align="center" style="background:#f0f0f0;"|'''Yocto Project Release'''
| align="center" style="background:#f0f0f0;"|'''Code Name'''
| align="center" style="background:#f0f0f0;"|'''Poky version'''
| align="center" style="background:#f0f0f0;"|'''Maintainer'''
| align="center" style="background:#f0f0f0;"|'''Features'''
| align="center" style="background:#f0f0f0;"|'''Schedule'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''QA Test Plan'''
| align="center" style="background:#f0f0f0;"|'''QA Test Report'''
| align="center" style="background:#f0f0f0;"|'''Release notes'''

|-valign="top"
| Yocto Project 3.4
| Honister
| 26.0
| Anuj Mittal
| [[Yocto_3.4_Features]]
| [[Yocto_3.4_Schedule]]
| [[Yocto_Project_v3.4_Status]]
| [[Yocto_Project_3.4_Release_Test_Plan | Yocto_3.4_Overall_Test_Plan]]
| [[Yocto_Project_3.4_Release_Test_Plan#Execution_History | 3.4 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/229 3.4 release notes]
|-
| Yocto Project 3.3
| Hardknott
| 25.0
| Anuj Mittal
| [[Yocto_3.3_Features]]
| [[Yocto_3.3_Schedule]]
| [[Yocto_Project_v3.3_Status]]
| [[Yocto_Project_3.3_Release_Test_Plan | Yocto_3.3_Overall_Test_Plan]]
| [[Yocto_Project_3.3_Release_Test_Plan#Execution_History | 3.3 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/215 3.3 release notes]
|-
| Yocto Project 3.2
| Gatesgarth
| 24.0
| Anuj Mittal
| [[Yocto_3.2_Features]]
| [[Yocto_3.2_Schedule]]
| [[Yocto_Project_v3.2_Status]]
| [[Yocto_Project_3.2_Release_Test_Plan | Yocto_3.2_Overall_Test_Plan]]
| [[Yocto_Project_3.2_Release_Test_Plan#Execution_History | 3.2 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/51262 3.2 release notes]
|-
|-valign="top"
| Yocto Project 3.1
| Dunfell
| 23.0
| Steve Sakoman
| [[Yocto_3.1_Features]]
| [[Yocto_3.1_Schedule]]
| [[Yocto_Project_v3.1_Status]]
| [[Yocto_Project_3.1_Release_Test_Plan | Yocto_3.1_Overall_Test_Plan]]
| [[Yocto_Project_3.1_Release_Test_Plan#Execution_History | 3.1 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/49201 3.1 release notes]
|-

|-valign="top"
| Yocto Project 3.0
| Zeus
| 22.0
| Armin Kuster/Anuj Mittal
| [[Yocto_2.8_Features]]
| [[Yocto_2.8_Schedule]]
| [[Yocto_Project_v2.8_Status]]
| [[Yocto_Project_2.8_Release_Test_Plan | Yocto_2.8_Overall_Test_Plan]]
| [[Yocto_Project_2.8_Release_Test_Plan#Execution_History | 2.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-October/047111.html 3.0 release notes]
|-
|-valign="top"
| Yocto Project 2.7
| Warrior
| 21.0
| Community
| [[Yocto_2.7_Features]]
| [[Yocto_2.7_Schedule]]
| [[Yocto_Project_v2.7_Status]]
| [[Yocto_Project_2.7_Release_Test_Plan | Yocto_2.7_Overall_Test_Plan]]
| [[Yocto_Project_2.7_Release_Test_Plan#Execution_History | 2.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-May/045028.html 2.7 release notes]
|-
|-valign="top"
| Yocto Project 2.6
| Thud
| 20.0
| Community
| [[Yocto_2.6_Features]]
| [[Yocto_2.6_Schedule]]
| [[Yocto_Project_v2.6_Status]]
| [[Yocto_Project_2.6_Release_Test_Plan | Yocto_2.6_Overall_Test_Plan]]
| [[Yocto_Project_2.6_Release_Test_Plan#Execution_History | 2.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-November/000147.html 2.6 release notes]
|-
|-valign="top"
| Yocto Project 2.5
| Sumo
| 19.0
| Community
| [[Yocto_2.5_Features]]
| [[Yocto_2.5_Schedule]]
| [[Yocto_Project_v2.5_Status]]
| [[Yocto_Project_2.5_Release_Test_Plan | Yocto_2.5_Overall_Test_Plan]]
| [[Yocto_Project_2.5_Release_Test_Plan#Execution_History | 2.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-May/000136.html 2.5 release notes]
|-
|-valign="top"
| Yocto Project 2.4
| Rocko
| 18.0
| Community
| [[Yocto_2.4_Features]]
| [[Yocto_2.4_Schedule]]
| [[Yocto_Project_v2.4_Status]]
| [[Yocto_Project_2.4_Release_Test_Plan | Yocto_2.4_Overall_Test_Plan]]
| [[Yocto_Project_2.4_Release_Test_Plan#Execution_History | 2.4 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-October/000125.html 2.4 release notes]
|-
|-valign="top"
| Yocto Project 2.3
| Pyro
| 17.0
| Community
| [[Yocto_2.3_Features]]
| [[Yocto_2.3_Schedule]]
| [[Yocto_Project_v2.3_Status]]
| [[Yocto_Project_2.3_Release_Test_Plan | Yocto_2.3_Overall_Test_Plan]]
| [[Yocto_Project_2.3_Release_Test_Plan#Execution_History | 2.3 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-May/000112.html 2.3 release notes]
|-
|-valign="top"
| Yocto Project 2.2
| Morty
| 16.0
| Community
| [[Yocto_2.2_Features]]
| [[Yocto_2.2_Schedule]]
| [[Yocto_Project_v2.2_Status]]
| [[Yocto_2.2_Overall_Test_Plan]]
| [[Yocto_Project_2.2_Release_Test_Plan#Execution_History | 2.2 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-November/000101.html 2.2 release notes]
|-
|-valign="top"
| Yocto Project 2.1
| Krogoth
| 15.0
| Community
| [[Yocto_2.1_Features]]
| [[Yocto_2.1_Schedule]]
| [[Yocto_Project_v2.1_Status]]
| [[Yocto_2.1_Overall_Test_Plan]]
| [[2.1 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-May/000089.html 2.1 release notes]
|-
|-valign="top"
| Yocto Project 2.0
| Jethro
| 14.0
| Community
| [[Yocto_1.9_Features]]
| [[Yocto_1.9_Schedule]]
| [[Yocto_Project_v1.9_Status]]
|
| [[1.9 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-November/000076.html 2.0 release notes]
|-valign="top"
| Yocto Project 1.8
| Fido
| 13.0
| Community
| [[Yocto_1.8_Features]]
| [[Yocto_1.8_Schedule]]
| [[Yocto_Project_v1.8_Status]]
| [[Yocto_1.8_Overall_Test_Plan]]
| [[1.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-April/000062.html 1.8 release notes]
|-
| Yocto Project 1.7
| Dizzy
| 12.0
| Community
| [[Yocto_1.7_Features]]
| [[Yocto_1.7_Schedule]]
| [[Yocto_Project_v1.7_Status]]
| [[Yocto_1.7_Overall_Test_Plan]]
| [[1.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-October/000053.html 1.7 release notes]
|-
| Yocto Project 1.6
| Daisy
| 11.0
| Community
| [[Yocto_1.6_Features]]
| [[Yocto_1.6_Schedule]]
| [[Yocto_Project_v1.6_Status]]
| [[Yocto_1.6_Overall_Test_Plan]]
| [[1.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-April/000045.html 1.6 release notes]
|-
| Yocto Project 1.5
| Dora
| 10.0
| Community
| [[Yocto_1.5_Features]]
| [[Yocto_1.5_Schedule]]
| [[Yocto_Project_v1.5_Status]]
| [[Yocto_1.5_Overall_Test_Plan]]
| [[1.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-October/000037.html 1.5 release notes]
|-
| Yocto Project 1.4
| Dylan
| 9.0
| Community
| [[Yocto_1.4_Features]]
| [[Yocto_1.4_Schedule]]
| [[Yocto_Project_v1.4_Status]]
| [[Yocto_1.4_Overall_Test_Plan]]
| [[Yocto_1.4_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-April/000027.html 1.4 release notes]
|-
| Yocto Project 1.3
| Danny
| 8.0
| Community
| [[Yocto_1.3_Features]]
| [[Yocto_1.3_Schedule]]
| [[Yocto_Project_v1.3_Status]]
| [[Yocto_1.3_Overall_Test_Plan]]
| [[Yocto_1.3_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-October/000020.html 1.3 release notes]
|-
| Yocto Project 1.2
| Denzil
| 7.0
| Community
| [[Yocto_1.2_Features]]
| [[Yocto_1.2_Schedule]]
| [[Yocto_Project_v1.2_Status]]
| [[Yocto_1.2_Overall_Test_Plan]]
| [[Yocto_1.2_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-April/000009.html 1.2 release notes]
|-
| Yocto Project 1.1
| Edison
| 6.0
| Community
| [[Yocto_1.1_Features]]
| [[Yocto_1.1_Schedule]]
| [[Yocto_Project_v1.1_Release_Criteria]]
| [[Yocto_1.1_Overall_Test_Plan]]
| [[Yocto_1.1_Milestone_Test_Report]]
|
|-
| Yocto Project 1.0
| Bernard
| 5.0
| Community
| [[Yocto_Features]]
| [[Yocto_1.0_Schedule]]
| [[Yocto_Project_v1.0_Release_Criteria]]
| [[Yocto_1.0_Overall_Test_Plan]]
|
|
|}

2026 Yocto Project Weekly Status Archive

2026-09-08T14:41:55Z

Rpurdie:

== Yocto Project Status 8 September 2026 ==
Current Dev Position: YP 6.1 M3 
Next Deadline: YP 6.1 M3: w/c 2026-08-31 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 10th Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 8st Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 10th Sept. 10am GMT and Monday 14th Sept. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
* YP 5.0.20 is under review.
* YP 6.1 M3 is due to build and we are at feature freeze
* There are issues with changes in bot/AI protection at github.com which are affecting our CI.
* Most M3 changes have merged, we want to mitigate the github issues before building M3.
* There is a new meta-openjdk layer: https://github.com/amarula/meta-openjdk https://lore.kernel.org/yocto-patches/xBB4.1788187111192557019.ULaN@lists.yoctoproject.org/T/#u
* AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
* There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
** Matchbox-wm segfault/xserver restart
** aarch64/x86-64 build host contamination/reproducibility issue
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*Remaining intermittent build failures of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**intermittent ptest failures in many recipes
*Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2622 (last week 2612) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1050 (last week 1039)
**Patches in the Pending State: 136 (13%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 6.0.3 is in review.
**Release Date w/c 2026-08-24
*YP 5.0.20 is in QA.
**Release Date w/c 2026-08-31
*YP 6.0.4
**Build Date w/c 2026-09-28
**Release Date w/c 2026-10-12
*YP 5.0.21
**Build Date w/c 2026-10-05
**Release Date w/c 2026-10-19

*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 1 September 2026 ==
Current Dev Position: YP 6.1 M3 
Next Deadline: YP 6.1 M3: w/c 2026-08-31 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 3rd Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 1st Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 3rd Sept. 10am GMT and Monday 7th Sept. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0.3 is under review.
*YP 5.0.20 is in QA.
*YP 6.1 M3 is due to build this week and we are at feature freeze
*For 6.1 M3 our current intent is to merge:
**rpm 6
**openssl 4
**clang 23.1.0
**7.2 linux kernel
*There were bot protection issues on layerindex causing forbidden errors to queries from layerindex code. These have now been resolved and should be working again.
*AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues.
*It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*Remaining intermittent build failures of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**intermittent ptest failures in many recipes
*Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2612 (last week 2659) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1039 (last week 1028)
**Patches in the Pending State: 139 (13%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 6.0.3 is in review.
**Release Date w/c 2026-08-24
*YP 5.0.20 is in QA.
**Release Date w/c 2026-08-31
*YP 6.0.4
**Build Date w/c 2026-09-28
**Release Date w/c 2026-10-12
*YP 5.0.21
**Build Date w/c 2026-10-05
**Release Date w/c 2026-10-19

*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Status 25 August 2026 ==
Current Dev Position: YP 6.1 M3 
Next Deadline: YP 6.1 M3: w/c 2026-08-31 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 27th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 25th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 27th Aug. 10am GMT and Monday 31st Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0.3 is in QA.
*YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
*For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
*AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*Remaining intermittent build failures of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**intermittent ptest failures in many recipes

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2659 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1028 (last week 1030)
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 6.0.3 is in QA.
**Release Date w/c 2026-08-24
*YP 5.0.20
**Build Date w/c 2026-08-17
**Release Date w/c 2026-08-31
*YP 6.0.4
**Build Date w/c 2026-09-28
**Release Date w/c 2026-10-12
*YP 5.0.21
**Build Date w/c 2026-10-05
**Release Date w/c 2026-10-19

*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 18 August 2026 ==
Current Dev Position: YP 6.1 M3 
Next Deadline: YP 6.1 M3: w/c 2026-08-31 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 20th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 18th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 20th Aug. 10am GMT and Monday 24th Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.1 M3 is due in two weeks and this will be the feature freeze point for YP 6.1.
*AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
*We would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.
*There have been locking changes with do_fetch/do_unpack within the bitbake fetcher to allow better performance of builds with shared DL_DIRs. There are also performance improvements to the handling of repeated ssl connection queries.
*There is discussion on the architecture list about how we could improve the fetcher, particularly around how recursion is handled in git submodules: https://lists.openembedded.org/g/openembedded-architecture/message/2416
*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues.
*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*Remaining intermittent build failures of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**intermittent ptest failures in many recipes

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2704 (last week 2694) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1028)
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 6.0.3 due to release
**Release Date w/c 2026-08-24
*YP 5.0.20
**Build Date w/c 2026-08-17
**Release Date w/c 2026-08-31
*YP 6.0.4
**Build Date w/c 2026-09-28
**Release Date w/c 2026-10-12
*YP 5.0.21
**Build Date w/c 2026-10-05
**Release Date w/c 2026-10-19

*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 11 August 2026 ==
Current Dev Position: YP 6.1 M3 
Next Deadline: YP 6.1 M3: w/c 2026-08-31 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 13rd Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 11th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 13rd Aug. 10am GMT and Monday 17th Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.1 M2 has been released
*YP 6.1 M3 is due in three weeks and this will be the feature freeze point for YP 6.1.
*We would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.
*Alex Stewart is stepping down as maintainer of opkg - huge thanks to him for his work on the project over the last 5 years, and thanks to National Instruments/Emerson for their continued support of opkg. Maintainership is being handed over to Erick Shepherd (also from NI/Emerson), there is also a call for input and anyone interested in being a co-maintainer: https://lists.yoctoproject.org/g/opkg/topic/120687514
*The NPM fetcher has been re-enabled in bitbake with security improvements and additional test cases
*The upgrade to sbom-cve-check 1.3.3 has more correct handling of Ubuntu/Red Hat specific CVEs, which may require new patches or CVE_STATUS assignments. The fallout in OE-core has been handled, other layers may see an uptick in reported CVEs.
*The SDK_TOOLCHAIN_LANGS variable has been replaced with a more general SDK_FEATURES variable to support improved SDK configurability. Uses of the old variable will need to be updated, `go` and `rust` langs are still supported as SDK features.
*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue
*We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
Remaining intermittent build failures of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**intermittent ptest failures in many recipes

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2694 (last week 2694) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1028 (last week 1029)
**Patches in the Pending State: 139 (14%) [last week 141 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M2: was released.
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 6.0.3 due to release
**Release Date w/c 2026-08-24
*YP 5.0.20
**Build Date w/c 2026-08-17
**Release Date w/c 2026-08-31

*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 4 August 2026 ==
Current Dev Position: YP 6.1 M3 
Next Deadline: YP 6.1 M3: w/c 2026-08-31 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 6th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 4th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 6th Aug. 10am GMT and Monday 10th Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.1 M2 is due for release
*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*Remaining intermittent build failures of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**intermittent ptest failures in many recipes
*Some class cleanups were merged which did require tweaks to some metadata:
**https://lore.kernel.org/openembedded-core/20260802102854.3952760-1-richard.purdie@linuxfoundation.org/
**See the “The series does break some things, notably” section
*Some invasive LICENSE changes have merged into master:
**We now require the LICENSE field to match SPDX identifiers.
**The build will issue warnings when this isn’t the case.
**Non SPDX licenses will need to be of the form LicenseRef-XXX
**CLOSED is no longer a valid value.
**‘WITH’ license exceptions are now supported
Big thanks to Joshua for getting us to the point where we can finally clean this up!
*We continue to work on the backlog of patches which has slightly reduced and we’re trying to catch up with AUH updates.
*Toolchain upgrades merged to glibc and bintuils with many other recipe version updates too.
*Rust is now using a shared work directory which reduces disk usage significantly.
*There have been further important fixes in pseudo which were included in the latest upgrade.
*The new uninative does not have i686 build host support. This will mean i686 build host support with uninative will no longer be possible out the box when that is merged to the LTS branches. It is unlikely anyone should be using that!

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2694 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1029 (last week 1021)
**Patches in the Pending State: 141 (14%) [last week 141 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M2: due for release
**Release Date: w/c 2026-08-03
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 6.0.3 due to release
**Release Date w/c 2026-08-24
*YP 5.0.20
**Build Date w/c 2026-08-17
**Release Date w/c 2026-08-31

*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 28 July 2026 ==
Current Dev Position: YP 6.1 M3 
Next Deadline: YP 6.1 M3: w/c 2026-08-31 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 30th July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 28th July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 30th July 10am GMT and Monday 3rd Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.19 has been released
*YP 6.1 M2 is out of QA and under review
*Progress has been made with some of the AB-INT issues:
**We identified a kernel issue likely causing the arm psplash boot hangs
**The groff race issues were reported upstream and we have that section of the build disabled for groff-native now to avoid them
**Several pseudo issues were patched in a recent update
**One infrastructure issue on a worker was corrected
*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*Some invasive LICENSE changes have merged into master:
**We now require the LICENSE field to match SPDX identifiers.
**The build will issue warnings when this isn’t the case.
**Non SPDX licenses will need to be of the form LicenseRef-XXX
**CLOSED is no longer a valid value.
**‘WITH’ license exceptions are now supported
Big thanks to Joshua for getting us to the point where we can finally clean this up!
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream. Initial results are good, some manual tweaking of commit messages may be needed, feedback is welcome to improve the automation.
*We continue to work on the backlog of patches which has slightly reduced.
*Fixes merged to handle ptest reports for both glibc and musl in resulttool and whilst this improves the main reports, it does cause noise in the regression reports due to poor comparison baselines.
*Remaining intermittent build failures of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**intermittent ptest failures in many recipes

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2689 (last week 2719) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1021 (last week 1019)
**Patches in the Pending State: 141 (14%) [last week 144 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M2: out of QA.
**Release Date: w/c 2026-08-03
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 5.0.19 due to release
**Release Date w/c 2026-07-13
*YP 6.0.3
**Build Date w/c 2026-08-10
**Release Date w/c 2026-08-24
*YP 5.0.20
**Build Date w/c 2026-08-17
**Release Date w/c 2026-08-31

*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 21 July 2026 ==
Current Dev Position: YP 6.1 M2 
Next Deadline: YP 6.1 M2: w/c 2026-07-20 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 23rd July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 21st July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 23rd July 10am GMT and Monday 27th July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0.2 has been released
*YP 5.0.19 is due to release
*YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
*Some invasive LICENSE changes have merged into master:
**We now require the LICENSE field to match SPDX identifiers.
**The build will issue warnings when this isn’t the case.
**Non SPDX licenses will need to be of the form LicenseRef-XXX
**CLOSED is no longer a valid value.
**‘WITH’ license exceptions are now supported
Big thanks for Joshua for getting us to the point where we can finally clean this up!
*We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
*A couple of further pseudo related issues were identified, one with linkat flags and one with openat2 (tar related/triggered). We hope to have patches merged soon.
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. The review calls are running out of time each meeting which limits progress.
**We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
**several qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2719 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1019 (last week 1019+)
**Patches in the Pending State: 144 (14%) [last week 145 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M2:
**Build Date: w/c 2026-07-20
**Release Date: w/c 2026-08-03
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 5.0.19 due to release
**Release Date w/c 2026-07-13
*YP 6.0.3
**Build Date w/c 2026-08-10
**Release Date w/c 2026-08-24
*YP 5.0.20
**Build Date w/c 2026-08-17
**Release Date w/c 2026-08-31

*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 14 July 2026 ==
Current Dev Position: YP 6.1 M2 
Next Deadline: YP 6.1 M2: w/c 2026-07-20 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 16th July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 14th July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 16th July 10am GMT and Monday 20th July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0.2 is due to release
*YP 5.0.19 is in review
*M2 is next week!
*We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
*We are happy to report we worked with Free BSD upstream and have resolved the NFS open/lock issue with a kernel patch that was impacting the autobuilder.
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*We have become aware we should ideally replace eudev with a minimal udev build from systemd instead similar to what some other distros are doing.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*The layer.conf changes are likely to be deferred to 6.2 due to lack of time to gather community consensus before feature freeze.
*We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
**several qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2689 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1019 (last week 1037)
**Patches in the Pending State: 145 (14%) [last week 145 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M2:
**Build Date: w/c 2026-07-20
**Release Date: w/c 2026-08-03
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 6.0.2 is due to release
**Release Date w/c 2026-07-06
*YP 5.0.19 is in review
**Release Date w/c 2026-07-13
*YP 6.0.3
**Build Date w/c 2026-08-10
**Release Date w/c 2026-08-24
*YP 5.0.20
**Build Date w/c 2026-08-17
**Release Date w/c 2026-08-31

*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 7 July 2026 ==
Current Dev Position: YP 6.1 M2 
Next Deadline: YP 6.1 M2: w/c 2026-07-20 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 9th July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 7th July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 9th July 10am GMT and Monday 13th July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.1 M1 was released
*YP 6.0.2 is in review
*YP 5.0.19 is in QA
*We are now two weeks away from M2!
*We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
*We are having some challenges with the autobuilder, both with an NFS server open file/lock build up of some kind causing slowdown and eventual halting of write operations and also a mkdir cache race issue. We are working to debug both issues but it is distracting from other work like patch review and new development (e.g. layer.conf format changes).
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*We have become aware we should ideally replace eudev with a minimal udev build from systemd instead similar to what some other distros are doing.
*We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*A key pseudo memory corruption issue when interacting with bash was identified and patches are being worked on for a new pseudo release to address this.
*Intermittent build failures continue to be problematic:
**several qemu ‘hang’ type issues
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2647 (last week 2620) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1036 (last week 1054)
**Patches in the Pending State: 145 (14%) [last week 145 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M2:
**Build Date: w/c 2026-07-20
**Release Date: w/c 2026-08-03
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 5.0.19 is in QA.
**Release Date w/c 2026-07-13
*YP 6.0.3
**Build Date w/c 2026-08-10
**Release Date w/c 2026-08-24
*YP 5.0.20
**Build Date w/c 2026-08-17
**Release Date w/c 2026-08-31

*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 30 June 2026 ==
Current Dev Position: YP 6.1 M2 
Next Deadline: YP 6.1 M2: w/c 2026-07-20 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 2nd July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 30th June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 2nd July 10am GMT and Monday 6th July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.1 M1 was released
*YP 6.0.2 is in QA
*The number of open CVEs on scarthgap has been reduced with stable kernel updates merging. We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases, see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
*Systemd v260+ will require a host Linux kernel of 5.10 or later due to systemd utils run during the build process. This presents issues with RHEL 8 era distros which have older kernel versions. We have patches in progress but if you’re using these distros, assistance will be needed to keep them supported. See https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*Intermittent build failures continue to be problematic:
**several qemu ‘hang’ type issues
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2647 (last week 2620) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1036 (last week 1054)
**Patches in the Pending State: 145 (14%) [last week 145 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M2:
**Build Date: w/c 2026-07-20
**Release Date: w/c 2026-08-03
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 5.0.19
**Build Date w/c 2026-06-30
**Release Date w/c 2026-07-13
*YP 6.0.3
**Build Date w/c 2026-08-10
**Release Date w/c 2026-08-24

*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 23 June 2026 ==
Current Dev Position: YP 6.1 M2 
Next Deadline: YP 6.1 M1: w/c 2026-07-20 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 25th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 23rd June. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 25th June 10am GMT and Monday 29th June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0.1 was released
*YP 6.1 M1 is in review
*AUH is now running daily in incremental mode. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know. Help is needed with resolving automatic update failures and getting the patches into a state where they can be accepted.
*CVE metrics are up on scarthgap & wrynose branches due to delays with kernel upgrades. We’ve had intermittent LTP failures, kconfig type changes, lttng build failures and new warnings in dmesg which we needed to handle. We’re working through this, help is needed to accelerate testing of future stable kernel upgrades.
*Systemd v260 will require Linux 5.10 or later. We run some systemd utils on the host during the build, so this presents issues with RHEL 8 era distros which have older kernel versions. If you use one of these distros, assistance may be needed to keep them supported. See https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*Intermittent build failures continue to be problematic:
**several qemu ‘hang’ type issues
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2620 (last week 2590) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1054(last week 1061)
**Patches in the Pending State: 145 (14%) [last week 146 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M1:
**Build Date: w/c 2026-06-08
**Release Date: w/c 2026-06-22
*6.1 M2:
**Build Date: w/c 2026-07-20
**Release Date: w/c 2026-08-03
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 6.0.1 is due to release
*YP 6.0.2
**Build Date w/c 2026-06-23
**Release Date w/c 2026-07-06
*YP 5.0.19
**Build Date w/c 2026-06-30
**Release Date w/c 2026-07-13
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 16 June 2026 ==
Current Dev Position: YP 6.1 M2 
Next Deadline: YP 6.1 M1: w/c 2026-07-20 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 18th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 16th June. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 18th June 10am GMT and Monday 22nd June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0.1 is due for release
*YP 6.1 M1 is in QA
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*An initial round of patches to remove shell=True subprocess usage in OE-Core have now merged
*AUH is now running daily in incremental mode so we can avoid large batches of upgrade patches and spread them out as well as reacting more quickly to new upstream releases. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know.
*We’ve deliberately aimed to get up to date with the AUH success patches to better evaluate the ongoing upgrades.
*We have merged support for `devtool upgrade --stable` and the upstream-stable-release-point bbclass. We hope to use this to track upstream projects with known good stable release series, but we need input and discussion on what the criteria should be. Please participate in the discussion on the OE-Architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/119437109
*Intermittent build failures continue to be problematic and unchanged from last week:
**several qemu ‘hang’ type issues - the qemu upgrade merged, at least some issues still occur
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes (python3-click was tweaked)
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2590 (last week 2655) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1061 (last week 1056)
**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M1:
**Build Date: w/c 2026-06-08
**Release Date: w/c 2026-06-22
*6.1 M2:
**Build Date: w/c 2026-07-20
**Release Date: w/c 2026-08-03
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 6.0.1 is due to release
*YP 6.0.2
**Build Date w/c 2026-06-23
**Release Date w/c 2026-07-06
*YP 5.0.19
**Build Date w/c 2026-06-30
**Release Date w/c 2026-07-13
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 9 June 2026 ==
Current Dev Position: YP 6.1 M1 
Next Deadline: YP 6.1 M1: w/c 2026-06-08 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 11th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 9th June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 11th June 10am GMT and Monday 15th June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.18 has been released
*YP 6.0.1 is in QA.
*YP 6.1 M1 is due to build this week
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
*We have merged support for `devtool upgrade --stable` and the upstream-stable-release-point bbclass. We hope to use this to track upstream projects with known good stable release series, but we need input and discussion on what the criteria should be. Please participate in the discussion on the OE-Architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/119437109
*We have changed the xz and zstd decompression dependencies to make the build slightly more efficient and use the host tools for decompression
*Intermittent build failures continue to be problematic and unchanged from last week:
**several qemu ‘hang’ type issues
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2655 (last week 2630) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1056 (last week 1087)
**Patches in the Pending State: 147 (14%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming development releases:''' 
*6.1 M1:
**Build Date: w/c 2026-06-08
**Release Date: w/c 2026-06-22
*6.1 M2:
**Build Date: w/c 2026-07-20
**Release Date: w/c 2026-08-03
*6.1 M3:
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02

'''Upcoming dot releases:''' 
*YP 6.0.1 is in QA.
*YP 6.0.2
**Build Date w/c 2026-06-23
**Release Date w/c 2026-07-06
*YP 5.0.19
**Build Date w/c 2026-06-30
**Release Date w/c 2026-07-13
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 2 June 2026 ==
Current Dev Position: YP 6.1 M1 
Next Deadline: YP 6.1 M1: w/c 2026-06-08 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 4th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 2nd June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 4th June 10am GMT and Monday 8th June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.18 is due to be released
*YP 6.0.1 is in QA.
*YP 6.1 M1 is due to build next week
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*The upgrade to gcc 16 merged
*We are planning to improve our python subprocess calls to avoid shell=True, we would appreciate others following and doing this in their code too.
*Intermittent build failures continue to be problematic and unchanged from last week:
**several qemu ‘hang’ type issues
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*Qemu v11 dropped support for 32 bit hosts and we are likely to drop support for running builds on 32 bits hosts
*The upstream kernel is looking likely to drop x32 support and if they do, we will have to drop our support too - let hem/us know if you’re using it!
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2630 (last week 2660) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 108 (last week 1083)
**Patches in the Pending State: 147 (14%) [last week 148 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
7
'''Upcoming dot releases:''' 
*YP 5.0.18 is in review.
*YP 6.0.1 is in QA.
*YP 6.0.2
**Build Date 2026-06-23
**Release Date 2026-07-06
*YP 5.0.19
**Build Date 2026-06-30
**Release Date 2026-07-13
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Status 26 May 2026 ==
Current Dev Position: YP 6.1 M1 
Next Deadline: YP 6.1 M1: w/c 2026-06-08 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 28th May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 26th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 28th May 10am GMT and Monday 1st June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.18 is out of QA and under review.
*YP 6.0.1 is in QA
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*Intermittent build failures continue to be problematic and unchanged from last week:
**several qemu ‘hang’ type issues
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*Is anyone using 32 bit SDKs, if so let us know. Qemu dropped support for 32 bit hosts and we are considering discontinuing 32 bit SDKs.
*We are likely to merge the gcc 16 upgrade soon
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto
*We are updating the project’s security team and welcome nominations and/or feedback: https://lists.openembedded.org/g/openembedded-architecture/topic/119388716

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2660 (last week 2673) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1083 (last week 1083)
**Patches in the Pending State: 148 (14%) [last week 148 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming dot releases:''' 
*YP 5.0.18 is in review.
*YP 6.0.1 is in QA.
*YP 5.0.19
**Build Date 2026-06-30
**Release Date 2026-07-13
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 19 May 2026 ==
Current Dev Position: YP 6.1 M1 
Next Deadline: YP 6.1 M1: w/c 2026-06-08 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 21st May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 19th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 21st May 10am GMT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0 was released, thanks everyone who contributed!
*YP 5.0.18 is in QA.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*Intermittent build failures continue to be problematic:
**several qemu ‘hang’ type issues
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*Master (blacksail) is open for new development
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto
*We are updating the project’s security team and welcome nominations and/or feedback: https://lists.openembedded.org/g/openembedded-architecture/topic/119388716
*Monday 25th May is a public holiday in the UK and USA so there will be no patch review call.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2673 (last week 2688) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1083 (last week 1087)
**Patches in the Pending State: 148 (14%) [last week 146 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming dot releases:''' 
*YP 5.3.4 was released.
*YP 5.0.18 is in QA.
*YP 6.0.1
**Build Date 2026-05-18
**Release Date 2026-06-01
*YP 5.0.19
**Build Date 2026-06-30
**Release Date 2026-07-13
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 12 May 2026 ==
Current Dev Position: YP 6.1 M1 
Next Deadline: YP 6.1 M1: w/c 2026-06-08 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 14th May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 12th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 14th May 10am GMT and Monday 18th May 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.4 is due to release (has been approved)
*YP 6.0 is due to release (has been approved)
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
*Intermittent build failures continue to be problematic
*We have pruned the release artefacts, please let us know if any you would like to use are missing. We’re also interested to know which ones people actually use outside of uninative/buildtools and the BSP test images.
*Master is open for new development
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. Please send proposals to the mailing list or raise them during the weekly status call, Paul will be collecting these into a project roadmap.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2688 (last week 2698) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1087 (last week 1087)
**Patches in the Pending State: 146 (13%) [last week 146 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming dot releases:''' 
*YP 5.3.4 is due to release
*YP 5.0.18
**Build Date 2026-05-11
**Release Date 2026-05-25
*YP 6.0.1
**Build Date 2026-05-18
**Release Date 2026-06-01
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 5 May 2026 ==
Current Dev Position: YP 6.1 M1 
Next Deadline: YP 6.1 M1: w/c 2026-06-22 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 7th May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 5th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 7th May 10am GMT and Monday 11th May 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.35 was released
*YP 5.3.4 is due to release, pending TSC approval
*YP 6.0 is due to release, pending TSC approval
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
*Intermittent build failures continue to be problematic
*Patch review/merging is slow due to public holidays clashing with a review call
*Master is open for new development.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2698 (last week 2788) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1087 (last week 1085)
**Patches in the Pending State: 146 (13%) [last week 146 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming dot releases:''' 
*YP 5.3.4 is due to release, pending TSC approval
*YP 5.0.18
**Build Date 2026-05-11
**Release Date 2026-05-25
*YP 6.0.1
**Build Date 2026-05-18
**Release Date 2026-06-01
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 28 April 2026 ==
Current Dev Position: YP 6.0 M4 
Next Deadline: YP 6.0 Release Date w/c 2026-05-04 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 30th Apr. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 29th Apr. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 30th Apr. 10am GMT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.35 is due to release
*YP 5.3.4 is in QA
*YP 6.0 rc1 is in QA
*There will be no patch review on Monday 4th May due to public holidays.
*We continue to triage the CVEs being reported by the new tooling.
*There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
*There have been several issues in pseudo identified and these have been fixed in the various pseudo point releases. We will upgrade pseudo in 6.0.1 to pull these in.
*There have been issues with 403 errors from crates.io, there is a change in bitbake to use the preferred upstream urls via their CDN.
*The kvm cpu features issue looks to be a host system CPU microcode issue and using the latest microcode appears to have resolved the issues.
*git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback but are trying to clear the backlog.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2788 (last week 2790) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1085 (last week 1078)
**Patches in the Pending State: 146 (13%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming dot releases:''' 
*YP 4.0.35 is in review.
*YP 5.3.4 is in QA
**Release Date 2026-05-06
*YP 5.0.18
**Build Date 2026-05-11
**Release Date 2026-05-25
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 21 April 2026 ==
Current Dev Position: YP 6.0 M4 
Next Deadline: YP 6.0 M4 Build Date 2026-04-20 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 23rd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 21st 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 23rd 10am GMT and Monday Apr. 27th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.17 was released
*YP 6.0 M3 was released
*YP 4.0.35 is in QA
*YP 6.0 M4 is due to build
*We continue to triage the CVEs being reported by the new tooling.
*Various fixes have merged or are planned to merge before the M4 release build:
**Various CVE issue resolutions from CVE triage
**Reproducibility issues with strace/apr-util
**Make race in groff
**Shadow-native tallylog issue fix
**Upgrade of barebox to align with an LTS release
**Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
**Sbom-cve-check upgrade (along with dependencies)
*Issues still pending:
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
**Intermittent wic failures on the autobuilder
*At this point we will likely run the release build as the remaining issues aren’t critical to end users and we have no clear timeframe for resolution of them
git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The final whinlatter build is happening this week.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2790 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1078 (last week 1072)
**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''Upcoming dot releases:''' 
*YP 5.0.17 was released.
*YP 4.0.35 is in QA.
*YP 5.3.4
**Build Date 2026-04-20
**Release Date 2026-05-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Status 14 April 2026 ==
Current Dev Position: YP 6.0 M4 
Next Deadline: YP 6.0 M4 Build Date 2026-04-20 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 16th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 14th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 16th 10am GMT and Monday Apr. 20th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.17 is due to be released
*YP 6.0 M3 is in QA
*YP 4.0.35 is queued for QA
*We have converted over to sbom-cve-check and dropped cve-check. This has caused a significant increase in CVEs reported, these are being triaged.
*Issues with pending work needed:
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Reports of pseudo errors on Fedora 44 beta related to openat2()
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
**Meta-oe cve layer filtering under new tooling (metrics script tweak?)
**Reprodicubility issues with strace/apr-util after gnulib macro changes (patches in testing)
*There was disruption to git services last week due to scraping attacks against the servers. This resulted in connection issues whilst those were mitigated, particularly the git protocol access.
git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
*The recent wic changes will need wic support files to be placed in files/wic within layers going forwards.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The final kirkstone build has taken place and we’re no longer planning to merge patches on this branch.
*If you have any final patches for whinlatter, please get these sent to the list ASAP.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2777 (last week 2797) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1072 (last week 1060)
**Patches in the Pending State: 147 (14%) [last week 148 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M3 in QA.
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.0.17 is in review.
*YP 4.0.35 is in QA.
*YP 5.3.4
**Build Date 2026-04-20
**Release Date 2026-05-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 7 April 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 9th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 7th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 9th 10am GMT and Monday Apr. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.3 was released.
*YP 5.0.17 is in QA
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*Issues with pending work needed:
**Converting scripts/run-cvecheck to sbom-cve-check
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds (need tags)
**Ubuntu 26.04 support (need worker adding for testing)
*Issues that have patches ready to merge:
**DISTRO_FEATURES defaults improvements.
**Fixing yocto-check-layer to work with --machines
**RHEL 9 xattrs/selinux/tar issue
**Splitting wic into an external tool.
**RHEL 10/openSUSE Leap 16.0 support
*Issues that need investigation
**Reports of pseudo errors on Fedora 44 beta
*The proposed wic changes will need wic support files to be placed in files/wic within layers going forwards.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*We are aware of our git hosting giving 502 Bad Gateway errors, this is being investigated
*The CFP for the Yocto Project Workshop at Embedded Recipes 2026 closes today: https://pretalx.com/yocto-embedded-recipes-2026/cfp

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2797 (last week 2814) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1060 (last week 1062)
**Patches in the Pending State: 148 (14%) [last week 148 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.3.3 was released.
*YP 5.0.17 is in QA.
*YP 4.0.35
**Build Date 2026-04-06
**Release Date 2026-04-22
*YP 5.3.4
**Build Date 2026-04-20
**Release Date 2026-05-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 31 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 2nd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 31st Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 2nd 10am GMT and Monday Apr. 6th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.34 was released.
*YP 5.3.3 is approved for release.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*Issues still pending:
**Splitting wic into an external tool.
**Converting scripts/run-cvecheck to sbom-cve-check
**DISTRO_FEATURES defaults improvements.
**RHEL 9 xattrs/selinux/tar issue
**How to improve DEBUG_BUILD?
**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
*Issues that are mostly known quantities still needing work:
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Fixing yocto-check-layer to work with --machines (many fixes merged)
*Issues that were resolved this week:
**Sbom-cve-check added
**Replacement of runtlp with kirk (Thanks Daniel!)
**bitbake-setup vscode integration
**Fedora 43 selftest failures
**Reconciling poky and OE-Core defaults templates.
*We have rationalized the tags in various project repositories, more information can be found here: https://lists.openembedded.org/g/openembedded-architecture/message/2312 Whilst controversial, this will make the tag list much easier to understand for users, guide users to use the right tags going forward and remove confusion about whether any tags were “missed”, at the expense that some CI setups may need adjusting short term.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The CFP closing date for the Yocto Project Workshop at Embedded Recipes 2026 has been extended until April 7th, please submit a proposal if you’d like to present: https://pretalx.com/yocto-embedded-recipes-2026/cfp

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2814 (last week 2819) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1062 (last week 1072)
**Patches in the Pending State: 148 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 4.0.34 was released.
*YP 5.3.3 ready for release.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 24 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Mar. 10am GMT and Monday 30th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0 M2 has been released.
*YP 4.0.34 is due to be released.
*YP 5.3.3 is in review after QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are many key changes needed still missing.
**Issues still pending:
**Splitting wic into an external tool.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*Issues that are mostly known quantities still needing work:
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
**Fixing yocto-check-layer to work with –machines
*Issues that were resolved this week:
**Switching to pkg-config.
**Allowing non-destructive git fetcher updates for bitbake-setup (further tweaks still being discussed)
*We are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due to xattrs)
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 was released.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 4.0.34 ready for release.
*YP 5.3.3 is in review.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Mar. 10am GMT and Monday 23rd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.2 has been released
*YP 6.0 M2 is due to be released
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build next week however there are many key changes needed still missing.
*We have issues we need to resolve before M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
*glibc was upgraded 2.43 and we released a new uninative to match
*runqemu now has better handling for different display outputs including VNC on unix domain sockets
*We are adding testing of ptests on musl to our test matrix
*Kernel rust support has merged
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*Thanks to everyone who helped out with the booth at Embedded World, it was a great success!

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is ready for release.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 is in QA.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Mar. 10am GMT and Monday 16th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.16 has been released
*YP 5.3.2 is due to be released
*YP 6.0 M2 is in QA
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build in 2 weeks however there are many key changes needed still missing.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before M3:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Switch to internal VNC server in QEMU
**update to glibc 2.43 so we can release a new uninative
*We identified a number of timeout/buffer related issues in and around ptest-runner and whilst we’re still in early stages of testing, these look to significantly improve autobuilder intermittent ptest failures, particularly on qemuriscv64.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*The project has a booth at Embedded World this week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2866 (last week 2908) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1081 (last week 1103)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.0.16 is released.
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-16
*YP 5.3.3 Release Date 2026-04-01
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Mar. 10am GMT and Monday 9th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashbard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 has been released
*YP 5.0.16 is in TSC review
*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
**We are aware of changes in QA timelines and are discussing how to address them.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
*OE-Core switched to enabling a hash equivalence server by default.
*We’re working through the backlog of patches and the high number of intermittent build failures is still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1107)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 is in review.
*YP 5.3.2 is in QA.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 24 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Feb. 10am GMT and Monday 2nd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is due for release
*YP 5.0.16 is in QA
*YP 5.2.3 is queued for QA
*YP 6.0 M2 is due to build when we have patches merged
*We have two open high issues which need further work that will block M3:
**x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup
**Splitting wic into an external tool
**Kernel rust support
**Switching to pkg-config
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES changes to ‘nodistro’ in OE-Core
**SBOM/cve-check changes
*We updated “nodistro” to use 3 of the include files poky was already using:
**Space optimization to reduce build footprint and sstate object size
**Disabling most static libraries by default (build size/speed wins)
**Enabling security flags by default
*“nodistro” now also enables uninative by default to allow for better CDN sstate reuse
*Distros now need to use INIT_MANAGER to select their preferred init system with the default being systemd for “nodistro”. Poky’s defaults remain unchanged and we don’t have plans to change this at this time due to the work involved and impact (e.g test result comparisons).
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2893 (last week 2941) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1107 (last week 1108)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is awaiting approval
*YP 5.0.16 is in QA
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1108 (last week 1106)
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Feb. 10am GMT and Monday 16th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 was released
*YP 6.0 M1 was released
*YP 4.0.33 is in QA
*YP 6.0 M2 is due to build next week.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2973 (last week 2945) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1106 (last week 1100)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.33 is in QA.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 February 2026==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 is due to be released
*YP 6.0 M1 is in QA
*YP 4.0.33 is queued for QA after 6.0 M1
*YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
*Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**Hangs of the autobuilder controller (database locking?) (#16129)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**rust do_test_compile/do_install segfault (#16058)
**x86 kvm broken on Fedora 43 (#16074)
*“build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1100 (last week 1097)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M2 Build Date 2026-02-02 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
* YP 5.0.15 was released
* YP 5.3.1 is under review
* YP 6.0 M1 is in QA
* YP 4.0.33 is queued for QA after 6.0 M1
* YP 6.0 M2 is due next week!
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
* There are currently 6 high open bugs, which will block M2:
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
** x86 kvm broken on Fedora 43 (#16074)
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
** Hangs of the autobuilder controller (database locking?) (#16129)
** Generation of releases.json needs updating (#16138)
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
* Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
* WDD 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 22nd Jan. 10am GMT and Monday 26th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: build-sysroots: useradd command did not succeed (#16135)
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback.

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

'''Ways to contribute:''' 
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

'''New to the project?''' 
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

'''Tracking Metrics:''' 
*WDD 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''Ways to contribute:''' 
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*There is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
*There are bugs identified as possible for newcomers to the project: https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_Unassigned_Enhancements/Bugs
*We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
*Help us resolve CVE issues: CVE metrics
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*Ongoing project development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing We need to continue to develop this as it will allow us to potentially find ways to fund specific work items.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Rpurdie: /* Release Activity */

== Release Activity==

Releases can be downloaded at https://www.yoctoproject.org/software-overview/downloads/

{| class="wikitable" border="2"
!Codename
!Yocto Project Version
!Release Date
!Current Version
!Support Level
!Poky Version
!BitBake branch
! Maintainer
|-
|Nanbield
|4.3
| October 2023
|
|Future - Support for 7 months (until April 2024)
|N/A
|
|Richard Purdie <richard.purdie@linuxfoundation.org>
|-
|Mickledore
|4.2
| April 2023
|
|Future - Support for 7 months (until October 2023)
|N/A
|
|Richard Purdie <richard.purdie@linuxfoundation.org>
|-
|Langdale
|4.1
| October 2022
| 4.1.2 (January 2023)
| Support until May 2023
|N/A
|2.2
|Steve Sakoman <steve@sakoman.com>
|-
|Kirkstone
|4.0
|May 2022
|4.0.6 (December 2022)
|Long Term Support (minimum Apr. 2024¹)
|N/A
|2.0
|Steve Sakoman <steve@sakoman.com>
|-
|-style="color: slategray;"
|Honister
|3.4
|October 2021
|3.4.4 (May 2022)
|EOL
|N/A
|1.52
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Hardknott
|3.3
|April 2021
|3.3.6 (April 2022)
|EOL
|N/A
|1.50
|Anuj Mittal <anuj.mittal@intel.com>
|-
|-style="color: slategray;"
|Gatesgarth
|3.2
|Oct 2020
|3.2.4 (May 2021)
|EOL
|N/A
|1.48
|Anuj Mittal <anuj.mittal@intel.com>
|-
|Dunfell
|3.1
|April 2020
|3.1.22 (January 2023)
|Long Term Support (until Apr. 2024¹)
|23.0
|1.46
|Steve Sakoman <steve@sakoman.com>
|-style="color: slategray;"
|Zeus
|3.0
|October 2019
|3.0.4 (August 2020)
|EOL
|22.0.3
|1.44
| Anuj/Armin
|-style="color: slategray;"
|Warrior
|2.7
|April 2019
|2.7.4 (June 2020)
|EOL
|21.0
|1.42
|Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Thud
|2.6
|Nov 2018
|2.6.4 (October 2019)
|EOL
|20.0
|1.40
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Sumo
|2.5
|April 2018
|2.5.3 (April 2019)
|EOL
|19.0
|1.38
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Rocko
|2.4
|Oct 2017
|2.4.4 (November 2018)
|EOL
|18.0
|1.36
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Pyro
|2.3
|May 2017
|2.3.4 (July 2018)
|EOL
|17.0
|1.34
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Morty
|2.2
|Nov 2016
|2.2.4 (July 2018)
|EOL
|16.0
|1.32
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Krogoth
|2.1
|Apr 2016
|2.1.3 (July 2017)
|EOL
|15.0
|1.30
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Jethro
|2.0
|Nov 2015
|2.0.3 (January 2016)
|EOL
|14.0
|1.28
|Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Fido
|1.8
|Apr 2015
|1.8.2
|EOL
|13.0
|1.26
|Joshua Lock <joshua.g.lock@intel.com>
|-style="color: slategray;"
|Dizzy
|1.7
|Oct 2014
|1.7.3
|EOL
|12.0
|1.24
| Armin Kuster <akuster808@gmail.com>
|-style="color: slategray;"
|Daisy
|1.6
|Apr 2014
|1.6.3
|EOL
|11.0
|1.22
| Saul Wold <sgw@linux.intel.com>
|-style="color: slategray;"
|Dora
|1.5
|Oct 2013
|1.5.4
|EOL
|10.0
|1.20
| Robert Yang <liezhi.yang@windriver.com>
|-style="color: slategray;"
|Dylan
|1.4
|Apr 2013
|1.4.3
|EOL
|9.0
|1.18
| Paul Eggleton <paul.eggleton@linux.intel.com>
|-style="color: slategray;"
|Danny
|1.3
|Oct 2012
|1.3.2
|EOL
|8.0
|1.16
|Ross Burton <ross.burton@intel.com>
|-style="color: slategray;"
|Denzil
|1.2
|Apr 2012
|1.2.2
|EOL
|7.0
|1.15
|-style="color: slategray;"
|Edison
|1.1
|Oct 2011
|1.1.2
|EOL
|6.0
|1.13
|-style="color: slategray;"
|Bernard
|1.0
|Apr 2011
|1.0.2
|EOL
|5.0
|1.11
|-style="color: slategray;"
|Laverne
|0.9
|Oct 2010
|
|
|4.0
|1.11
|-style="color: slategray;"
|Green
|N/A
|11 June 2010
|
|
|3.3
|
|-style="color: slategray;"
|Purple
|N/A
|15 Dec 2009
|
|
|3.2
|
|-style="color: slategray;"
|Pinky
|N/A
|12 Nov 2009
|
|
|3.1
|
|-style="color: slategray;"
|Blinky
|N/A
|1 Aug 2007
|
|
|3.0
|
|-style="color: slategray;"
|Clyde
|N/A
|19 Jan 2007
|
|
|2.0
|
|-style="color: slategray;"
|Inky
|N/A
|10 Feb 2006
|
|
|1.0
|
|}

'''Note:''' see also [[Stable Release and LTS]], [[Linux Yocto]], [[Planning]] and [[Release Feature Table]] pages. EOL means some community support on email lists but no commit updates in the repos. There is also OS Vendor support for some Yocto EOL releases.

¹ The 3.1 series was originally planned for two years but extended to four. No decision has been made about 4.0, it would be a decision by the project members who fund it. The project in unable to commit to funding the work multiple years in advance.

== Releases Links==
{| class="wikitable" border="2"
| align="center" style="background:#f0f0f0;"|'''Yocto Project Release'''
| align="center" style="background:#f0f0f0;"|'''Code Name'''
| align="center" style="background:#f0f0f0;"|'''Poky version'''
| align="center" style="background:#f0f0f0;"|'''Maintainer'''
| align="center" style="background:#f0f0f0;"|'''Features'''
| align="center" style="background:#f0f0f0;"|'''Schedule'''
| align="center" style="background:#f0f0f0;"|'''Status'''
| align="center" style="background:#f0f0f0;"|'''QA Test Plan'''
| align="center" style="background:#f0f0f0;"|'''QA Test Report'''
| align="center" style="background:#f0f0f0;"|'''Release notes'''

|-valign="top"
| Yocto Project 3.4
| Honister
| 26.0
| Anuj Mittal
| [[Yocto_3.4_Features]]
| [[Yocto_3.4_Schedule]]
| [[Yocto_Project_v3.4_Status]]
| [[Yocto_Project_3.4_Release_Test_Plan | Yocto_3.4_Overall_Test_Plan]]
| [[Yocto_Project_3.4_Release_Test_Plan#Execution_History | 3.4 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/229 3.4 release notes]
|-
| Yocto Project 3.3
| Hardknott
| 25.0
| Anuj Mittal
| [[Yocto_3.3_Features]]
| [[Yocto_3.3_Schedule]]
| [[Yocto_Project_v3.3_Status]]
| [[Yocto_Project_3.3_Release_Test_Plan | Yocto_3.3_Overall_Test_Plan]]
| [[Yocto_Project_3.3_Release_Test_Plan#Execution_History | 3.3 qa run history]]
| [https://lists.yoctoproject.org/g/yocto-announce/message/215 3.3 release notes]
|-
| Yocto Project 3.2
| Gatesgarth
| 24.0
| Anuj Mittal
| [[Yocto_3.2_Features]]
| [[Yocto_3.2_Schedule]]
| [[Yocto_Project_v3.2_Status]]
| [[Yocto_Project_3.2_Release_Test_Plan | Yocto_3.2_Overall_Test_Plan]]
| [[Yocto_Project_3.2_Release_Test_Plan#Execution_History | 3.2 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/51262 3.2 release notes]
|-
|-valign="top"
| Yocto Project 3.1
| Dunfell
| 23.0
| Steve Sakoman
| [[Yocto_3.1_Features]]
| [[Yocto_3.1_Schedule]]
| [[Yocto_Project_v3.1_Status]]
| [[Yocto_Project_3.1_Release_Test_Plan | Yocto_3.1_Overall_Test_Plan]]
| [[Yocto_Project_3.1_Release_Test_Plan#Execution_History | 3.1 qa run history]]
| [https://lists.yoctoproject.org/g/yocto/message/49201 3.1 release notes]
|-

|-valign="top"
| Yocto Project 3.0
| Zeus
| 22.0
| Armin Kuster/Anuj Mittal
| [[Yocto_2.8_Features]]
| [[Yocto_2.8_Schedule]]
| [[Yocto_Project_v2.8_Status]]
| [[Yocto_Project_2.8_Release_Test_Plan | Yocto_2.8_Overall_Test_Plan]]
| [[Yocto_Project_2.8_Release_Test_Plan#Execution_History | 2.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-October/047111.html 3.0 release notes]
|-
|-valign="top"
| Yocto Project 2.7
| Warrior
| 21.0
| Community
| [[Yocto_2.7_Features]]
| [[Yocto_2.7_Schedule]]
| [[Yocto_Project_v2.7_Status]]
| [[Yocto_Project_2.7_Release_Test_Plan | Yocto_2.7_Overall_Test_Plan]]
| [[Yocto_Project_2.7_Release_Test_Plan#Execution_History | 2.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto/2019-May/045028.html 2.7 release notes]
|-
|-valign="top"
| Yocto Project 2.6
| Thud
| 20.0
| Community
| [[Yocto_2.6_Features]]
| [[Yocto_2.6_Schedule]]
| [[Yocto_Project_v2.6_Status]]
| [[Yocto_Project_2.6_Release_Test_Plan | Yocto_2.6_Overall_Test_Plan]]
| [[Yocto_Project_2.6_Release_Test_Plan#Execution_History | 2.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-November/000147.html 2.6 release notes]
|-
|-valign="top"
| Yocto Project 2.5
| Sumo
| 19.0
| Community
| [[Yocto_2.5_Features]]
| [[Yocto_2.5_Schedule]]
| [[Yocto_Project_v2.5_Status]]
| [[Yocto_Project_2.5_Release_Test_Plan | Yocto_2.5_Overall_Test_Plan]]
| [[Yocto_Project_2.5_Release_Test_Plan#Execution_History | 2.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2018-May/000136.html 2.5 release notes]
|-
|-valign="top"
| Yocto Project 2.4
| Rocko
| 18.0
| Community
| [[Yocto_2.4_Features]]
| [[Yocto_2.4_Schedule]]
| [[Yocto_Project_v2.4_Status]]
| [[Yocto_Project_2.4_Release_Test_Plan | Yocto_2.4_Overall_Test_Plan]]
| [[Yocto_Project_2.4_Release_Test_Plan#Execution_History | 2.4 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-October/000125.html 2.4 release notes]
|-
|-valign="top"
| Yocto Project 2.3
| Pyro
| 17.0
| Community
| [[Yocto_2.3_Features]]
| [[Yocto_2.3_Schedule]]
| [[Yocto_Project_v2.3_Status]]
| [[Yocto_Project_2.3_Release_Test_Plan | Yocto_2.3_Overall_Test_Plan]]
| [[Yocto_Project_2.3_Release_Test_Plan#Execution_History | 2.3 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2017-May/000112.html 2.3 release notes]
|-
|-valign="top"
| Yocto Project 2.2
| Morty
| 16.0
| Community
| [[Yocto_2.2_Features]]
| [[Yocto_2.2_Schedule]]
| [[Yocto_Project_v2.2_Status]]
| [[Yocto_2.2_Overall_Test_Plan]]
| [[Yocto_Project_2.2_Release_Test_Plan#Execution_History | 2.2 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-November/000101.html 2.2 release notes]
|-
|-valign="top"
| Yocto Project 2.1
| Krogoth
| 15.0
| Community
| [[Yocto_2.1_Features]]
| [[Yocto_2.1_Schedule]]
| [[Yocto_Project_v2.1_Status]]
| [[Yocto_2.1_Overall_Test_Plan]]
| [[2.1 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2016-May/000089.html 2.1 release notes]
|-
|-valign="top"
| Yocto Project 2.0
| Jethro
| 14.0
| Community
| [[Yocto_1.9_Features]]
| [[Yocto_1.9_Schedule]]
| [[Yocto_Project_v1.9_Status]]
|
| [[1.9 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-November/000076.html 2.0 release notes]
|-valign="top"
| Yocto Project 1.8
| Fido
| 13.0
| Community
| [[Yocto_1.8_Features]]
| [[Yocto_1.8_Schedule]]
| [[Yocto_Project_v1.8_Status]]
| [[Yocto_1.8_Overall_Test_Plan]]
| [[1.8 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2015-April/000062.html 1.8 release notes]
|-
| Yocto Project 1.7
| Dizzy
| 12.0
| Community
| [[Yocto_1.7_Features]]
| [[Yocto_1.7_Schedule]]
| [[Yocto_Project_v1.7_Status]]
| [[Yocto_1.7_Overall_Test_Plan]]
| [[1.7 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-October/000053.html 1.7 release notes]
|-
| Yocto Project 1.6
| Daisy
| 11.0
| Community
| [[Yocto_1.6_Features]]
| [[Yocto_1.6_Schedule]]
| [[Yocto_Project_v1.6_Status]]
| [[Yocto_1.6_Overall_Test_Plan]]
| [[1.6 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2014-April/000045.html 1.6 release notes]
|-
| Yocto Project 1.5
| Dora
| 10.0
| Community
| [[Yocto_1.5_Features]]
| [[Yocto_1.5_Schedule]]
| [[Yocto_Project_v1.5_Status]]
| [[Yocto_1.5_Overall_Test_Plan]]
| [[1.5 qa run history]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-October/000037.html 1.5 release notes]
|-
| Yocto Project 1.4
| Dylan
| 9.0
| Community
| [[Yocto_1.4_Features]]
| [[Yocto_1.4_Schedule]]
| [[Yocto_Project_v1.4_Status]]
| [[Yocto_1.4_Overall_Test_Plan]]
| [[Yocto_1.4_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2013-April/000027.html 1.4 release notes]
|-
| Yocto Project 1.3
| Danny
| 8.0
| Community
| [[Yocto_1.3_Features]]
| [[Yocto_1.3_Schedule]]
| [[Yocto_Project_v1.3_Status]]
| [[Yocto_1.3_Overall_Test_Plan]]
| [[Yocto_1.3_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-October/000020.html 1.3 release notes]
|-
| Yocto Project 1.2
| Denzil
| 7.0
| Community
| [[Yocto_1.2_Features]]
| [[Yocto_1.2_Schedule]]
| [[Yocto_Project_v1.2_Status]]
| [[Yocto_1.2_Overall_Test_Plan]]
| [[Yocto_1.2_Milestone_Test_Report]]
| [https://lists.yoctoproject.org/pipermail/yocto-announce/2012-April/000009.html 1.2 release notes]
|-
| Yocto Project 1.1
| Edison
| 6.0
| Community
| [[Yocto_1.1_Features]]
| [[Yocto_1.1_Schedule]]
| [[Yocto_Project_v1.1_Release_Criteria]]
| [[Yocto_1.1_Overall_Test_Plan]]
| [[Yocto_1.1_Milestone_Test_Report]]
|
|-
| Yocto Project 1.0
| Bernard
| 5.0
| Community
| [[Yocto_Features]]
| [[Yocto_1.0_Schedule]]
| [[Yocto_Project_v1.0_Release_Criteria]]
| [[Yocto_1.0_Overall_Test_Plan]]
|
|
|}