Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(322 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 28th, 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 June 30th 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)
*Monthly Project Meeting 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)
*Weekly Engineering Sync Tuesday June 28th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 27th Aug. 10am GMT and Monday 31st Aug. 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 4.0.2 is due to build this week however we want to fix one bitbake logging regression first.
*YP 6.0.3 is in QA.
*A fix has been merged for a logging regression found in bitbake where the first message to the console during parsing would be shown but subsequent ones would not.  
*YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
*Fedora 36 is causing problems on the autobuilder since it drops support for the scp protocol requiring sftp on target instead to exchange files. Dropbear does not have sftp support. We need scp to perform several of our image tests.  We can add sftp to both dropbear and openssh images however that then causes dev-pkg conflicts since openssh and dropbear cannot be installed at the same time but are pulled in by openssh-dev and dropbear-dev.
*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!
*As such we’re proposing to change -dev package dependencies to become rrecommends instead of rdepends. This does radically change the contents of some images but in a way which is much more correct.
*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.
*There is a potential follow up change to change injected symlink dependencies from rdepends to rrecommends as well, which reduces the delta  of “dev-pkg” featured images even more.
*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 also problems in the cve-check selftests causing other build failures.
*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:
*Various npm fixes were merged, thanks Enrico.
**Matchbox-wm segfault/xserver restart
*There are problems with rust-cross-canadian, it has never worked correctly for the full set of different targets cross-canadian might be set to. Help to fix that would be much appreciated.
**aarch64/x86-64 build host contamination/reproducibility issue
*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
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/>
'''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 4.1 See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_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.
*Help us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
 
'''New to the project?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''YP 4.1 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 4.1 M2 build date 2022/07/11
*WDD 2659 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.1 M2 Release date 2022/07/22
*OE-Core/Poky Patch Metrics
*YP 4.1 M3 build date 2022/08/22
**Total patches found: 1028 (last week 1030)
*YP 4.1 M3 Release date 2022/09/02
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
*YP 4.1 M4 build date 2022/10/03
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
*YP 4.1 M4 Release date 2022/10/28
 
'''Upcoming development releases:'''<br/>
*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/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.2 build date 2022/06/27
*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 2400 (last week 2430) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1151 (last week 1160)
**Patches in the Pending State: 326 (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 61: 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"