Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(200 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status October 3rd, 2023 ==
== Yocto Project Status 29 September 2026 ==
Current Dev Position: YP 4.3 M4 (Feature Freeze)<br/>
Current Dev Position: YP 6.1 M4 - Stabilization (Bug Fixing)<br/>
Next Deadline: 2nd October 2023 YP 4.3 M4 build date<br/>
Next Deadline: YP 6.1 M4: w/c 2026-10-12<br/>


'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 1st Oct. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync  - Tuesday 29th Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 1st Oct. 10am GMT and Monday 5th Oct. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


'''Next Team Meetings:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*Bug Triage meeting Thursday October 5th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday October 3rd 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.3 M4 is due to build this week. We have challenges due to the kernel version.
*YP 6.1 M3 was released
*YP 3.1.28 was released.
*YP 6.1 is due for build imminently
*YP 4.0.13 is due to be released
*Blacksail and master are now on separate branches and have diverged.
*The biggest challenge for the M4 build is that the 6.4 kernel was made EOL. Thanks to hard work from Bruce we have 6.5 recipes but this kernel version is throwing multiple errors in testing:
*We are not aware of anyone focusing on specific 6.1 stabilization work so we will likely build 6.1 very soon.
**cryptodev breaks (patch in master-next)
*We’ve continued progress on the build architecture reproducibility issues, thanks all!
**x86 image testing randomly fails with login issues (both selftest and testimage)
*There are issues where we could accept help:
**arm kvm ptest images randomly throw jitterentropy errors and fail
**Matchbox-wm segfault/xserver restart
**strace ptest failures (x86 and arm)
**aarch64/x86-64 build host contamination/reproducibility issue - thanks for the work and fixes so far on this.
**arm LTP testing fails with OOM crashes
**Remaining github.com references in bitbake-selftest
We don’t have fixes for the OOM issue or strace at this point, potential ideas for other issues are undergoing testing.
*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.
*The numpy reproducibility issue was finally root caused and resolved.
*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.
*Issues with mesa-native and contamination with llvm from the host have been resolved
**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.
*Improvements to bitbake-getvar output and handling of undefined values were merged
*The openssh ptest intermittent failure does have better logs available but we’ve yet to decode what it means:
http://autobuilder.yocto.io/pub/non-release/20230917-2/testresults/qemuarm64-ptest/openssh.log
*The project is working on improving its security processes and policies, there are emails on the mailing list discussing this. Please highlight these to any parties who may be interested or have useful feedback.
 


'''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: patchtest, layerindex, 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 are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 that are currently unassigned for YP 4.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_Unassigned_Enhancements.2FBugs
*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.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*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.
*Help us resolve CVE issues: CVE metrics
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''YP 4.3 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 4.3 M3 was released.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 4.3 M4 build date  2023/10/02
*YP 4.3 M4 Release date 2023/10/27


'''YP 5.0 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 5.0 M1 build date 2023/12/04
*WDD 2640 (last week 2647) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0 M1 Release date 2023/12/15
*OE-Core/Poky Patch Metrics
*YP 5.0 M2 build date  2024/01/15
**Total patches found: 1055 (last week 1054)
*YP 5.0 M2 Release date 2024/01/24
**Patches in the Pending State: 137 (13%) [last week 135 (1%)]
*YP 5.0 M3 build date  2024/02/19
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/3
*YP 5.0 M3 Release date 2024/03/01
 
*YP 5.0 M4 build date  2024/04/01
'''Upcoming development releases:'''<br/>
*YP 5.0 M4 Release date 2024/04/30
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.28 is ready for release.
*YP 6.0.4
*YP 4.0.13 is in QA.
**Build Date w/c 2026-09-28
*YP 3.1.29 build date 2023/10/30
**Release Date w/c 2026-10-12
*YP 3.1.29 Release date 2023/11/10
*YP 5.0.21
*YP 4.0.14 build date 2023/11/06
**Build Date w/c 2026-10-05
*YP 4.0.14 Release date 2023/11/17
**Release Date w/c 2026-10-19
*YP 4.2.4 build date 2023/11/13
*YP 4.2.4 Release date 2023/11/24
*YP 4.3.1 build date 2023/11/27
*YP 4.3.1 Release date 2023/12/08
*YP 3.1.30 build date 2023/12/11
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29
*YP 4.3.2 build date 2024/01/08
*YP 4.3.2 Release date 2024/01/19
*YP 3.1.31 build date 2024/01/22
*YP 3.1.31 Release date 2024/02/02
*YP 4.0.16 build date 2024/01/29
*YP 4.0.16 Release date 2024/02/09
*YP 4.3.3 build date 2024/02/12
*YP 4.3.3 Release date 2024/02/23
*YP 3.1.32 build date 2024/03/04
*YP 3.1.32 Release date 2024/03/15
*YP 4.0.17 build date 2024/03/11
*YP 4.0.17 Release date 2024/03/22
*YP 4.3.4 build date 2024/03/25
*YP 4.3.4 Release date 2024/04/05
*YP 3.1.33 build date 2024/04/15
*YP 3.1.33 Release date 2024/04/26
*YP 4.0.18 build date 2024/04/22
*YP 4.0.18 Release date 2024/05/03
*YP 4.0.19 build date 2024/06/03
*YP 4.0.19 Release date 2024/06/14
 
'''Tracking Metrics:'''<br/>
*WDD 2455 (last week 2475) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*Total patches found: 1176 (last week 1183)
*Patches in the Pending State: 254 (21%) [last week 254 (21%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


*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 100: Line 60:


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