Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(202 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Apr. 12th, 2022 ==
== Yocto Project Weekly Status June 4th, 2024 ==
Current Dev Position: YP 4.1 M1<br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: 30th May 2022 YP 4.1 M1 build<br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Apr. 14th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday June 6th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday May 3rd at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday June 4th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Apr. 12th 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/>
*The next release, kirkstone will be 4.0 (previously known as 3.5) and will be bitbake 2.0 based.
*YP 4.0.19 is in QA
*The first release candidate build for YP 4.0 (3.5) is in QA but has at least one issue which will mean we need a second release candidate build. We will build that after the final QA report is back.
*YP 5.1 M1 rc1 is building
*YP 3.3.6, the final hardknott release will build after 4.0 rc2.
*We identified the performance problem in bitbake using hash equivalence servers and have made changes to batch queries and improve build times
*There are several issues which have arisen in the last week which mean we will need a second release candidate build:
*Extra logging for that performance problem is available by setting BB_LOGCONFIG=XXX/bitbake/contrib/autobuilderlog.json (the more verbose logging the autobuilder uses) which will then show if initial query or rehash looping takes longer than 30s for iterations or 60s overall.
**edgerouter didn’t boot with rc1 due to a kernel patch issue
*We changed locked-sigs to include the hash equivalence mapping data, removing the need to copy the cache file.
**uninative didn’t work with libstdc++ from gcc 12 so we have an upgraded version
*Libtool was upgraded to the 2.5.0 alpha release, many patches were merged upstream.
**there were several CVE fixes that came in (libarchive, gzip, xz)
*Qemu has been upgraded to 9.0.0, kernel headers to 6.9 and stable and dev kernel updates merged (to 6.6.32)
**a key intermittent autobuilder fix was identified
*There is one remaining issue on fedora40, systemtap-native does not build. The other Fedora 40 are believed to be fixed.
  Not all of these were release blockers but together they mean an rc2 is appropriate.
*Some layers are setting fallbacks for UNPACKDIR which break OE-Core by trying to claim compatibility with everything. Errors have been added to make this problem clear.
*If anyone is aware of other issues in rc1 that need to be addressed in rc2, please let us know ASAP.
*sstate has had changes to fix a bug where build-history data was inconsistent. The siteconfig class was removed to make that change easier and improve the code, it was mostly unused anyway.
*YP 4.1 planning document is available for review at: https://docs.google.com/document/d/1-g7DatSdmIETwD3xFSCxV7MbWVVkpQvQ788mIr1MPTI/edit?usp=sharing
*The parallelism in the hash client was removed as batching queries is much more effective and easier on the server.
*If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
*There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
*Intermittent issues continue to be at high levels and help is very much welcome in trying to resolve them. 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 We did work out the cause of the infamous tinfoil wait_event intermittent issue.
*Please consider signing this to show support for those changes.
*Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
*There is a further update from Marta/Syslinbit on the CVE tooling/patches
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
*Post release upgrading is resulting in an improvement in patch metrics which is great to see, more should appear next week in the statistics too.


'''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!
*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 3.5. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhancements.2FBugs
*There are bugs that are currently unassigned for YP 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_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 us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
*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 us resolve CVE issues: CVE metrics
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''YP 4.0 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 4.0 is in QA
*WDD 2772 (last week 2772) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.0 M4 Release date 2022/04/29
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1121)
**Patches in the Pending State: 205 (19%) [last week 221 (20%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''YP 4.1 Milestone Dates:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 4.1 M1 build date 2022/05/30
*YP 5.1 M1 Build date 2024-05-20
*YP 4.1 M1 Release date 2022/06/10
*YP 5.1 M1 Release date 2024-05-31
*YP 4.1 M2 build date 2022/07/11
*YP 5.1 M2 Build date 2024-07-08
*YP 4.1 M2 Release date 2022/07/22
*YP 5.1 M2 Release date 2024-07-19
*YP 4.1 M3 build date 2022/08/22
*YP 5.1 M3 Build date 2024-08-26
*YP 4.1 M3 Release date 2022/09/02
*YP 5.1 M3 Release date 2024-09-06
*YP 4.1 M4 build date 2022/10/03
*YP 5.1 M4 Build date 2024-09-30
*YP 4.1 M4 Release date 2022/10/28
*YP 5.1 M4 Release date 2024-10-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.3.6 build date 2022/03/28
*YP 4.0.19 is in QA.
*YP 3.3.6 Release date 2022/04/08
*YP 5.0.2 Build Date 2024-06-24
*YP 3.1.16 build date 2022/04/25
*YP 5.0.2 Release Date 2024-07-05
*YP 3.1.16 Release date 2022/05/06
*YP 4.0.20 Build Date 2024-07-15
*YP 3.4.4 build date 2022/05/02
*YP 4.0.20 Release Date 2024-07-26
*YP 3.4.4 Release date 2022/05/13
*YP 5.0.3 Build Date 2024-08-12
*YP 4.0.1 build date 2022/05/16
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.1 Release date 2022/05/27
*YP 4.0.21 Build Date 2024-09-09
*YP 3.1.17 build date 2022/06/06
*YP 4.0.21 Release Date 2024-09-20
*YP 3.1.17 Release date 2022/06/17
*YP 5.0.4 Build Date 2024-09-23
*YP 4.0.2 build date 2022/06/27
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.2 Release date 2022/07/08
*YP 4.0.22 Build Date 2024-10-14
*YP 3.1.18 build date 2022/07/18
*YP 4.0.22 Release Date 2024-10-25
*YP 3.1.18 Release date 2022/07/29
*YP 5.0.5 Build Date 2024-11-11
*YP 4.0.3 build date 2022/08/08
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.3 Release date 2022/08/19
*YP 4.0.23 Build Date 2024-11-18
*YP 3.1.19 build date 2022/08/29
*YP 4.0.23 Release Date 2024-11-29
*YP 3.1.19 Release date 2022/09/09
*YP 4.0.4 build date 2022/09/19
*YP 4.0.4 Release date 2022/09/30
*YP 3.1.20 build date 2022/10/10
*YP 3.1.20 Release date 2022/10/21
*YP 4.0.5 build date 2022/10/31
*YP 4.0.5 Release date 2022/11/11
 
'''Tracking Metrics:'''<br/>
*WDD 2597 (last week 2589) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
**Total patches found: 1203 (last week 1200)
**Patches in the Pending State: 343 (29%) [last week 342 (28%)]


'''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/>
Line 80: Line 76:


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

Latest revision as of 14:49, 4 June 2024

Yocto Project Weekly Status June 4th, 2024

Current Dev Position: YP 5.1 M1
Next Deadline: YP 5.1 M1 Build 20 May 2024

Next Team Meetings:

Key Status/Updates:

  • YP 4.0.19 is in QA
  • YP 5.1 M1 rc1 is building
  • We identified the performance problem in bitbake using hash equivalence servers and have made changes to batch queries and improve build times
  • Extra logging for that performance problem is available by setting BB_LOGCONFIG=XXX/bitbake/contrib/autobuilderlog.json (the more verbose logging the autobuilder uses) which will then show if initial query or rehash looping takes longer than 30s for iterations or 60s overall.
  • We changed locked-sigs to include the hash equivalence mapping data, removing the need to copy the cache file.
  • Libtool was upgraded to the 2.5.0 alpha release, many patches were merged upstream.
  • Qemu has been upgraded to 9.0.0, kernel headers to 6.9 and stable and dev kernel updates merged (to 6.6.32)
  • There is one remaining issue on fedora40, systemtap-native does not build. The other Fedora 40 are believed to be fixed.
  • Some layers are setting fallbacks for UNPACKDIR which break OE-Core by trying to claim compatibility with everything. Errors have been added to make this problem clear.
  • sstate has had changes to fix a bug where build-history data was inconsistent. The siteconfig class was removed to make that change easier and improve the code, it was mostly unused anyway.
  • The parallelism in the hash client was removed as batching queries is much more effective and easier on the server.
  • There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
  • Please consider signing this to show support for those changes.
  • Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
  • There is a further update from Marta/Syslinbit on the CVE tooling/patches
  • We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
  • Post release upgrading is resulting in an improvement in patch metrics which is great to see, more should appear next week in the statistics too.

Ways to contribute:

Tracking Metrics:

YP 5.1 Milestone Dates:

  • YP 5.1 M1 Build date 2024-05-20
  • YP 5.1 M1 Release date 2024-05-31
  • YP 5.1 M2 Build date 2024-07-08
  • YP 5.1 M2 Release date 2024-07-19
  • YP 5.1 M3 Build date 2024-08-26
  • YP 5.1 M3 Release date 2024-09-06
  • YP 5.1 M4 Build date 2024-09-30
  • YP 5.1 M4 Release date 2024-10-25

Upcoming dot releases:

  • YP 4.0.19 is in QA.
  • YP 5.0.2 Build Date 2024-06-24
  • YP 5.0.2 Release Date 2024-07-05
  • YP 4.0.20 Build Date 2024-07-15
  • YP 4.0.20 Release Date 2024-07-26
  • YP 5.0.3 Build Date 2024-08-12
  • YP 5.0.3 Release Date 2024-08-23
  • YP 4.0.21 Build Date 2024-09-09
  • YP 4.0.21 Release Date 2024-09-20
  • YP 5.0.4 Build Date 2024-09-23
  • YP 5.0.4 Release Date 2024-10-04
  • YP 4.0.22 Build Date 2024-10-14
  • YP 4.0.22 Release Date 2024-10-25
  • YP 5.0.5 Build Date 2024-11-11
  • YP 5.0.5 Release Date 2024-11-22
  • YP 4.0.23 Build Date 2024-11-18
  • YP 4.0.23 Release Date 2024-11-29

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