Weekly Status

2026-06-16T14:47:04Z

Paul Barker:

Weekly Status

2026-06-09T08:13:38Z

Paul Barker: /* Yocto Project Status 9 June 2026 */

== 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 

== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]

Weekly Status

2026-06-09T07:08:01Z

Paul Barker: /* Yocto Project Status 9 June 2026 */

== 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
*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 

== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]

Security private reporting

2026-06-01T20:19:40Z

Paul Barker:

= (WIP) Security team and private reporting =

Note: this page is undergoing migration to [https://docs.yoctoproject.org/ the official Yocto Project documentation].

== How to Report a Potential Vulnerability? ==

If you would like to report a public issue (for example, one with a released CVE number), please report it using the [https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Security Security Bugzilla].

If you are dealing with a not-yet-released or urgent issue, please send a message to security AT yoctoproject DOT org, including as many details as possible: the layer or software module affected, the recipe and its version, and any example code, if available.

''' Branches maintained with security fixes'''
----------------------------------------------
See [https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS Stable release and LTS]for detailed info regarding the policies and maintenance of Stable branch.

The [https://wiki.yoctoproject.org/wiki/Releases Release page] contains a list of all releases of the Yocto Project. Versions in grey are no longer actively maintained with security patches, but well-tested patches may still be accepted for them for significant issues.

== How to Contact the Yocto Project regarding Security ==

We have set up two security-related mailing lists:

* '''Public List'''
: yocto [dash] security [at] yoctoproject[dot] org
: This is a public mailing list for anyone to subscribe to. This list is an open list to discuss public security issues/patches and security-related initiatives. For more information, including subscription information, please see the [https://lists.yoctoproject.org/g/yocto-security yocto-security mailing list info page].

* '''Private List'''
: security [at] yoctoproject [dot] org
: This is a private mailing list for reporting non-published potential vulnerabilities. The list is monitored by the Yocto Project Security team.

'''What you should do if you find a security vulnerability'''
---------------------------------------------
If you find a security flaw; a crash, an information leakage, or anything that can have a security impact if exploited in any Open Source software built or used by the Yocto Project, please report this to the Yocto Project Security Team. If you prefer to contact the upstream project directly, please send a copy to the security team at the Yocto Project as well.
If you believe this is highly sensitive information, please report the vulnerability in a secure way, i.e. encrypt the email and send it to the private list. This ensures that the exploit is not leaked and exploited before a response/fix has been generated.

'''What Yocto Security Team does when it receives a security vulnerability'''
---------------------------------------------
The YP Security Team team performs a quick analysis and would usually report the flaw to the upstream project. Normally the upstream project analyzes the problem. If they deem it a real security problem in their software, they develop and release a fix following their own security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.

The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are normally non-public.

When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.

'''If an upstream project does not respond quickly'''
---------------------------------------------
If an upstream project does not fix the problem in a reasonable time, the Yocto's Security Team will contact other interested parties (usually other distributions) in the community and together try to solve the vulnerability as quickly as possible.

The Yocto Project Security team adheres to the 90 days disclosure policy by default. An increase of the embargo time is possible when necessary.

== Security Team Appointment ==

The Yocto Project Security Team consists of at least three members. When new members are needed, the YP TSC asks for nominations by public channels including a nomination deadline. Self-nominations are possible. When the limit time is reached, the YP TSC posts the list of candidates for the comments of project participants and developers. Comments may be sent publicly or privately to the YP and OE TSCs. The candidates are approved by both YP TSC and OE TSC and the final list of the team members is announced publicly. The aim is to have people representing technical leadership, security knowledge and infrastructure present with enough people to provide backup/coverage but keep the notification list small enough to minimise information risk and maintain trust.

YP Security Team members may resign at any time.

== Security Team Operations ==

The work of the Security Team might require high confidentiality. Team members are individuals selected by merit and do not represent the companies they work for. They do not share information about confidential issues outside of the team and do not hint about ongoing embargoes.

Team members can bring in domain experts as needed. Those people should be added to individual issues only and adhere to the same standards as the YP Security Team.

The YP security team organizes its meetings and communication as needed.

When the YP Security team receives a report about a potential security vulnerability, they quickly analyze and notify the reporter of the result. They might also request more information.

If the issue is confirmed and affects the code maintained by the YP, they confidentially notify maintainers of that code and work with them to prepare a fix.

If the issue is confirmed and affects an upstream project, the YP security team notifies the project. Usually, the upstream project analyzes the problem again. If they deem it a real security problem in their software, they develop and release a fix following their security policy. They may want to include the original reporter in the loop. There is also sometimes some coordination for handling patches, backporting patches etc, or just understanding the problem or what caused it.

The security policy of the upstream project might include a notification to Linux distributions or other important downstream projects in advance to discuss coordinated disclosure. These mailing lists are generally non-public. The YP Security Team participates in the discussion as needed. They might also include the YP maintainer of the affected package.

When the upstream project releases a version with the fix, they are responsible for contacting Mitre (cve.mitre.org) to get a CVE number assigned and the CVE record published.

When the fix is publicly available, the YP security team member or the package maintainer sends patches against the YP code base, following usual procedures, including public code review.

== Handling multi-project embargoes ==

In rare cases, a severe security issue affects multiple projects. This might be numerous projects having a similar issue because of design, coding pattern, or reuse of the same code (an example of this situation is CVE-2023-44487 where multiple web servers share a design weakness). It might also be a high-profile issue in a commonly used library (like OpenSSL). In such cases, the project, learning first about the issue, might decide to notify other affected projects confidentially so that they come up with a synchronized fix. It might also be the affected project informing major distributions to roll out the update simultaneously.

Such notifications happen over confidential, non-public means. Typically, the project initiating this "embargo" directly notifies a selected number of people from each project, including a subset of the security team. When Yocto Project is a part of such a notified group, developers prepare fixes on separate infrastructure and test it. They might also include additional developers and domain experts who can help with the fix and eventual regressions. When the embargo is lifted, they send a patch to the relevant public list, and the usual review process starts.

== Current Security Team Members ==

For secure communications, please send your messages encrypted using the GPG keys. Remember message headers are not encrypted so do not include sensitive information in the subject line.

* Richard Purdie '''<richard.purdie@linuxfoundation.org>'''
: [https://keys.openpgp.org/search?q=richard.purdie%40linuxfoundation.org Public key]

* Michael Halstead '''<mhalstead [at] linuxfoundation [dot] org>'''
: Public keys: [https://pgp.mit.edu/pks/lookup?op=vindex&search=0x3373170601861969 Michael Halstead] or [https://keyserver.ubuntu.com/pks/lookup?op=get&search=0xd1f2407285e571ed12a407a73373170601861969 Michael Halstead]

* Ross Burton '''<ross@burtonini.com>'''
: [https://keys.openpgp.org/search?q=ross%40burtonini.com Public key]

* Marta Rybczynska '''<marta DOT rybczynska [at] syslinbit [dot] com>'''
: [https://keys.openpgp.org/search?q=marta.rybczynska@syslinbit.com Public key]

* Paul Barker '''<paul [at] pbarker [dot] dev>'''
: [https://keys.openpgp.org/search?q=paul@pbarker.dev Public key]

Security private reporting

2026-05-19T11:07:59Z

Paul Barker:

Security private reporting

2026-05-19T10:49:59Z

Paul Barker: /* Current Security Team Members */

2026 Yocto Project Weekly Status Archive

2026-04-28T14:52:41Z

Paul Barker:

== 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

2021-07-27T16:06:27Z

Paul Barker: Created page with "== Yocto Project related talks at ELC 2021 == * [https://osselc21.sched.com/event/lAUP/bof-the-yocto-project-and-embedded-linux-armin-kuster-montavista-llc-nicolas-dechesne-l..."

== Yocto Project related talks at ELC 2021 ==

* [https://osselc21.sched.com/event/lAUP/bof-the-yocto-project-and-embedded-linux-armin-kuster-montavista-llc-nicolas-dechesne-linaro?iframe=no BoF: The Yocto Project and Embedded Linux - Armin Kuster, MontaVista, LLC & Nicolas Dechesne, Linaro]

* [https://osselc21.sched.com/event/lAMf/securing-a-yocto-based-distribution-the-case-of-allscenariosos-marta-rybczynska?iframe=no Securing a Yocto-based Distribution: The Case of AllScenariosOS - Marta Rybczynska]

* [https://osselc21.sched.com/event/lAMl/yocto-continuous-integration-in-a-kube-joshua-watt-garmin?iframe=no Yocto Continuous Integration in a Kube - Joshua Watt, Garmin]

* [https://osselc21.sched.com/event/lC8w/the-5-key-success-factors-to-deploy-yocto-for-production-grade-embeddediot-devices-adrien-leravat-witekio?iframe=no The 5 Key Success Factors to Deploy Yocto for “Production Grade” Embedded/IoT Devices - Adrien Leravat, Witekio]

* [https://osselc21.sched.com/event/lAMT/binary-artifacts-and-the-ease-of-use-onramp-for-the-yocto-project-bruce-ashfield-xilinx?iframe=no Binary Artifacts and the Ease of Use Onramp for the Yocto Project - Bruce Ashfield, Xilinx]

* [https://osselc21.sched.com/event/lAMW/a-tale-of-three-build-systems-building-a-custom-linux-os-for-beaglev-starlight-with-buildroot-isar-and-yocto-project-tim-orling-intel-corporation?iframe=no A Tale of Three Build Systems: Building a Custom Linux OS for BeagleV Starlight with Buildroot, Isar and Yocto Project - Tim Orling, Intel Corporation]

* [https://osselc21.sched.com/event/lAMi/practical-experience-with-linux-ab-upgrades-leon-anavi-konsulko-group?iframe=no Practical Experience with Linux A/B Upgrades - Leon Anavi, Konsulko Group]

* [https://osselc21.sched.com/event/lAMc/yocto-project-and-android-compare-and-contrast-chris-simmonds-2net?iframe=no Yocto Project and Android – Compare and Contrast - Chris Simmonds, 2net]

Project Users

2020-01-17T11:12:02Z

Paul Barker: /* Projects that use the Yocto Project */

It's hard to know which companies or projects use the Yocto Project since there is no requirement to tell us. This list is here to informally collate the companies, projects and products that use the Yocto Project in some way.

= Companies using the Yocto Project =

Semiconductor Vendors:
* AMD (Silver Member)
* ARM (Platinum Member)
* Intel (Platinum Member)
* NXP (Silver Member)
* Qualcomm
* Renesas (Gold Member)
* STMicroelectronics (Silver Member)
* Texas Instruments (Platinum Member)
* Xilinx (Platinum Member)

OSVs:
* ENEA (Silver Member)
* Linaro (Silver Member)
* Lineo (Silver Member)
* Mentor Graphics (Gold Member)
* Montavista (Silver Member)
* Wind River (Gold Member)

Others:
* Cisco (Platinum Member)
* Comcast (Platinum Member)
* Dell (Silver Member)
* Facebook (Platinum Member)
* Juniper (Gold Member)
* LG (Silver Member)
* Microsoft

= Products that use the Yocto Project =

* Comcast set top boxes
* LG TVs

= Projects that use the Yocto Project =

* [https://www.automotivelinux.org/ Automotive Grade Linux (AGL)]
* Comcast RDK
* OpenBMC
* Windows Subsystem Linux (v1+v2)
* [https://oryx-linux.org/ Oryx Linux]

Janitors

2013-09-19T13:11:33Z

Paul Barker: /* Style and Formatting */

__TOC__

The following tasks are intended to help people get started working with the Yocto Project. These tasks should not require a lot of context. Anyone with basic programming skills, experience working with Open Source software, and some time on their hands should be able to complete these.

When adding tasks, please be sure to follow this format:
* Task Title
** Difficulty: (Hard|Moderate|Easy)
** Estimate: 0-9 (Day|Hour)s?
** Submitter: IRC Handle
** Task item detail
** Task item detail

As these are meant to help people get started, tasks should be self-contained and doable without a lot of context dealing with bitbake based build systems. Re-writing the recipe parser in C is probably not a good fit for this task list.

= Tasks =
== Kernel ==
* Build kernel modules on target
** Difficulty: Moderate
** Estimate: 3 Days
** Submitter: dvhart
** Package up the kernel sysroot and make it available on the target. This should become a linux-headers package or similar.

== Build ==
* Ability to archive work dir
** Difficulty: Easy
** Estimate: 2 Days
** Submitter: LCS suggestion
** Add the ability to archive the work directory to handle the GPL compliance issue.

== Documentation ==
* Document undocumented variables according to bbvars.py
** Difficulty: Moderate
** Estimate: 1 Hour (per variable)
** Submitter: dvhart
** Start with the variables with the highest count
** First add a doctag to meta/conf/documentation.conf
** Second prepare a patch to documentation/poky-ref-manual/poky-ref-manual.xml
$ scripts/contrib/bbvars.py -d documentation/poky-ref-manual/poky-ref-manual.xml -t meta/conf/documentation.conf -m meta

* Rewrite bbvars.py to use bitbake to find variables
** Difficulty: Hard
** Estimate: 3 Days
** Submitter: dvhart
** bbvars.py does a rather dumb regex search for things vaguely resembling variables, the bitbake parser knows how to do this properly.

== Compliance ==
* Fix compliance issues
** Difficulty: Moderate
** Estimate: 3 days
** Submitter: jnfleisc
** This is a task to address the compliance issues found when the LTP and POSIX compliance tests were run against a build created using Yocto Project.
** The test results from running these tests against a build created using Yocto Project are at https://wiki.yoctoproject.org/wiki/Posix_result and https://wiki.yoctoproject.org/wiki/LTP_result.

== Style and Formatting ==
* Review recipes for compliance with the [[Recipe & Patch Style Guide]]
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Possibly look at reviving the old stylisation script (http://git.openembedded.org/openembedded/tree/contrib/oe-stylize.py). It would need bringing up-to-date with the current styleguide and then submitting to oe-core

* Convert short DESCRIPTION values (< 80 characters) to set SUMMARY instead
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Possibly write a script to use 'bitbake -e' to get the DESCRIPTION value and then check it's length

* Review naming of "files" directories
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** If there is only one recipe in the containing directory (like x_0.bb and x_1.bb) the files directory should be called x, if the patches are only for version 1 of x then the files directory should be called x-1. Also check if the patches in it are still applied or only deadwood.
** Possibly start by running "find -type d -name files" at the root of openembedded-core and meta-openembedded

* Run a spell checker on descriptive variables and comments
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Probably not the most interesting task!

== Misc ==
* Write a friendly IRC bot for the #yocto channel
** Difficultly: Moderate
** Estimate: 1 Week (requires feedback and iterative development)
** Submitter: dvhart
** Possibly named "yocti"
** The bot should be either snarky or obsequious
** The bot should respond to at least the following commands:
*** yocti help (send help privately to user on commands)
*** yocti quiet (no more public output, should still respond to private msgs)
*** yocti speak (start responding again)
*** bug ### (provide a URL to the bug)
*** bzinfo ### (display the bug summary, and possibly whiteboard)
*** git ### (display the git commit subject)
*** bbvar VAR_NAME (display the doctag)
** The bot could also respond to things like:
*** user++ (track kudos points per user per day)
*** user-- (remove kudos points)
*** kudos (display the current kudos scoreboard)
*** .*someday.* (suggest the user add a task to the Janitors list)
*** I'm sure there are more, current recipe version, maintainer of a recipe, etc.

== Janitor entries in Bugzilla ==

{{#bugzilla:
|columns=id,to,estimated,summary,whiteboard,milestone,status
|noresultsmessage=None
|status=NEW,ACCEPTED,IN PROGRESS DESIGN,NEEDINFO
|severity=janitors
}}

Janitors

2013-09-19T13:10:12Z

Paul Barker:

__TOC__

The following tasks are intended to help people get started working with the Yocto Project. These tasks should not require a lot of context. Anyone with basic programming skills, experience working with Open Source software, and some time on their hands should be able to complete these.

When adding tasks, please be sure to follow this format:
* Task Title
** Difficulty: (Hard|Moderate|Easy)
** Estimate: 0-9 (Day|Hour)s?
** Submitter: IRC Handle
** Task item detail
** Task item detail

As these are meant to help people get started, tasks should be self-contained and doable without a lot of context dealing with bitbake based build systems. Re-writing the recipe parser in C is probably not a good fit for this task list.

= Tasks =
== Kernel ==
* Build kernel modules on target
** Difficulty: Moderate
** Estimate: 3 Days
** Submitter: dvhart
** Package up the kernel sysroot and make it available on the target. This should become a linux-headers package or similar.

== Build ==
* Ability to archive work dir
** Difficulty: Easy
** Estimate: 2 Days
** Submitter: LCS suggestion
** Add the ability to archive the work directory to handle the GPL compliance issue.

== Documentation ==
* Document undocumented variables according to bbvars.py
** Difficulty: Moderate
** Estimate: 1 Hour (per variable)
** Submitter: dvhart
** Start with the variables with the highest count
** First add a doctag to meta/conf/documentation.conf
** Second prepare a patch to documentation/poky-ref-manual/poky-ref-manual.xml
$ scripts/contrib/bbvars.py -d documentation/poky-ref-manual/poky-ref-manual.xml -t meta/conf/documentation.conf -m meta

* Rewrite bbvars.py to use bitbake to find variables
** Difficulty: Hard
** Estimate: 3 Days
** Submitter: dvhart
** bbvars.py does a rather dumb regex search for things vaguely resembling variables, the bitbake parser knows how to do this properly.

== Compliance ==
* Fix compliance issues
** Difficulty: Moderate
** Estimate: 3 days
** Submitter: jnfleisc
** This is a task to address the compliance issues found when the LTP and POSIX compliance tests were run against a build created using Yocto Project.
** The test results from running these tests against a build created using Yocto Project are at https://wiki.yoctoproject.org/wiki/Posix_result and https://wiki.yoctoproject.org/wiki/LTP_result.

== Style and Formatting ==
* Review recipes for compliance with the [[Recipe & Patch Style Guide]]
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Possibly look at reviving the old stylisation script ([[http://git.openembedded.org/openembedded/tree/contrib/oe-stylize.py]]). It would need bringing up-to-date with the current styleguide and then submitting to oe-core

* Convert short DESCRIPTION values (< 80 characters) to set SUMMARY instead
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Possibly write a script to use 'bitbake -e' to get the DESCRIPTION value and then check it's length

* Review naming of "files" directories
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** If there is only one recipe in the containing directory (like x_0.bb and x_1.bb) the files directory should be called x, if the patches are only for version 1 of x then the files directory should be called x-1. Also check if the patches in it are still applied or only deadwood.
** Possibly start by running "find -type d -name files" at the root of openembedded-core and meta-openembedded

* Run a spell checker on descriptive variables and comments
** Difficulty: Easy
** Estimate: < 1 week
** Submitter: paulbarker
** Probably not the most interesting task!

== Misc ==
* Write a friendly IRC bot for the #yocto channel
** Difficultly: Moderate
** Estimate: 1 Week (requires feedback and iterative development)
** Submitter: dvhart
** Possibly named "yocti"
** The bot should be either snarky or obsequious
** The bot should respond to at least the following commands:
*** yocti help (send help privately to user on commands)
*** yocti quiet (no more public output, should still respond to private msgs)
*** yocti speak (start responding again)
*** bug ### (provide a URL to the bug)
*** bzinfo ### (display the bug summary, and possibly whiteboard)
*** git ### (display the git commit subject)
*** bbvar VAR_NAME (display the doctag)
** The bot could also respond to things like:
*** user++ (track kudos points per user per day)
*** user-- (remove kudos points)
*** kudos (display the current kudos scoreboard)
*** .*someday.* (suggest the user add a task to the Janitors list)
*** I'm sure there are more, current recipe version, maintainer of a recipe, etc.

== Janitor entries in Bugzilla ==

{{#bugzilla:
|columns=id,to,estimated,summary,whiteboard,milestone,status
|noresultsmessage=None
|status=NEW,ACCEPTED,IN PROGRESS DESIGN,NEEDINFO
|severity=janitors
}}