Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(294 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status August 30th, 2022 ==
== Yocto Project Status 19 May 2026 ==
Current Dev Position: YP 4.1 M3 (Feature Freeze)<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: 22nd August 2022 YP 4.1 M3 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 September 1st  7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 21st May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday August 30th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 19th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 21st May 10am GMT and Monday 25th May 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 3.1.19 was released
*YP 6.0 was released, thanks everyone who contributed!
*We are now at feature freeze for 4.1 but M3 has not been built yet.
*YP 5.0.18 is in QA.
*We are trying to prepare for the M3 build but the status of too many issues remains uncertain. In particular:
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
**llvm buildpaths patch was requested to be rewritten and the rewrite doesn’t work
*Intermittent build failures continue to be problematic:
**rust ppc patch was deemed incorrect
**several qemu ‘hang’ type issues
**layer setup changes didn’t test successfully
**sometimes yocto-check-layer is showing checksum mismatch issues
**rust SDK relocation patch is still in progress
**siggen reset issues (“ResourceWarning: unclosed transport”)
**concerns were raised over the rust crossbeam-utils atomics workaround
**groff build race issues
*In addition, several other high priority (release blocking) bugs were identified in bug triage, particularly issues which are occurring intermittently but regularly and hence causing failed builds. Richard and Ross own the majority but can’t handle all these at once and rather depressingly, there was nobody to take ownership of some of them. The current list of open high bugs:
**intermittent ptest failures in many recipes
**perl builds hanging indefinitely: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14902
*Master (blacksail) is open for new development
**cve checking crashing intermittently with database issues: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14899
*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
**ptest in gcrypt intermittently but regularly failing on arm: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14800
*We are updating the project’s security team and welcome nominations and/or feedback: https://lists.openembedded.org/g/openembedded-architecture/topic/119388716
**build path corruption when llvm is used to build mesa: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14897
*Monday 25th May is a public holiday in the UK and USA so there will be no patch review call.
**ptest infrastructure issue which stops us debugging an intermittent failure in lttng: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14901
**intermittent rust SDK host library corruption: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14892
**no automated mechanism to compare releases for ptest regressions: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14897
*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


'''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 3.1.19 is released
*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 2469 (last week 2482) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2673 (last week 2688) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1224 (last week 1212)
**Total patches found: 1083 (last week 1087)
**Patches in the Pending State: 329 (27%) [last week 329 (27%)]
**Patches in the Pending State: 148 (14%) [last week 146 (13%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''Upcoming dot releases:'''<br/>
*YP 5.3.4 was released.
*YP 5.0.18 is in QA.
*YP 6.0.1
**Build Date  2026-05-18
**Release Date 2026-06-01
*YP 5.0.19
**Build Date  2026-06-30
**Release Date 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 59: Line 56:


== 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, 19 May 2026

Yocto Project Status 19 May 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 6.0 was released, thanks everyone who contributed!
  • YP 5.0.18 is in QA.
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
  • Intermittent build failures continue to be problematic:
    • 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
  • Master (blacksail) is open for new development
  • 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
  • We are updating the project’s security team and welcome nominations and/or feedback: https://lists.openembedded.org/g/openembedded-architecture/topic/119388716
  • Monday 25th May is a public holiday in the UK and USA so there will be no patch review call.

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