Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(183 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status November 14th, 2023 ==
== Yocto Project Status 21 July 2026 ==
Current Dev Position: YP 5.0 M1<br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: 4th December 2023 YP 5.0 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 16, 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 14th at 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)
<br/>
'''Key Status/Updates:'''<br/>
*YP 4.3 was released, thanks to everyone who contributed!
*YP 4.0.14 is out of QA and due for release
*YP 3.1.29 is out of QA and due for release after investigation of vim reproducibility issues
*YP 4.2.4 is currently being built
*bitbake’s hash equivalence server has undergoing a lot of development (thanks Joshua!) including:
**websockets support
**user authentication/permissions support
**entry removal API addition
**support for multiple database backends
*master saw various upgrades for the kernel and other components
*the length of time rebuilds are taking on the autobuilder is a concern, world can take 16 hours as can oe-selftest with a cold sstate cache


'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


<br/>
'''Key Status/Updates:'''<br/>
*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:'''<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: patchtest, layerindex, 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 4.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_Unassigned_Enhancements.2FBugs
*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.


'''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 5.0 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 5.0 M1 build date 2023/12/04
*6.1 M2:
*YP 5.0 M1 Release date 2023/12/15
**Build Date: w/c 2026-07-20
*YP 5.0 M2 build date  2024/01/15
**Release Date: w/c 2026-08-03
*YP 5.0 M2 Release date 2024/01/24
*6.1 M3:
*YP 5.0 M3 build date  2024/02/19
**Build Date: w/c 2026-08-31
*YP 5.0 M3 Release date 2024/03/01
**Release Date: w/c 2026-09-14
*YP 5.0 M4 build date  2024/04/01
*6.1.0:
*YP 5.0 M4 Release date 2024/04/30
**Build Date (M4): w/c 2026-10-12
 
**Release Date: w/c 2026-11-02


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.29 build date 2023/10/30
*YP 5.0.19 due to release
*YP 3.1.29 Release date 2023/11/10
**Release Date w/c 2026-07-13
*YP 4.0.14 build date 2023/11/06
*YP 6.0.3
*YP 4.0.14 Release date 2023/11/17
**Build Date w/c 2026-08-10
*YP 4.2.4 build date 2023/11/13
**Release Date w/c 2026-08-24
*YP 4.2.4 Release date 2023/11/24
*YP 5.0.20
*YP 4.3.1 build date 2023/11/27
**Build Date w/c 2026-08-17
*YP 4.3.1 Release date 2023/12/08
**Release Date w/c 2026-08-31
*YP 3.1.30 build date 2023/12/11
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29
*YP 4.3.2 build date 2024/01/08
*YP 4.3.2 Release date 2024/01/19
*YP 3.1.31 build date 2024/01/22
*YP 3.1.31 Release date 2024/02/02
*YP 4.0.16 build date 2024/01/29
*YP 4.0.16 Release date 2024/02/09
*YP 4.3.3 build date 2024/02/12
*YP 4.3.3 Release date 2024/02/23
*YP 3.1.32 build date 2024/03/04
*YP 3.1.32 Release date 2024/03/15
*YP 4.0.17 build date 2024/03/11
*YP 4.0.17 Release date 2024/03/22
*YP 4.3.4 build date 2024/03/25
*YP 4.3.4 Release date 2024/04/05
*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/>
*WDD 2533 (last week 2540) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1177 (last week 1173)
**Patches in the Pending State: 253 (21%) [last week 253 (22%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


*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 94: 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]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 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"