Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(115 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Oct. 22nd,  2024 ==
== Yocto Project Status 29 September 2026 ==
Current Dev Position: YP 5.2 M1<br/>
Current Dev Position: YP 6.1 M4 - Stabilization (Bug Fixing)<br/>
Next Deadline: YP 5.2 M1 Release date 2024-12-09<br/>
Next Deadline: YP 6.1 M4: w/c 2026-10-12<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Oct. 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 1st Oct. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Oct. 22nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 29th Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 1st Oct. 10am GMT and Monday 5th Oct. 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 5.1 was released - Thanks to everyone who helped contribute to 5.1!
*YP 6.1 M3 was released
*YP 4.0.22 is due to release
*YP 6.1 is due for build imminently
*We are continuing with the autobuilder migration and the typhoon cluster is being decommissioned. All builds are now happening on valkyrie (the new cluster).
*Blacksail and master are now on separate branches and have diverged.
*There are still a lot of failures occurring on the autobuilder. Of the remaining issues, we are making progress on many but work is still ongoing.
*We are not aware of anyone focusing on specific 6.1 stabilization work so we will likely build 6.1 very soon.
*In particular it was found the debian 11 5.10 kernel was problematic with qemu and the 6.1 kernel appears more stable for our workloads. We will switch the debian 11 workers to the 6.1 backport kernel.
*We’ve continued progress on the build architecture reproducibility issues, thanks all!
*We plan to disable the rust tests for mips and ppc, we cannot find any users of rust on these architectures.
*There are issues where we could accept help:
*For 5.2 it would be helpful to have rough development plans for areas of the project if anyone is able to help document a rough roadmap/plan for them. The following areas are known to be being or need working on:
**Matchbox-wm segfault/xserver restart
**Autobuilder
**aarch64/x86-64 build host contamination/reproducibility issue - thanks for the work and fixes so far on this.
**Binary Distro
**Remaining github.com references in bitbake-selftest
**Bitbake config fragments
*Bitbake’s network disabling has recently been enhanced to include landlock support. This means the network isolation for tasks can be more effective on certain kernel/distro combinations using newer technology.
**Bitbake setup process/tooling
*Next week is Open Source Summit EU and Yocto Project Developer Day in Prague! Contact Paul or Megan if you are attending and want to meet up with other Yocto Project folks, especially if you’re new t o our community.
**GUI screen shot QA test
**Regular meetings on Tuesday and Thursday next week will be canceled, including the Tech call (Tue 6th), Patch review call (Thu 8th) and Bug triage call (Thu 8th). The Monday patch review call will be going ahead.
**IDE Plugin development
**Layer Index
**Patchtest
**Security Tooling
**Swatbot
**Toaster
*If there are other areas we should have plans for, please let us know.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*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 is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
*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/
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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.
*There are bugs that are currently unassigned for YP 5.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_Unassigned_Enhancements/Bugs
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*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.
 
*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.
'''New to the project?'''<br/>
*Help us resolve CVE issues: CVE metrics
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2776 (last week 2774) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2640 (last week 2647) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1078 (last week 1075)
**Total patches found: 1055 (last week 1054)
**Patches in the Pending State: 175 (16%) [last week 175 (16%)]
**Patches in the Pending State: 137 (13%) [last week 135 (1%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/3


'''YP 5.1 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 5.1 is released.
*6.1 M3: was released
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02


'''YP 5.2 Milestone Dates:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.2 M1 Build Date 2024-12-09
*YP 6.0.4
*YP 5.2 M1 Release Date 2024-12-20
**Build Date w/c 2026-09-28
*YP 5.2 M2 Build Date 2025-01-20
**Release Date w/c 2026-10-12
*YP 5.2 M2 Release Date 2025-01-31
*YP 5.0.21
*YP 5.2 M3 Build Date 2025-03-03
**Build Date w/c 2026-10-05
*YP 5.2 M3 Release Date 2025-03-14
**Release Date w/c 2026-10-19
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25


'''Upcoming dot releases:'''<br/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 4.0.22 is in review.
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.23 Release Date 2024-11-29
*YP 5.1.1 Build Date 2024-12-02
*YP 5.1.1 Release Date 2024-12-13
*YP 5.0.6 Build Date 2024-12-16
*YP 5.0.6 Release Date 2024-12-27
*YP 4.0.24 Build Date 2025-01-06
*YP 4.0.24 Release Date 2025-01-17
*YP 5.1.2 Build Date 2025-01-13
*YP 5.1.2 Release Date 2025-01-24
*YP 5.0.7 Build Date 2025-01-27
*YP 5.0.7 Release Date 2025-02-07
*YP 4.0.25 Build Date 2025-02-17
*YP 4.0.25 Release Date 2025-02-28
*YP 5.1.3 Build Date 2025-02-24
*YP 5.1.3 Release Date 2025-03-07
*YP 5.0.8 Build Date 2025-03-10
*YP 5.0.8 Release Date 2025-03-21
*YP 5.1.4 Build Date 2025-03-24
*YP 5.1.4 Release Date 2025-04-04
*YP 4.0.26 Build Date 2025-04-07
*YP 4.0.26 Release Date 2025-04-18
*YP 5.0.9 Build Date 2025-04-21
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.0.10 Build Date 2025-06-02
*YP 5.0.10 Release Date 2025-06-13
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11


'''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 98: Line 60:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]

Latest revision as of 14:59, 29 September 2026

Yocto Project Status 29 September 2026

Current Dev Position: YP 6.1 M4 - Stabilization (Bug Fixing)
Next Deadline: YP 6.1 M4: w/c 2026-10-12

Next Team Meetings:

Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

  • YP 6.1 M3 was released
  • YP 6.1 is due for build imminently
  • Blacksail and master are now on separate branches and have diverged.
  • We are not aware of anyone focusing on specific 6.1 stabilization work so we will likely build 6.1 very soon.
  • We’ve continued progress on the build architecture reproducibility issues, thanks all!
  • There are issues where we could accept help:
    • Matchbox-wm segfault/xserver restart
    • aarch64/x86-64 build host contamination/reproducibility issue - thanks for the work and fixes so far on this.
    • Remaining github.com references in bitbake-selftest
  • Bitbake’s network disabling has recently been enhanced to include landlock support. This means the network isolation for tasks can be more effective on certain kernel/distro combinations using newer technology.
  • Next week is Open Source Summit EU and Yocto Project Developer Day in Prague! Contact Paul or Megan if you are attending and want to meet up with other Yocto Project folks, especially if you’re new t o our community.
    • Regular meetings on Tuesday and Thursday next week will be canceled, including the Tech call (Tue 6th), Patch review call (Thu 8th) and Bug triage call (Thu 8th). The Monday patch review call will be going ahead.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M3: was released
  • 6.1.0:
    • Build Date (M4): w/c 2026-10-12
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 6.0.4
    • Build Date w/c 2026-09-28
    • Release Date w/c 2026-10-12
  • YP 5.0.21
    • Build Date w/c 2026-10-05
    • Release Date w/c 2026-10-19

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