Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status March 19th, 2024 ==
== Yocto Project Weekly Status March 26th, 2024 ==
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Next Deadline: 1st April 2024 YP 5.0 M4 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 21st 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 19th 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/>
*YP 5.0 M3 has been through QA. There is one major issue, we will likely release M3 and fix that in M4.
*YP 5.0 M3 has been released.
*YP 4.0.17 is in QA.
*YP 4.0.17 is under review and due for release.
*There is a regression on beaglebone testing where X is no longer starting which was found during M3 QA. Fixes are under discussion for this and will be in M4.
*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.
*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.
*The opkg lock issue with systemd images continues to be a significant concern for the release. We do now have a way to reproduce the bug and it is due to “opkg configure” being executed in a postinstall script whilst opkg install has the lock.
*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.
*There is a uninative issue showing up with newer distros due to the glibc changes where the pthread library is no longer separate. There are patches in testing to try and mitigate against this.
*The opkg lock issue is now understood but the best fix is still under discussion/ development.
*There are multiple other failures occurring on the autobuilder but no specific pattern has been identified as yet. One test build had 4 different failures, and 2 of them were new never seen before issues. There is also some kind of issue with devtool/recipe tool test isolation in selftest which needs to be tracked down.
*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.
*The previously reported CVE database update issue has been mitigated for now but further improvements to the autobuilder process for generating the metrics may still be needed.
*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:'''<br/>
'''Ways to contribute:'''<br/>
Line 28: Line 29:


'''YP 5.0 Milestone Dates:'''<br/>
'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 M3 is ready for release.
*YP 5.0 M3 is released.
*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.0.17 is in QA.
*YP 4.0.17 is out of QA.
*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 44: Line 45:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2706 (last week 2688) (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: 1148 (last week 1148)
**Total patches found: 1156 (last week 1148)
**Patches in the Pending State: 249 (22%) [last week 249 (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