Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(344 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Mar. 1st, 2022 ==
== Yocto Project Status 9 June 2026 ==
Current Dev Position: YP 3.5 M4<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: 4th Apr. 2022 YP 3.5 M4 build<br/>
Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Mar. 3rd at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 11th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Mar. 1st at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 9th June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Mar. 8th at 8 am 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)
*Twitch -  See https://www.twitch.tv/theyoctojester
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We are now at feature freeze for 3.5, our next LTS release
*YP 5.0.18 has been released
*YP 3.3.5 is out of QA and pending release approval
*YP 6.0.1 is in QA.
*Inclusive language changes have merged however there are still:
*YP 6.1 M1 is due to build this week
**Incompatible license related variable changes
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
**Function variable name changes needed
*Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
**No migration documentation or documentation of the changes
*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
**No documentation of the bitbake rename code
*We have changed the xz and zstd decompression dependencies to make the build slightly more efficient and use the host tools for decompression
**No updates to the manual for the variable renames
*Intermittent build failures continue to be problematic and unchanged from last week:
We do need people to pull things together and finish things off, help in doing that is needed and much appreciated.
**several qemu ‘hang’ type issues
*There is a pending patch to warn about old style license identifiers pending in master-next and due to be posted for review. On balance this is probably a good thing to get into the LTS but we’re open to input on that.
**sometimes yocto-check-layer is showing checksum mismatch issues
*The incompatible license changes will mean anyone using those variables will need to update what they’re doing carefully. Patches in master-next now pass testing and are due to be posted on the mailing list.
**siggen reset issues (“ResourceWarning: unclosed transport”)
*The python build process change to use wheels has merged. That change has caused some disruption but was close enough to being ready it seemed worth making the final push for inclusion.
**groff build race issues
*The infrastructure move was successful and all services should be restored. There are some networking issues occurring on autobuilder builds which are preventing release builds at this time and are being looked into.
**intermittent ptest failures in many recipes
*As such, the M3 release build will likely happen late this week or early next week.
*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
*If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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


'''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 3.5. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_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
 
'''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 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/


'''YP 3.5 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 3.5 M3 build date 2022/02/21
*6.1 M1:
*YP 3.5 M3 Release date 2022/03/04
**Build Date: w/c 2026-06-08
*YP 3.5 M4 build date 2022/04/04
**Release Date: w/c 2026-06-22
*YP 3.5 M4 Release date 2022/04/29
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.3.5 is out of QA
*YP 6.0.1 is in QA.
*YP 3.3.5 Release date 2022/02/25
*YP 6.0.2
*YP 3.1.15 build date 2022/03/14
**Build Date w/c 2026-06-23
*YP 3.1.15 Release date 2022/03/25
**Release Date w/c 2026-07-06
*YP 3.4.3 build date 2022/03/21
*YP 5.0.19
*YP 3.4.3 Release date 2022/04/01
**Build Date w/c 2026-06-30
*YP 3.3.6 build date 2022/03/28
**Release Date w/c 2026-07-13
*YP 3.3.6 Release date 2022/04/08
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 3.1.16 build date 2022/04/25
*YP 3.1.16 Release date 2022/05/06
 
'''Tracking Metrics:'''<br/>
*WDD 2679 (last week 2652) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
**Total patches found: 1202 (last week 1202)
**Patches in the Pending State: 336 (28%) [last week 334 (28%)]


'''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 61: Line 70:


== 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 08:13, 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:

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:

New to the project?

Tracking Metrics:

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:

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