Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(15 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Apr. 1st, 2025 ==
== Yocto Project Weekly Status July 1st, 2025 ==
Current Dev Position: YP 5.2 M4 - Feature Freeze<br/>
Current Dev Position: YP 5.3 M2<br/>
Next Deadline: YP 5.2 M4 Build Date 2025-03-31 - Feature Freeze<br/>
Next Deadline: YP 5.3 M2 Build date 2025-07-21<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday Apr. 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday July 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday July 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 3rd 10am GMT and Monday Apr. 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)  
*Yocto Project Patch Review - Thursday July 3rd 10am GMT and Monday July 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)  


'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.2 M3 and YP 5.0.8 were released
*YP 5.3 M1 is due to be released. One issue was found which needs to be fixed during M2: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
*YP 5.1.4 is due for release
**Help in debugging and fixing this would be very welcome.
*Our first release candidate for YP 5.2 is ready for QA
*YP 4.0.28 is in QA.
*The walnascar branches have diverged from master
*Patches continue to merge into master for upgrades and fixes.
*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.
*There were git tag improvements meaning we can now start adding these to SRC_URIs in all cases as shallow clone tarballs now account for them.
*Some other autobuilder test targets were also tweaked to match current needs (e.g. fewer oe-selftest runs).
*The clang build time and size increases continue to cause significant concern.
*Some disk usage improvements for rust were merged or queued for merge to help with overall build performance.
*Patches to improve gomod support in devtool merged.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*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.
*OE_SHARED_UMASK was added to control the umask used for files created in the shared DL_DIR and SSTATE_DIR directories.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 2)
**switch classextend to use [filter] support from bitbake


'''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 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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*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
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
Line 33: Line 38:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2781 (last week 2801) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2770 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1060)
**Total patches found: 1091 (last week 1093)
**Patches in the Pending State: 167 (15%) [last week 168 (16%)]
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 5.2 Milestone Dates:'''<br/>
'''YP 5.3 Milestone Dates:'''<br/>
*YP 5.2 M3 was released.
*YP 5.3 M1 is ready for release.
*YP 5.2 M4 is in QA.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.8 was released.
*YP 4.0.28 is in QA.
*YP 5.1.4 is ready for release.
*YP 5.2.2 Build Date 2025-07-07
*YP 4.0.26 Build Date 2025-04-07
*YP 5.2.2 Release Date 2025-07-18
*YP 4.0.26 Release Date 2025-04-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.9 Build Date 2025-04-21
*YP 5.0.11 Release Date 2025-07-25
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.29 Release Date 2025-08-25
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.3 Build Date 2025-08-18
*YP 5.0.10 Build Date 2025-06-02
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.10 Release Date 2025-06-13
*YP 5.0.12 Build Date 2025-08-25
*YP 4.0.28 Build Date 2025-06-30
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.28 Release Date 2025-07-11
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16


'''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/>

Revision as of 14:41, 1 July 2025

Yocto Project Weekly Status July 1st, 2025

Current Dev Position: YP 5.3 M2
Next Deadline: YP 5.3 M2 Build date 2025-07-21

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.3 M1 is due to be released. One issue was found which needs to be fixed during M2: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
    • Help in debugging and fixing this would be very welcome.
  • YP 4.0.28 is in QA.
  • Patches continue to merge into master for upgrades and fixes.
  • There were git tag improvements meaning we can now start adding these to SRC_URIs in all cases as shallow clone tarballs now account for them.
  • The clang build time and size increases continue to cause significant concern.
  • Patches to improve gomod support in devtool merged.
  • The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
  • OE_SHARED_UMASK was added to control the umask used for files created in the shared DL_DIR and SSTATE_DIR directories.
  • For M2, the following changes have been mentioned as possibilities:
    • bitbake-setup
    • wic split from OE-Core
    • RISC-V tune changes (part 2)
    • switch classextend to use [filter] support from bitbake

Ways to contribute:

Tracking Metrics:

YP 5.3 Milestone Dates:

  • YP 5.3 M1 is ready for release.
  • YP 5.3 M2 Build Date 2025-07-21
  • YP 5.3 M2 Release Date 2025-08-01
  • YP 5.3 M3 Build Date 2025-09-01
  • YP 5.3 M3 Release Date 2025-09-12
  • YP 5.3 M4 Build Date 2025-10-06
  • YP 5.3 M4 Release Date 2025-10-31

Upcoming dot releases:

  • YP 4.0.28 is in QA.
  • YP 5.2.2 Build Date 2025-07-07
  • YP 5.2.2 Release Date 2025-07-18
  • YP 5.0.11 Build Date 2025-07-14
  • YP 5.0.11 Release Date 2025-07-25
  • YP 4.0.29 Build Date 2025-08-11
  • YP 4.0.29 Release Date 2025-08-25
  • YP 5.2.3 Build Date 2025-08-18
  • YP 5.2.3 Release Date 2025-08-29
  • YP 5.0.12 Build Date 2025-08-25
  • YP 5.0.12 Release Date 2025-09-05
  • YP 4.0.30 Build Date 2025-09-22
  • YP 4.0.30 Release Date 2025-10-03
  • YP 5.2.4 Build Date 2025-09-29
  • YP 5.2.4 Release Date 2025-10-10
  • YP 5.0.13 Build Date 2025-10-13
  • YP 5.0.13 Release Date 2025-10-24
  • YP 4.0.31 Build Date 2025-11-03
  • YP 4.031 Release Date 2025-11-14
  • YP 5.0.14 Build Date 2025-11-17
  • YP 5.0.14 Release Date 2025-11-28
  • YP 4.0.32 Build Date 2025-12-15
  • YP 4.0.32 Release Date 2025-12-24
  • YP 5.0.15 Build Date 2026-01-05
  • YP 5.0.15 Release Date 2026-01-16

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