Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(49 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 18th, 2024 ==
== Yocto Project Weekly Status Apr. 1st, 2025 ==
Current Dev Position: YP 5.1 M2 <br/>
Current Dev Position: YP 5.2 M4 - Feature Freeze<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<br/>
Next Deadline: YP 5.2 M4 Build Date 2025-03-31 - Feature Freeze<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday June 13th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Apr. 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday June 11th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday Apr. 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday Apr. 3rd 10am GMT and Monday Apr. 7th 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 4.0.19 is ready for release.
*YP 5.2 M3 and YP 5.0.8 were released
*YP 5.1 M1 is ready for release.
*YP 5.1.4 is due for release
*Patch status tags are now checked for by default. Layers which don't wish this can disable the error by removing patch-status from ERROR_QA.
*Our first release candidate for YP 5.2 is ready for QA
*Fedora 40 support should be almost complete. GCC 14 is the gift that keeps on giving, the last issue I'm aware of is in 'expect' and there are now two competing patches for that.
*The walnascar branches have diverged from master
*Some larger patches are on the list and help reviewing these would be appreciated:
*qemumips, qemumips64 and qemuppc have been dropped from automated testing for walnascar and master onwards. Older releases will continue to have the testing they were released with.
**Adding SPDX 3.0 from Joshua
*Some other autobuilder test targets were also tweaked to match current needs (e.g. fewer oe-selftest runs).
**Improved CVE tooling from Marta
*Some disk usage improvements for rust were merged or queued for merge to help with overall build performance.
**bitbake-setup and configuration fragments from Alexander
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it.
*We had some fixes for the install-buildtools script which showed a lack of automated testing for it. Adding some would be an interesting first contribution if anyone is interested.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been temporarily disabled at times of high load to help ensure clones work.
*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
**Please consider signing this to show support for those changes.
**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.
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
*Through post release upgrading our patch count reduced again and is now the lowest level since July 2008!


'''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 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 identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 that are currently unassigned for YP 5.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_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/>
'''Tracking Metrics:'''<br/>
*WDD 2779 (last week 2774) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2781 (last week 2801) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1072 (last week 1072)
**Total patches found: 1080 (last week 1060)
**Patches in the Pending State: 205 (19%) [last week 205 (19%)]
**Patches in the Pending State: 167 (15%) [last week 168 (16%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 5.1 Milestone Dates:'''<br/>
'''YP 5.2 Milestone Dates:'''<br/>
*YP 5.1 M1 is ready for release.
*YP 5.2 M3 was released.
*YP 5.1 M2 Build date 2024-07-08
*YP 5.2 M4 is in QA.
*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 4.0.19 is ready for release.
*YP 5.0.8 was released.
*YP 5.0.2 Build Date 2024-06-24
*YP 5.1.4 is ready for release.
*YP 5.0.2 Release Date 2024-07-05
*YP 4.0.26 Build Date 2025-04-07
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.26 Release Date 2025-04-18
*YP 4.0.20 Release Date 2024-07-26
*YP 5.0.9 Build Date 2025-04-21
*YP 5.0.3 Build Date 2024-08-12
*YP 5.0.9 Release Date 2025-05-02
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.21 Build Date 2024-09-09
*YP 4.0.27 Release Date 2025-05-30
*YP 4.0.21 Release Date 2024-09-20
*YP 5.0.10 Build Date 2025-06-02
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.10 Release Date 2025-06-13
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.28 Release Date 2025-07-11
*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 72: Line 61:


== 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:00, 1 April 2025

Yocto Project Weekly Status Apr. 1st, 2025

Current Dev Position: YP 5.2 M4 - Feature Freeze
Next Deadline: YP 5.2 M4 Build Date 2025-03-31 - Feature Freeze

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.2 M3 and YP 5.0.8 were released
  • YP 5.1.4 is due for release
  • Our first release candidate for YP 5.2 is ready for QA
  • The walnascar branches have diverged from master
  • qemumips, qemumips64 and qemuppc have been dropped from automated testing for walnascar and master onwards. Older releases will continue to have the testing they were released with.
  • Some other autobuilder test targets were also tweaked to match current needs (e.g. fewer oe-selftest runs).
  • Some disk usage improvements for rust were merged or queued for merge to help with overall build performance.
  • A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it.
  • We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been temporarily disabled at times of high load to help ensure clones work.

Ways to contribute:

Tracking Metrics:

YP 5.2 Milestone Dates:

  • YP 5.2 M3 was released.
  • YP 5.2 M4 is in QA.

Upcoming dot releases:

  • YP 5.0.8 was released.
  • YP 5.1.4 is ready for release.
  • YP 4.0.26 Build Date 2025-04-07
  • YP 4.0.26 Release Date 2025-04-18
  • YP 5.0.9 Build Date 2025-04-21
  • YP 5.0.9 Release Date 2025-05-02
  • YP 4.0.27 Build Date 2025-05-19
  • YP 4.0.27 Release Date 2025-05-30
  • YP 5.0.10 Build Date 2025-06-02
  • YP 5.0.10 Release Date 2025-06-13
  • YP 4.0.28 Build Date 2025-06-30
  • YP 4.0.28 Release Date 2025-07-11

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