Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(133 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 2nd, 2024 ==
== Yocto Project Status 21 April 2026 ==
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<br/>
Next Deadline: YP 6.0 M4 Build Date 2026-04-20<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday April 4th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Apr. 23rd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday April 2nd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday Apr. 21st 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*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/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.17 has been released.
*YP 5.0.17 was released
*YP 4.3.4 is in QA and is the final planned nanbield release.
*YP 6.0 M3 was released
*YP 5.0 rc1 is now due to build when ready.
*YP 4.0.35 is in QA
*Steve is taking patches for Dunfell until around April 8 in preparation for an April 15 build. This will be the last release of dunfell.
*YP 6.0 M4 is due to build
*5.0 build status:
*We continue to triage the CVEs being reported by the new tooling.
**The opkg lock issue has been worked around for now in the run-postinsts script
*Various fixes have merged or are planned to merge before the M4 release build:
**An intermittent oe-selftest failure (sstatetests hang) was tracked down to a race in tinfoil event handling.
**Various CVE issue resolutions from CVE triage
**The public hash equivalence server changes aren’t ready yet unfortunately
**Reproducibility issues with strace/apr-util
**There are issues with the size of the buildhistory repository which is being split up, this needs to happen before we can build the release.
**Make race in groff
**A key worry now is the documentation for the release, especially given it is an LTS. There are emails on the docs list about this, help is much appreciated. This will now be the main delay on the release timeframe.
**Shadow-native tallylog issue fix
*A new yocto-status https://lists.yoctoproject.org/g/yocto-status/topics mailing list has been created where we plan to send just the project weekly status reports and any other suitable updates on the project. This should help those who found the traffic of the other mailing lists too much.
**Upgrade of barebox to align with an LTS release
*A yocto-patches https://lists.yoctoproject.org/g/yocto-patches/topics mailing list has been setup and patches that used to go to the yocto@ list will be migrating over to this new list, making yocto@ a bit more friendly for questions and discussions.
**Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
*Some other obsolete mailing lists were removed or made read-only to try and make it easier for people to find the right place to see/send things.
**Sbom-cve-check upgrade (along with dependencies)
*Debian 12 and Fedora 40 containers have been added to crops (Thanks Rob Wolley)
*Issues still pending:
*All the crops yocto-base containers now include python3-virtualenv
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
*The “Binary Distro” work is now well underway and there are PR Server passthrough patches ready for review. The wiki page https://wiki.yoctoproject.org/wiki/Binary_Distro_Prototype#Policies_and_Processes has had a number of policy/process proposals documented, at least as a first pass. Help is welcome to help improve these, or highlight where further documentation is needed.
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
*One year after the original linux.com article, an update was published: https://www.yoctoproject.org/blog/2024/03/28/maintainer-confidential-challenges-and-opportunities-one-year-on/
**Intermittent wic failures on the autobuilder
*There was a significant security issue with xz release tarballs. We never merged the affected version and it was never in any of our main branches but we did test it on the autobuilder and saw build failures. We continue to watch for information on any potential implications of that. We have removed the compromised tarballs from our mirrors.
*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
*We continue to watch the NIST NVD (CVE database) situation, the recent update didn’t clarify much. Unfortunately there doesn’t appear to be a clear path forward as yet.
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:'''<br/>
'''Ways to contribute:'''<br/>
*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!
*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 bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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/
*There are bugs that are currently unassigned for YP 5.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
*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.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*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.


'''YP 5.0 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 5.0 M4 build date  2024/04/01
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 5.0 M4 Release date 2024/04/30
 
'''Upcoming dot releases:'''<br/>
*YP 4.0.17 is released.
*YP 4.3.4 is in QA.
*YP 3.1.33 build date 2024/04/15
*YP 3.1.33 Release date 2024/04/26
*YP 4.0.18 build date 2024/04/22
*YP 4.0.18 Release date 2024/05/03
*YP 4.0.19 build date 2024/06/03
*YP 4.0.19 Release date 2024/06/14


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2681 (last week 2703) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2790 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1173 (last week 1156)
**Total patches found: 1078 (last week 1072)
**Patches in the Pending State: 249 (21%) [last week 249 (22%)]
**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''Upcoming dot releases:'''<br/>
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 63: Line 61:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]

Latest revision as of 14:47, 21 April 2026

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:

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:

New to the project?

Tracking Metrics:

Upcoming dot releases:

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

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86807"