Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(149 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status May 28th, 2024 ==
== Yocto Project Status 6 October 2026 ==
Current Dev Position: YP 5.1 M1 <br/>
Current Dev Position: YP 6.2 M1 - Development<br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<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 May 30th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 15th Oct. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday May 28th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 13rd Oct. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 15th Oct. 10am GMT and Monday 12th 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.0.1 has been released.
*YP 6.1 is in QA
*We have suspected a performance problem for a while, this has now been identified/confirmed as an issue with hash equivalence. The public server using websockets/SSL has significantly slowed down things, to the point a 2 hour world build is taking 18+ hours. In trying to improve this, we ended up destablising the autobuilders entirely, breaking many builds and halting the patch merging.
*YP 6.0.4 is pending with QA.
The problem is visible both at build initialization time and also at any point it rehashes due to new hash information from the server. We are still trying to work out ways to improve things but there appears to be multiple levels of different problems, including the hashserve client parallelism seeming to have bugs. The issue affects scarthgap as well as master.
*Blacksail and master are now on separate branches and have diverged.
*A new gcc 14 compatible version of uninative was released allowing fedora 40 testing. Unfortunately there are issues with build failures on that host that are as yet uninvestigated.
*Patches for 6.2 have started merging into master
*The WORKDIR to UNPACKDIR transition has merged and other layers are now working on the updates needed. There appear to be some challenges around go modules in particular which are needing more investigation and development time.
*There are changes to the pypi class so that PYPI_PACKAGE is the normalised name
*We aim to build YP 5.1 M1 after the performance issue is addressed and we have stable builds.
*python3-pytz moved from core to meta-oe, if you notice anything using it, it is a sign the dependencies may be obsolete
*We were able to merge a chunk of pending patches but things are still processing slowly unfortunately.
*There are issues where we could accept help:
*There are some CVE related announcements which are helpful to us:
**Matchbox-wm segfault/xserver restart
**There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
**aarch64/x86-64 build host contamination/reproducibility issue - thanks for the work and fixes so far on this.
**CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
**Remaining github.com references in bitbake-selftest
**Unfortunately there are reports that the backlog of CVEs without version constraints is growing rapidly
*Bitbake’s network disabling has recently been enhanced to include landlock support.
*There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
*This 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 to our community.
**Please consider signing this to show support for those changes.
**Regular meetings on Tuesday and Thursday will be canceled, including the Tech call (Tue 6th), Patch review call (Thu 8th) and Bug triage call (Thu 8th).
**Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
*The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date.
T*he project is in the process of testing a new way of hosting our autobuilder with plans to switch soon if successful. Our existing hardware is past end of life and showing increased hardware failures so is currently down on capacity meaning builds are taking longer than normal, also not helped with the performance issue identfiied above.
*Further performance graph improvements have merged and the graphs now have links to specific revisions allowing regressions to be much more easily tracked down.


'''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 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 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_Unassigned_Enhancements/Bugs
*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
'''New to the project?'''<br/>
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2772 (last week 2752) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2644 (last week 2643) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1121 (last week 1127)
**Total patches found: 1057 (last week 1053)
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
**Patches in the Pending State: 135 (13%) [last week 135 (13%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/3


'''YP 5.1 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 5.1 M1 Build date 2024-05-20
*6.1.0: in QA
*YP 5.1 M1 Release date 2024-05-31
**Release Date: w/c 2026-11-02
*YP 5.1 M2 Build date 2024-07-08
*YP 5.1 M2 Release date 2024-07-19
*YP 5.1 M3 Build date 2024-08-26
*YP 5.1 M3 Release date 2024-09-06
*YP 5.1 M4 Build date 2024-09-30
*YP 5.1 M4 Release date 2024-10-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.1 is released.
*YP 6.0.4 in QA
*YP 4.0.19 build date 2024-06-03
**Release Date w/c 2026-10-12
*YP 4.0.19 Release date 2024-06-14
*YP 5.0.21
*YP 5.0.2 Build Date 2024-06-24
**Build Date w/c 2026-10-05
*YP 5.0.2 Release Date 2024-07-05
**Release Date w/c 2026-10-19
*YP 4.0.20 Build Date 2024-07-15
 
*YP 4.0.20 Release Date 2024-07-26
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 5.0.3 Build Date 2024-08-12
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.21 Build Date 2024-09-09
*YP 4.0.21 Release Date 2024-09-20
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.22 Release Date 2024-10-25
*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


'''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 78: Line 58:


== 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:13, 6 October 2026

Yocto Project Status 6 October 2026

Current Dev Position: YP 6.2 M1 - Development
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 is in QA
  • YP 6.0.4 is pending with QA.
  • Blacksail and master are now on separate branches and have diverged.
  • Patches for 6.2 have started merging into master
  • There are changes to the pypi class so that PYPI_PACKAGE is the normalised name
  • python3-pytz moved from core to meta-oe, if you notice anything using it, it is a sign the dependencies may be obsolete
  • 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 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 to our community.
    • Regular meetings on Tuesday and Thursday will be canceled, including the Tech call (Tue 6th), Patch review call (Thu 8th) and Bug triage call (Thu 8th).

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1.0: in QA
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 6.0.4 in QA
    • 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=86891"