Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(354 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Jan. 25th, 2022 ==
== Yocto Project Status 19 May 2026 ==
Current Dev Position: YP 3.5 M3<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: 21th Feb. 2022 YP 3.5 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 Jan. 27th at 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)
*Monthly Project Meeting Tuesday Feb. 1st 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)
*Weekly Engineering Sync Tuesday Jan. 25th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 21st May 10am GMT and Monday 25th May 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.5 M2 finally built today after a number of autobuilder build issues and is now in QA
*YP 6.0 was released, thanks everyone who contributed!
*Building M2 was fairly painful as various sstate error/warning code paths were exposed in release builds, there were some infrastructure issues, some test reporting bugs and other bugs like that in systemtap on arm and a reproducibility issue, all of which combined to break the release builds in different ways. Hopefully most of these are now addressed or in the process of being fixed/tested.
*YP 5.0.18 is in QA.
*Upstream glibc are planning to remove prelink support in 2.35 with patches proposed on their mailing list.https://sourceware.org/pipermail/libc-alpha/2022-January/135565.html The project is unlikely to be able to continue to maintain any prelink support once this happens and we will therefore remove our prelink support before the next LTS unless the situation changes and maintainers step forward.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*An email proposing inclusive language changes https://lists.openembedded.org/g/openembedded-core/message/160881 for bitbake and OE-Core has been sent to the community for review. The aim is to implement this before M3.
*Intermittent build failures continue to be problematic:
*The debian9 autobuilder issues were hardware related and fixes for the arm systemtap issues are being tested but autobuilder intermittent issues are still at an all time high.
**several qemu ‘hang’ type issues
*CVE metrics improved for master https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive but work still remains on the various stable branches which have high counts.
**sometimes yocto-check-layer is showing checksum mismatch 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
**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:'''<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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing


'''YP 3.5 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 3.5 M2 is built
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 3.5 M2 Release date 2022/01/28
 
*YP 3.5 M3 build date 2022/02/21
'''Tracking Metrics:'''<br/>
*YP 3.5 M3 Release date 2022/03/04
*WDD 2673 (last week 2688) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.5 M4 build date 2022/04/04
*OE-Core/Poky Patch Metrics
*YP 3.5 M4 Release date 2022/04/29
**Total patches found: 1083 (last week 1087)
**Patches in the Pending State: 148 (14%) [last week 146 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.14 build date 2022/01/24
*YP 5.3.4 was released.
*YP 3.1.14 Release date 2022/02/04
*YP 5.0.18 is in QA.
*YP 3.4.2 build date 2022/02/07
*YP 6.0.1
*YP 3.4.2 Release date 2022/02/18
**Build Date  2026-05-18
*YP 3.3.5 build date 2022/02/14
**Release Date 2026-06-01
*YP 3.3.5 Release date 2022/02/25
*YP 5.0.19
*YP 3.1.15 build date 2022/03/14
**Build Date  2026-06-30
*YP 3.1.15 Release date 2022/03/25
**Release Date 2026-07-13
*YP 3.4.3 build date 2022/03/21
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 3.4.3 Release date 2022/04/01
*YP 3.3.6 build date 2022/03/28
*YP 3.3.6 Release date 2022/04/08
*YP 3.1.16 build date 2022/04/25
*YP 3.1.16 Release date 2022/05/06
 
'''Tracking Metrics:'''<br/>
*WDD 2700 (last week 2675) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
**Total patches found: 1230 (last week 1229)
**Patches in the Pending State: 340 (28%) [last week 345 (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 57: 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"