Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status March 5th, 2024 ==
== Yocto Project Weekly Status March 26th, 2024 ==
Current Dev Position: YP 5.0 M3 - Feature Freeze <br/>
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Next Deadline: 19th February 2024 YP 5.0 M3 build<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday March 7th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday March 28th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday March 5th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday March 26th 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
*YP 5.0 M3 has been released.
*YP 4.3.3 was released
*YP 4.0.17 is under review and due for release.
*YP 3.1.32 is in QA
*Steve is taking patches for Dunfell until around April 8 in preparation for an April 15 build. This will be the last release of dunfell.
*Several changes have merged for M3:
*There was a regression on beaglebone in 5.0 M3 where X11 wasn’t working but this has been fixed in master ready for the release.
**genericarm64 machine (also added to autobuilder)
*A key worry now is the documentation for the release, especially given it is an LTS. There are emails on the docs list about this, help is much appreciated.
**go upgrade to 1.21.7
*For M4, we are still hoping to transition to a different public hash equivalence server before release. We have stopped taking general point release upgrades to recipes unless there is a security or other key reason to take them. *The key remaining fix needed before building is for the opkg lock issue.
**rust upgrade to 1.75
*The opkg lock issue is now understood but the best fix is still under discussion/ development.
**change to bmaptool hosting
*One set of the problematic autobuilder failures was tracked down to a queued but  unmerged bitbake patch. There are other intermittent issues which still need to be root caused, at least one failure was also due to system load issues.
**using ipk to generate poky-altcfg images with extra space added
*We continue to watch the NIST NVD (CVE database) issue and await further information about what the future holds there (https://nvd.nist.gov/  - “You will temporarily see delays in analysis efforts during this transition”)
**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:'''<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: patchtest, layerindex, 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 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.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
*There are bugs that are currently unassigned for YP 5.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
Line 39: Line 29:


'''YP 5.0 Milestone Dates:'''<br/>
'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 M3 build date  2024/02/19
*YP 5.0 M3 is released.
*YP 5.0 M3 Release date 2024/03/01
*YP 5.0 M4 build date  2024/04/01
*YP 5.0 M4 build date  2024/04/01
*YP 5.0 M4 Release date 2024/04/30
*YP 5.0 M4 Release date 2024/04/30


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.3.3 was released.
*YP 4.0.17 is out of QA.
*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 build date 2024/03/25
*YP 4.3.4 Release date 2024/04/05
*YP 4.3.4 Release date 2024/04/05
Line 60: Line 45:


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



Revision as of 14:43, 26 March 2024

Yocto Project Weekly Status March 26th, 2024

Current Dev Position: YP 5.0 M4 - Final Release
Next Deadline: 1st April 2024 YP 5.0 M4 build

Next Team Meetings:

Key Status/Updates:

  • YP 5.0 M3 has been released.
  • YP 4.0.17 is under review and due for release.
  • Steve is taking patches for Dunfell until around April 8 in preparation for an April 15 build. This will be the last release of dunfell.
  • There was a regression on beaglebone in 5.0 M3 where X11 wasn’t working but this has been fixed in master ready for the release.
  • A key worry now is the documentation for the release, especially given it is an LTS. There are emails on the docs list about this, help is much appreciated.
  • For M4, we are still hoping to transition to a different public hash equivalence server before release. We have stopped taking general point release upgrades to recipes unless there is a security or other key reason to take them. *The key remaining fix needed before building is for the opkg lock issue.
  • The opkg lock issue is now understood but the best fix is still under discussion/ development.
  • One set of the problematic autobuilder failures was tracked down to a queued but unmerged bitbake patch. There are other intermittent issues which still need to be root caused, at least one failure was also due to system load issues.
  • We continue to watch the NIST NVD (CVE database) issue and await further information about what the future holds there (https://nvd.nist.gov/ - “You will temporarily see delays in analysis efforts during this transition”)

Ways to contribute:

YP 5.0 Milestone Dates:

  • YP 5.0 M3 is released.
  • YP 5.0 M4 build date 2024/04/01
  • YP 5.0 M4 Release date 2024/04/30

Upcoming dot releases:

  • YP 4.0.17 is out of QA.
  • 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