Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(52 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status August 23rd, 2023 ==
== Yocto Project Weekly Status March 26th, 2024 ==
Current Dev Position: YP 4.3 M3<br/>
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Next Deadline: 28th August 2023 YP 4.3 M3 build date<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday August 25th 8 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 August 23rd 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 two weeks away from feature freeze for 4.3.
*YP 5.0 M3 has been released.
*YP 3.1.27 was released
*YP 4.0.17 is under review and due for release.
*YP 4.0.12 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.
*The 6.4 kernel upgrade is still blocked as we’ve seen two nasty looking hangs in automated testing: https://autobuilder.yoctoproject.org/typhoon/#/builders/148/builds/349/steps/12/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/148/builds/354/steps/12/logs/stdio as well as a preempt-rt boot error that appears more consistently: https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/7616/steps/36/logs/stdio The intermittent issues are a significant risk to automated testing stability and it is hard to know how to proceed as few people are willing/able to help with them. We’ve upgraded qemu 8.0.3 -> 8.0.4 just in case that helps.
*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.
*The various systemd issues have mostly been resolved although the AUH did break as a result and will have to be fixed and rerun.
*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.
*Build layout changed slightly with the removal of PE and PR from the WORKDIR path.
*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 are patches pending which remove source control revisions from PV and move them to PKGV, further simplifying WORKDIR paths and generally improving the code and the way AUTOREV works. This allows SRCPV to be removed as it is no longer needed.
*The opkg lock issue is now understood but the best fix is still under discussion/ development.
*Significant fixes were made to both the binutils and gcc testsuites which avoid many of the mips toolchain test failures. The failure counts are roughly the same (few hundred) for each architecture now resulting in ~3200 failures overall.  
*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.
*There are now consistently ~200 ltp ‘controllers’ failures on both arm and x86 targets.
*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”)
*A new uninative version was released to add some patches to patchelf to avoid bugs.
*A new test addition to oe-selftest caused another test to fail consistently on the autobuilder and this has been tracked down to one test corrupting the other if they run in the same TMPDIR. This only happens with specific parallelism settings where they happen to run together or with no parallelism.
*We continue to see intermittent ptest failures for glib-networking, mdadm and openssh, help would be much appreciated.
*CVE metrics are worrying with significant numbers of open CVEs against master, many of them kernel related. The 6.4 upgrade should help but that is blocked. Mickledore is also badly affected with a record high count. https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''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 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
*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
*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 32: Line 28:
*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.


'''YP 4.3 Milestone Dates:'''<br/>
'''YP 5.0 Milestone Dates:'''<br/>
*YP 4.3 M3 build date  2023/08/28
*YP 5.0 M3 is released.
*YP 4.3 M3 Release date 2023/09/08
*YP 5.0 M4 build date  2024/04/01
*YP 4.3 M4 build date  2023/10/02
*YP 5.0 M4 Release date 2024/04/30
*YP 4.3 M4 Release date 2023/10/27


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.12 is ready for release
*YP 4.0.17 is out of QA.
*YP 4.2.3 is in QA
*YP 4.3.4 build date 2024/03/25
*YP 3.1.28 build date 2023/09/18
*YP 4.3.4 Release date 2024/04/05
*YP 3.1.28 Release date 2023/09/29
*YP 3.1.33 build date 2024/04/15
*YP 4.0.13 build date 2023/09/25
*YP 3.1.33 Release date 2024/04/26
*YP 4.0.13 Release date 2023/10/06
*YP 4.0.18 build date 2024/04/22
*YP 3.1.29 build date 2023/10/30
*YP 4.0.18 Release date 2024/05/03
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.19 build date 2024/06/03
*YP 4.0.14 build date 2023/11/06
*YP 4.0.19 Release date 2024/06/14
*YP 4.0.14 Release date 2023/11/17
*YP 4.2.4 build date 2023/11/13
*YP 4.2.4 Release date 2023/11/24
*YP 3.1.30 build date 2023/12/11
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2488 (last week 2463) (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: 1183 (last week 1186)
**Total patches found: 1156 (last week 1148)
**Patches in the Pending State: 258 (22%) [last week 255 (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/


Line 67: Line 55:


== Archives ==
== Archives ==
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]

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

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86276"