Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(491 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Nov. 24, 2020 ==
== Yocto Project Status 9 June 2026 ==
Current Dev Position: YP 3.3 M1 development<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: 7th December 2020 YP 3.3 M1 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 Nov. 26th at 7:30am 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 Dec. 1st at 8am 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 Nov. 24th at 8am 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/>
*YP 3.1.4 should build this week now the CVE work has reached a logical point for the build.
*YP 5.0.18 has been released
*Master has now opened up for 3.3 development and patches are merging.
*YP 6.0.1 is in QA.
*Dunfell has seen a number of CVE report improvements (count of 202 down to 71 in the past three months), either through patches/upgrades or in corrections to the CVE database information, thanks Steve and all those who’ve helped.
*YP 6.1 M1 is due to build this week
*The dunfell CVE improvements have also drastically improved the situation with master.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*Intermittent autobuilder issues continue to occur. 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
*Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
*The SWAT team has been re-established. A new mailing has been created as swat@lists.yoctoproject.org to support this and a number of member organisations have agreed to help staff this team. We are in the process of getting the process running again and in due course there will be the option of other community members being able to help too. The tools and processes are under review to allow us to optimise the process. Thanks to the members and everyone participating to make this happen!
*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
*There are big improvements underway to the autobuilder display of builds, for example, https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/2744 which shows many more individual steps with more detailed information. *There still needs to be improvements to the configuration markup to make best use of this (help welcome!) but this should significantly improve the autobuilder readability.
*We have changed the xz and zstd decompression dependencies to make the build slightly more efficient and use the host tools for decompression
*There are other ideas being discussed around autobuilder usability improvements such as remembering field history (patch submitted to upstream buildbot), better success/failure count reporting and potential replacement of the buildlog wiki page and autobuilder integration with a specific purpose django app.
*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:'''<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.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_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.
*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


'''YP 3.3 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.3 M1 build date 2020/12/07
*WDD 2655 (last week 2630) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.3 M1 Release date 2020/12/18
*OE-Core/Poky Patch Metrics
*YP 3.3 M2 build date 2021/01/18
**Total patches found: 1056 (last week 1087)
*YP 3.3 M2 Release date 2021/01/29
**Patches in the Pending State: 147 (14%) [last week 147 (14%)]
*YP 3.3 M3 build date 2021/03/01
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
*YP 3.3 M3 Release date 2021/03/12
*YP 3.3 M4 build date 2021/04/05
*YP 3.3 M4 Release date 2021/04/30


'''Planned upcoming dot releases:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 3.1.4 build date 2020/11/2
*6.1 M1:
*YP 3.1.4 release date 2020/11/13
**Build Date: w/c 2026-06-08
*YP 3.2.1 build date 2020/11/16
**Release Date: w/c 2026-06-22
*YP 3.2.1 release date 2020/12/4
*6.1 M2:
*YP 3.1.5 build date 2021/01/11
**Build Date: w/c 2026-07-20
*YP 3.1.5 release date 2021/01/22
**Release Date: w/c 2026-08-03
*YP 3.2.2 build date 2021/02/08
*6.1 M3:
*YP 3.2.2 release date 2021/02/19
**Build Date: w/c 2026-08-31
*YP 3.1.6 build date 2021/02/22
**Release Date: w/c 2026-09-14
*YP 3.1.6 release date 2021/03/05
*6.1.0:
*YP 3.1.7 build date 2021/03/22
**Build Date (M4): w/c 2026-10-12
*YP 3.1.7 release date 2021/04/02
**Release Date: w/c 2026-11-02


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2532 (last week 2534) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 6.0.1 is in QA.
*Poky Patch Metrics 
*YP 6.0.2
**Total patches found: 1279 (last week 1275)
**Build Date w/c 2026-06-23
**Patches in the Pending State: 497 (39%) [last week 497 (39%)]
**Release Date w/c 2026-07-06
*YP 5.0.19
**Build Date w/c 2026-06-30
**Release Date w/c 2026-07-13
*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 58: 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]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 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"