Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(104 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 23rd, 2024 ==
== Yocto Project Weekly Status Dec. 16th, 2025 ==
Current Dev Position: YP 5.0 in QA <br/>
Current Dev Position: YP 6.0 M1<br/>
Next Deadline: YP 5.0 Release by 30 April 2024<br/>
Next Deadline: YP 6.0 M1 Build Date 2026-01-05<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday April 25th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Dec. 18th at 7:30 am PST, then Thursday 8th Jan 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday April 23rd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday Dec. 18th 8 am PDT, then Tuesday 6th Jan 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday Dec. 18th 10am GMT and Monday  Dec. 22th 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.0 rc4 is in QA.
*YP 5.3 was released, thanks to everyone who helped make it happen!
*YP 3.1.33, The final dunfell build will follow 5.0 into QA.
*YP 4.0.32 is in QA
*YP 4.0.18 is behind 3.1.33 for QA.
*The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
*YP 5.0 rc2 was abandoned after issues with git in buildtools were found caused by a curl regression. 5.0 rc3 had further buildtools issues from configuration problems. 5.0 rc4 was built cleanly and went into QA to replace rc2.
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*The master branch has diverged from scarthgap and we’re trying to keep up to date with incoming patches there.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*There are also patches under review for the patch/cve metrics page to improve the usability as well as build performance graphing improvements.
*Further bitbake-setup changes under discussion for the new development cycle:
*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
**defaulting to a common sstate directory and hashequiv server
Please consider signing this to show support for those changes, which would improve our ability to analyze CVEs, and that of many other projects (including other distros) to do so too.
**Allowing symlinking of local existing repos into the build instead of fetching
*We continue to watch the NIST NVD (CVE database) situation, the lack of CPE information is problematic for us and we are considering what alternatives we have.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*Some CVE information is being provided for issues in meta-openembedded, this has been provided with help from the Sovereign Tech Fund.
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.
*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.  


'''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!
*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!
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 bugs that are currently unassigned for YP 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_Unassigned_Enhancements/Bugs
*There are bugs identified as possible for newcomers to the project: https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_Unassigned_Enhancements/Bugs
*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.
*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.
*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  
*Help us resolve CVE issues: CVE metrics  
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*Ongoing project development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing We need to continue to develop this as it will allow us to potentially find ways to fund specific work items.
'''Tracking Metrics:'''<br/>
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
'''YP 5.3 Milestone Dates:'''<br/>
*YP 5.3 M4 is released.


'''YP 5.0 Milestone Dates:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 5.0 is in QA
*YP 6.0 M1 Build Date 2026-01-05
*YP 5.0 M4 Release date 2024/04/30
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26


'''YP 5.1 Milestone Dates:'''<br/>
*YP 5.1 M1 Build date 2024-05-20
*YP 5.1 M1 Release date 2024-05-31
*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 3.1.33 is in QA
*YP 4.0.32 is in QA.
*YP 4.0.18 is in QA
*YP 5.0.15 Build Date 2026-01-05
*YP 4.0.18 Release date 2024-05-03
*YP 5.0.15 Release Date 2026-01-16
*YP 5.0.1 Build Date 2024-05-13
*YP 5.3.1 Build Date 2026-01-12
*YP 5.0.1 Release Date 2024-05-24
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.19 build date 2024-06-03
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.19 Release date 2024-06-14
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.2 Build Date 2024-06-24
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.2 Release Date 2024-07-05
*YP 5.0.16 Release Date 2026-02-20
*YP 4.0.20 Build Date 2024-07-15
*YP 5.3.2 Build Date 2026-02-16
*YP 4.0.20 Release Date 2024-07-26
*YP 5.3.2 Release Date 2026-02-27
*YP 5.0.3 Build Date 2024-08-12
*YP 4.0.34 Build Date 2026-02-23
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.34 Release Date 2026-03-06
*YP 4.0.21 Build Date 2024-09-09
*YP 5.3.3 Build Date 2026-03-09
*YP 4.0.21 Release Date 2024-09-20
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.4 Release Date 2024-10-04
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.22 Release Date 2024-10-25
*YP 4.0.35 Release Date 2026-04-17
*YP 5.0.5 Build Date 2024-11-11
*YP 5.3.4 Build Date 2026-04-13
*YP 5.0.5 Release Date 2024-11-22
*YP 5.3.4 Release Date 2026-04-24
*YP 4.0.23 Build Date 2024-11-18
*YP 5.0.18 Build Date 2026-04-20
*YP 4.0.23 Release Date 2024-11-29
*YP 5.0.18 Release Date 2026-05-01
 
*YP 5.0.19 Build Date 2026-05-26
'''Tracking Metrics:'''<br/>
*YP 5.0.19 Release Date 2026-06-05
*WDD 2714 (last week 2719) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1140 (last week 1173)
**Patches in the Pending State: 249 (21%) [last week 249 (21%)]
*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 80: Line 85:


== Archives ==
== Archives ==
*[[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 15:51, 16 December 2025

Yocto Project Weekly Status Dec. 16th, 2025

Current Dev Position: YP 6.0 M1
Next Deadline: YP 6.0 M1 Build Date 2026-01-05

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.3 was released, thanks to everyone who helped make it happen!
  • YP 4.0.32 is in QA
  • The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
  • Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
  • We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
  • Further bitbake-setup changes under discussion for the new development cycle:
    • defaulting to a common sstate directory and hashequiv server
    • Allowing symlinking of local existing repos into the build instead of fetching
  • The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
  • We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

Ways to contribute:

Tracking Metrics:

YP 5.3 Milestone Dates:

  • YP 5.3 M4 is released.

YP 6.0 Milestone Dates:

  • YP 6.0 M1 Build Date 2026-01-05
  • YP 6.0 M1 Release Date 2026-01-16
  • YP 6.0 M2 Build Date 2026-02-02
  • YP 6.0 M2 Release Date 2026-02-13
  • YP 6.0 M3 Build Date 2026-03-02
  • YP 6.0 M3 Release Date 2026-03-13
  • YP 6.0 M4 Build Date 2026-03-30
  • YP 6.0 M4 Release Date 2026-04-26


Upcoming dot releases:

  • YP 4.0.32 is in QA.
  • YP 5.0.15 Build Date 2026-01-05
  • YP 5.0.15 Release Date 2026-01-16
  • YP 5.3.1 Build Date 2026-01-12
  • YP 5.3.1 Release Date 2026-01-23
  • YP 4.0.33 Build Date 2026-01-26
  • YP 4.0.33 Release Date 2026-01-30
  • YP 5.0.16 Build Date 2026-02-09
  • YP 5.0.16 Release Date 2026-02-20
  • YP 5.3.2 Build Date 2026-02-16
  • YP 5.3.2 Release Date 2026-02-27
  • YP 4.0.34 Build Date 2026-02-23
  • YP 4.0.34 Release Date 2026-03-06
  • YP 5.3.3 Build Date 2026-03-09
  • YP 5.3.3 Release Date 2026-03-20
  • YP 5.0.17 Build Date 2026-03-16
  • YP 5.0.17 Release Date 2026-03-23
  • YP 4.0.35 Build Date 2026-04-06
  • YP 4.0.35 Release Date 2026-04-17
  • YP 5.3.4 Build Date 2026-04-13
  • YP 5.3.4 Release Date 2026-04-24
  • YP 5.0.18 Build Date 2026-04-20
  • YP 5.0.18 Release Date 2026-05-01
  • YP 5.0.19 Build Date 2026-05-26
  • YP 5.0.19 Release Date 2026-06-05

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