Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(281 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status November 8th, 2022 ==
== Yocto Project Status 21 July 2026 ==
Current Dev Position: YP 4.2 M1<br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: 5th December 2022 YP 4.2 M1 Build<br/>
Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday November 10th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 23rd July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday November 8th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 21st July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 23rd July 10am GMT and Monday 27th July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.5 was released.
*YP 6.0.2 has been released
*There have been a number of important CVEs (e.g. the recent openssl one) which are merging to branches as they are ready, we suggest people keep an eye on the branches.
*YP 5.0.19 is due to release
*Patches continue to flow steadily into master.
*YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
*The CVEs in master continue to fall and patches are flowing into the other stable branches.
*Some invasive LICENSE changes have merged into master:
*We are making some progress with patch submission upstream, including gcc. This does sometimes mean helping resolve other issues those patches then introduce which can be time consuming, thanks go to all helping work on this.
**We now require the LICENSE field to match SPDX identifiers.  
*The number of AB-INT issues continues to be of concern, we’re working to try and resolve the most frequently occurring issues to enable cleaner test runs but could use help.
**The build will issue warnings when this isn’t the case.
*We do have a growing number of bugs in bugzilla, for example a number of rust bugs were opened recently. We are probably at an all time low on numbers of people able to work on bugs too which is a worrying combination.
**Non SPDX licenses will need to be of the form LicenseRef-XXX
*If anyone is working on features for 4.2, please do let us know about them so we can plan accordingly. Even an idea of what is coming is helpful to plan.
**CLOSED is no longer a valid value.  
**‘WITH’ license exceptions are now supported
Big thanks for Joshua for getting us to the point where we can finally clean this up!
*We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
*A couple of further pseudo related issues were identified, one with linkat flags and one with openat2 (tar related/triggered). We hope to have patches merged soon.
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. The review calls are running out of time each meeting which limits progress.
**We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
**several qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.


'''Ways to contribute:'''<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.2 See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_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 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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*Help us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
 
'''New to the project?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
 
'''Tracking Metrics:'''<br/>
*WDD 2719 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1019 (last week 1019+)
**Patches in the Pending State: 144 (14%) [last week 145 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 4.2 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 4.2 M1 build date 2022/12/05
*6.1 M2:
*YP 4.2 M1 Release date 2022/12/16
**Build Date: w/c 2026-07-20
*YP 4.2 M2 build date 2023/01/23
**Release Date: w/c 2026-08-03
*YP 4.2 M2 Release date 2023/02/03
*6.1 M3:
*YP 4.2 M3 build date 2023/02/20
**Build Date: w/c 2026-08-31
*YP 4.2 M3 Release date 2023/03/03
**Release Date: w/c 2026-09-14
*YP 4.2 M4 build date 2023/04/03
*6.1.0:
*YP 4.2 M4 Release date 2023/04/28
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02


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


*YP 4.0.5 is released.
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 4.1.1 build date 2022/11/14
*YP 4.1.1 Release date 2022/11/25
*YP 3.1.21 build date 2022/11/28
*YP 3.1.21 Release date 2022/12/09
*YP 4.0.6 build date 2022/12/12
*YP 4.0.6 Release date 2022/12/23
*YP 4.1.2 build date 2023/01/09
*YP 4.1.2 Release date 2023/01/20
*YP 3.1.22 build date 2023/01/16
*YP 3.1.22 Release date 2023/01/27
*YP 4.0.7 build date 2023/01/30
*YP 4.0.7 Release date 2023/02/10
*YP 3.1.23 build date 2023/02/13
*YP 3.1.23 Release date 2023/02/24
*YP 4.0.8 build date 2023/02/27
*YP 4.0.8 Release date 2023/03/10
*YP 4.1.3 build date 2023/03/06
*YP 4.1.3 Release date 2023/03/17
*YP 3.1.24 build date 2023/03/20
*YP 3.1.24 Release date 2023/03/31
*YP 4.0.9 build date 2023/04/10
*YP 4.0.9 Release date 2023/04/21
*YP 4.1.4 build date 2023/05/01
*YP 4.1.4 Release date 2023/05/13
*YP 3.1.25 build date 2023/05/08
*YP 3.1.25 Release date 2023/05/19
*YP 4.0.10 build date 2023/05/15
*YP 4.0.10 Release date 2023/05/26
 
'''Tracking Metrics:'''<br/>
*WDD 2424 (last week 2412) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1201 (last week 1207)
**Patches in the Pending State: 296 (25%) [last week 309 (26%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''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 78: Line 77:


== 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:50, 21 July 2026

Yocto Project Status 21 July 2026

Current Dev Position: YP 6.1 M2
Next Deadline: YP 6.1 M2: w/c 2026-07-20

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.0.2 has been released
  • YP 5.0.19 is due to release
  • YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
  • Some invasive LICENSE changes have merged into master:
    • We now require the LICENSE field to match SPDX identifiers.
    • The build will issue warnings when this isn’t the case.
    • Non SPDX licenses will need to be of the form LicenseRef-XXX
    • CLOSED is no longer a valid value.
    • ‘WITH’ license exceptions are now supported

Big thanks for Joshua for getting us to the point where we can finally clean this up!

  • We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
  • Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
  • A couple of further pseudo related issues were identified, one with linkat flags and one with openat2 (tar related/triggered). We hope to have patches merged soon.
  • Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. The review calls are running out of time each meeting which limits progress.
    • We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
    • several qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • siggen reset issues (“ResourceWarning: unclosed transport”)
    • groff build race issues
    • intermittent ptest failures in many recipes
  • For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

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

Upcoming dot releases:

  • YP 5.0.19 due to release
    • Release Date w/c 2026-07-13
  • YP 6.0.3
    • Build Date w/c 2026-08-10
    • Release Date w/c 2026-08-24
  • YP 5.0.20
    • Build Date w/c 2026-08-17
    • Release Date w/c 2026-08-31

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