Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(636 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 30, 2019 ==
== Yocto Project Status 9 June 2026 ==
Current Dev Position: YP 2.8 M3<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: YP 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, 2019<br/>
Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
 
*Bug Triage meeting - Thursday 11th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*SWAT lead is currently: Paul
*Weekly Project Engineering Sync - Tuesday 9th June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*SWAT team rotation: Paul -> Ross on Aug. 2, 2019
*Yocto Project Patch Review - Thursday 11th June 10am GMT and Monday 15th June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*SWAT team rotation: Ross -> Amanda on Aug. 9, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*Bug Triage meeting Thursday August 1st at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting August 6th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - Next event is August 6th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.8 M2 rc1 is in QA which is due to complete on Wednesday
*YP 5.0.18 has been released
*YP 2.6.3 will build to go into QA on Wednesday
*YP 6.0.1 is in QA.
*We have a new “newcomer” bug category which are bugs suited to someone new to the project. These can be seen here: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*YP 6.1 M1 is due to build this week
*The Yocto Project TSC has determined how it plans to operate and put the details into the appropriate wiki page: https://wiki.yoctoproject.org/wiki/TSC. It is intended as a decision making body of last resort, if there are issues people wish it to address, please raise them with one of its members.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*After discussion in various places its been agreed that the next project release will be “3.0”, to replace “2.8”. The 2.8 placeholder may continue to be used, particularly in the bugzilla. There are many good reasons to bump the version, the most recent being the runqueue changes allowing build optimizations based upon output equivalence (see below) but also including the new project governance, the autobuilder, improved test coverage any many other things.
*Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
*There are patches available which enable runqueue optimisations based on output comparisons of tasks. This removes the need to run later tasks if the output is unchanged and is based upon the previous hash equivalence server work. This feature should be a significant win for the users and is now working to a level where we’ll likely make this a key feature of the next release. These patches are being tested in master-next at present.
*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 also changes in -next which are being considered which change several bitbake APIs around runqueue. The feeling is now may be the best time to clean up several interfaces. If there are other API fixes people want to see, now is a good time to mention them.
*We have changed the xz and zstd decompression dependencies to make the build slightly more efficient and use the host tools for decompression
*The project is working on some mentor and mentee opportunities. Please see the separate email from Nicolas on the yocto list about this.
*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


'''Planned Releases for YP 2.8:'''<br/>
'''Ways to contribute:'''<br/>
*M2 is in QA
*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=---
*M2 Release 26th July
*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/
*M3 Cutoff (Feature Freeze) 25th Aug
*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.
*M3 Release 6th Sept
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*M4 Cutoff 30th Sept
*2.8 (M4) Final Release 25th Oct


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 2.7.2 (Warrior) is planned for after 2.8 M2  release.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and before 2.8 M3.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2483 (last week 2489) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2655 (last week 2630) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1499 (last week 1502)
**Total patches found: 1056 (last week 1087)
**Patches in the Pending State: 623 (42%) [last week 630 (42%)]
**Patches in the Pending State: 147 (14%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Key Status Links for YP:'''<br/>
'''Upcoming development releases:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status<br/>
*6.1 M1:
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule<br/>
**Build Date: w/c 2026-06-08
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features<br/>
**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:'''<br/>
*YP 6.0.1 is in QA.
*YP 6.0.2
**Build Date w/c 2026-06-23
**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/>
https://wiki.yoctoproject.org/wiki/TSC<br/>


== 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]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2019 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"