Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status February 27th, 2024 ==
== Yocto Project Weekly Status March 5th, 2024 ==
Current Dev Position: YP 5.0 M3 - Feature Freeze <br/>
Current Dev Position: YP 5.0 M3 - Feature Freeze <br/>
Next Deadline: 19th February 2024 YP 5.0 M3 build<br/>
Next Deadline: 19th February 2024 YP 5.0 M3 build<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday February 29th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday March 7th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday February 27th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday March 5th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester
*Twitch -  See https://www.twitch.tv/theyoctojester


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We are now at feature freeze for 5.0, preparing to build M3
*We are now at feature freeze for 5.0, preparing to build M3
*YP 4.3.3 passed QA and is in review pending release
*YP 4.3.3 was released
*The changes which we’d still like to see in 5.0 that have not merged yet are:
*YP 3.1.32 is in QA
**genericarm64 machine (there is a draft and it is close)
*Several changes have merged for M3:
**genericarm64 machine (also added to autobuilder)
**go upgrade to 1.21.7
**rust upgrade to 1.75
**change to bmaptool hosting
**using ipk to generate poky-altcfg images with extra space added
**6.6.20 stable kernel update
**ability to use “extratools” on autobuilder for tests (e.g. imagemagick components)
*Changes still needed or under consideration
**genericarm64 helper artefacts publishing changes
**QA screenshot comparison
**QA screenshot comparison
**sstate permissions issue testcase
**sstate permissions issue testcase
*Several changes have merged for M3:
**go upgrade to 1.22 (tests cleanly on oe-core now, concerns for other layers)
**ncurses based task dependency explorer (thanks David!)
*We are seeing some odd failures, there was a devtool selftest failure (bug 15418 filed) and also an opkg lock issue as we enabled ipk images but that hasn’t recurred (yet). The opkg lock issue has been seen in builds by Khem previously.
**change to rust test suite logging
*There is a concerning problem when trying to update the CVE database since CPE restrictions don’t always update when changed upstream. This is causing higher numbers of CVEs to be reported on the autobuilder generated charts.
**useradd fix
**dbus configuration security fix
**bitbake hashserve improvements to better position future server capability/functionality
**tweaks to support recipe locale support
**support for BB_LOADFACTOR_MAX load regulation in bitbake when psi is unavailable.
**further IDE integration tweaks and improvements
*There are also several concerning issues without any clear resolution path at present:
**rust upgrade blocked by reproducibility issues
**musl upgrade blocked by large number of unsubmitted pending patches
**nativesdk-systemd usage broken by usrmerge requirement (we can’t changing the SDK layout now)
**go isn't upgraded (although there now are partial patches)
*There have been questions about official RISC-V support in this next release, especially since it is an LTS. We will trial qemuriscv64 support in M3 but remove it before the final LTS release as there is no sponsor for that support.
*There have been questions about official RISC-V support in this next release, especially since it is an LTS. We will trial qemuriscv64 support in M3 but remove it before the final LTS release as there is no sponsor for that support.


Line 47: Line 45:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.3.3 is ready for release.
*YP 4.3.3 was released.
*YP 3.1.32 build date 2024/03/04
*YP 3.1.32 is in QA.
*YP 3.1.32 Release date 2024/03/15
*YP 3.1.32 Release date 2024/03/15
*YP 4.0.17 build date 2024/03/11
*YP 4.0.17 build date 2024/03/11
Line 62: Line 60:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2633 (last week 2636) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2618 (last week 2633) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1144 (last week 1145)
**Total patches found: 1155 (last week 1144)
**Patches in the Pending State: 250 (22%) [last week 250 (22%)]
**Patches in the Pending State: 249 (22%) [last week 250 (22%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/



Revision as of 15:39, 5 March 2024

Yocto Project Weekly Status March 5th, 2024

Current Dev Position: YP 5.0 M3 - Feature Freeze
Next Deadline: 19th February 2024 YP 5.0 M3 build

Next Team Meetings:

Key Status/Updates:

  • We are now at feature freeze for 5.0, preparing to build M3
  • YP 4.3.3 was released
  • YP 3.1.32 is in QA
  • Several changes have merged for M3:
    • genericarm64 machine (also added to autobuilder)
    • go upgrade to 1.21.7
    • rust upgrade to 1.75
    • change to bmaptool hosting
    • using ipk to generate poky-altcfg images with extra space added
    • 6.6.20 stable kernel update
    • ability to use “extratools” on autobuilder for tests (e.g. imagemagick components)
  • Changes still needed or under consideration
    • genericarm64 helper artefacts publishing changes
    • QA screenshot comparison
    • sstate permissions issue testcase
    • go upgrade to 1.22 (tests cleanly on oe-core now, concerns for other layers)
  • We are seeing some odd failures, there was a devtool selftest failure (bug 15418 filed) and also an opkg lock issue as we enabled ipk images but that hasn’t recurred (yet). The opkg lock issue has been seen in builds by Khem previously.
  • There is a concerning problem when trying to update the CVE database since CPE restrictions don’t always update when changed upstream. This is causing higher numbers of CVEs to be reported on the autobuilder generated charts.
  • There have been questions about official RISC-V support in this next release, especially since it is an LTS. We will trial qemuriscv64 support in M3 but remove it before the final LTS release as there is no sponsor for that support.

Ways to contribute:

YP 5.0 Milestone Dates:

  • YP 5.0 M3 build date 2024/02/19
  • YP 5.0 M3 Release date 2024/03/01
  • YP 5.0 M4 build date 2024/04/01
  • YP 5.0 M4 Release date 2024/04/30

Upcoming dot releases:

  • YP 4.3.3 was released.
  • YP 3.1.32 is in QA.
  • YP 3.1.32 Release date 2024/03/15
  • YP 4.0.17 build date 2024/03/11
  • YP 4.0.17 Release date 2024/03/22
  • YP 4.3.4 build date 2024/03/25
  • YP 4.3.4 Release date 2024/04/05
  • YP 3.1.33 build date 2024/04/15
  • YP 3.1.33 Release date 2024/04/26
  • YP 4.0.18 build date 2024/04/22
  • YP 4.0.18 Release date 2024/05/03
  • YP 4.0.19 build date 2024/06/03
  • YP 4.0.19 Release date 2024/06/14

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Archives