Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(291 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status August 23rd, 2022 ==
== Yocto Project Status 21 April 2026 ==
Current Dev Position: YP 4.1 M3 (Feature Freeze)<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: 22nd August 2022 YP 4.1 M3 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 August 25th 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 August 23rd 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.3 was released
*YP 5.0.17 was released
*YP 3.1.19 has been built and is in QA
*YP 6.0 M3 was released
*We are now at feature freeze for 4.1.
*YP 4.0.35 is in QA
*The 4.1 build is planned as soon as we resolve the status of some pending patches. The known remaining issues are the rust automated tests, layer setup changes and gcc and rust version upgrades. We also need to fix some autobuilder errors such as the llvm reproducibility issue with mesa.
*YP 6.0 M4 is due to build
*Several patch series have been problematic in the last week which has put strain on our infrastructure, particularly the binutils upgrade.
*We continue to triage the CVEs being reported by the new tooling.
*The CVE count for master rose sharply again this week due to multiple issues in vim and tiff. The vim issues have been patched, tiff hasn’t as yet.
*Various fixes have merged or are planned to merge before the M4 release build:
*We have seen a sharp rise in the number of patches in OE-Core, particularly related to changes in new clang versions. Many of these have been submitted upstream and/or have good reasons for being present but we need to continue to work to reduce our patch burden.
**Various CVE issue resolutions from CVE triage
*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
**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:'''<br/>
'''Ways to contribute:'''<br/>
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 that are currently unassigned for YP 4.1 See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enhancements.2FBugs
*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/
*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.
*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.
*Help us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing


'''YP 4.1 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 4.1 M3 build date 2022/08/22
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 4.1 M3 Release date 2022/09/02
*YP 4.1 M4 build date 2022/10/03
*YP 4.1 M4 Release date 2022/10/28
 
'''Upcoming dot releases:'''<br/>
*YP 4.0.3 is released
*YP 3.1.19 is in QA
*YP 3.1.19 Release date 2022/09/09
*YP 4.0.4 build date 2022/09/19
*YP 4.0.4 Release date 2022/09/30
*YP 3.1.20 build date 2022/10/10
*YP 3.1.20 Release date 2022/10/21
*YP 4.0.5 build date 2022/10/31
*YP 4.0.5 Release date 2022/11/11


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2482 (last week 2447) (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: 1212 (last week 1188)
**Total patches found: 1078 (last week 1072)
**Patches in the Pending State: 329 (27%) [last week 322 (28%)]
**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 52: Line 61:


== Archives ==
== 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]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2021 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"