Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(321 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 5th, 2022 ==
== Yocto Project Status 25 August 2026 ==
Current Dev Position: YP 4.1 M2<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: 11th July 2022 YP 4.1 M2 Build<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday July 7th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 27th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday July 5th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 25th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 27th Aug. 10am GMT and Monday 31st Aug. 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 6.0.3 is in QA.
*YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
*For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
*AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*Remaining intermittent build failures of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**intermittent ptest failures in many recipes
'''Ways to contribute:'''<br/>
*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 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/
*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


*Next week M2 is due to build so if anyone has changes for that milestone, please send ASAP.
'''New to the project?'''<br/>
*YP 4.0.2 has been through QA and is likely to be released in the next few days.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*A reproducibility issue was identified and raised a question on whether we could enable              an old QA check for these kinds of issues (‘buildpaths’ in insane.bbclass). Some bugs were fixed in the test but is has highlighted several reproducibility issues. Some have been fixed but others remain:
**docs issues in lib32-vala, rpm, lib32-gtk-doc, vala, gtk-doc
**musl issue in ltp
**multilib issues in lib32-vala, vala, rpm (may overlap docs)
**qemuarm64 kernel-devsrc issue (Bruce looking into)
**meta-virt issues in xen-tools (Christopher looking into)
**meta-gplv2 issues in mc, tar
**lttng-modules .debug issue on beaglebone, edgerouter, and qemumips
*Fixing these will allow us to enable buildpaths by default which should allow more people to spot reproducibility issues.
*There is a discussion about layer setup tooling in the bitbake-layers discussion on the OE-Core list, input is welcome from those with an interest in this.
*There is also a RFC series about improving the eSDK tooling workflows from Alex Kanavin which may be of interest.
*Code to monitor the /proc/pressure interface has been added and there is a patch to optionally allow bitbake to reduce the number of processes running depending on system load, which it is hoped may help some of our autobuilder intermittent issues (thanks Aryaman and Randy).
*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/>
'''Tracking Metrics:'''<br/>
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*WDD 2659 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*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
*OE-Core/Poky Patch Metrics
*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.
**Total patches found: 1028 (last week 1030)
*Help us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 4.1 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 4.1 M2 build date 2022/07/11
*6.1 M3:
*YP 4.1 M2 Release date 2022/07/22
**Build Date: w/c 2026-08-31
*YP 4.1 M3 build date 2022/08/22
**Release Date: w/c 2026-09-14
*YP 4.1 M3 Release date 2022/09/02
*6.1.0:
*YP 4.1 M4 build date 2022/10/03
**Build Date (M4): w/c 2026-10-12
*YP 4.1 M4 Release date 2022/10/28
**Release Date: w/c 2026-11-02


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.2 build date 2022/06/27 - pending TSC approval
*YP 6.0.3 is in QA.
*YP 4.0.2 Release date 2022/07/08
**Release Date w/c 2026-08-24
*YP 3.1.18 build date 2022/07/18
*YP 5.0.20
*YP 3.1.18 Release date 2022/07/29
**Build Date w/c 2026-08-17
*YP 4.0.3 build date 2022/08/08
**Release Date w/c 2026-08-31
*YP 4.0.3 Release date 2022/08/19
*YP 6.0.4
*YP 3.1.19 build date 2022/08/29
**Build Date w/c 2026-09-28
*YP 3.1.19 Release date 2022/09/09
**Release Date w/c 2026-10-12
*YP 4.0.4 build date 2022/09/19
*YP 5.0.21
*YP 4.0.4 Release date 2022/09/30
**Build Date w/c 2026-10-05
*YP 3.1.20 build date 2022/10/10
**Release Date w/c 2026-10-19
*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/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*WDD 2387 (last week 2400) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1158 (last week 1151)
**Patches in the Pending State: 328 (28%) [last week 326 (28%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''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 67: Line 68:


== 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:45, 25 August 2026

Yocto Project Status 25 August 2026

Current Dev Position: YP 6.1 M3
Next Deadline: YP 6.1 M3: w/c 2026-08-31

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.0.3 is in QA.
  • YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
  • For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
  • AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
  • We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
  • There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
    • Matchbox-wm segfault/xserver restart
    • aarch64/x86-64 build host contamination/reproducibility issue

We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.

  • Remaining intermittent build failures of concern:
    • other qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • intermittent ptest failures in many recipes

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 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:

  • YP 6.0.3 is in QA.
    • Release Date w/c 2026-08-24
  • YP 5.0.20
    • Build Date w/c 2026-08-17
    • Release Date w/c 2026-08-31
  • 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=86868"