Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(166 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status August 23rd, 2022 ==
== Yocto Project Weekly Status May 14th, 2024 ==
Current Dev Position: YP 4.1 M3 (Feature Freeze)<br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: 22nd August 2022 YP 4.1 M3 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 August 25th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday May 16th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday August 23rd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday May 14th 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 4.0.3 has been through QA with a clean report and is likely to be released
*YP 4.0.18 has been released
*The CVE count for master rose sharply this week but a number of fixes were sent by Khem, thanks!
*YP 5.0.1 rc2 is in QA.
*Bitbake changes in class handling merged which means classes can now be enforced to be in “global” or “recipe” scope. This handles a long standing usability issue of it not being clear which scope classes should be used in. For example, “testimage” now needs to be included via IMAGE_CLASSES and not via INHERIT. Global class inclusions in recipes such as “base” and “package” will now show a parsing error. “base” was particularly pointless and can simply be removed as it was always inherited.
*YP 5.0.1 rc1 was abandoned due to high numbers of intermittent failures.
*The rust toolchain changes merged and are now being tested by default on the autobuilder but there is one intermittent issue with shebang length overflow in the SDK which still needs to be resolved
*There are some CVE related announcements which are helpful to us:
*We upgraded glibc to 2.36 and produced a new uninative version which supports this.
**There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
*There are patches out for review for the debug path improvements. These rely on a gcc patch and small change of gcc behavior which is being discussed with upstream.
**CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
*There were cleanups to copyright and license headers in OE-Core and Bitbake.
*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
*“largefile” support in oe-core was cleaned up and removed as we assume this everywhere now, completing something we said would happen in release notes a few years ago.
**Please consider signing this to show support for those changes.
*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
**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.
*The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date.  
*The WORKDIR to UNPACKDIR transition and redefinition of UNPACKDIR now has patches under testing in master-next, including updates to recipetool and devtool which pass our automated tests.
*gcc 14 has patches pending thanks for Khem and Martin in particular. Merging the new gcc version is needed to generate new uninative tarballs to support Fedora 40 builds or any other distro using the new gcc version.
*The project is in the process of testing a new way of hosting our autobuilder with plans to switch soon if successful. Our existing hardware is past end of life and showing increased hardware failures so is currently down on capacity meaning builds are taking longer than normal.
*Mailing list changes now mean any google hosted email accounts have the mailing list From: address rewritten. This had impacted our ability to handle patches but key maintainers now have workarounds for this.
*Our automated tests have been seeing a number of intermittent issues. An email was sent detailing a few of these and the response with several patches or patches in progress has been extremely helpful and they’re very gratefully received.


'''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 4.1 See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_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
'''YP 4.1 Milestone Dates:'''<br/>
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*YP 4.1 M3 build date 2022/08/22
*YP 4.1 M3 Release date 2022/09/02
*YP 4.1 M4 build date 2022/10/03
*YP 4.1 M4 Release date 2022/10/28
 
'''Upcoming dot releases:'''<br/>
*YP 4.0.3 is released
*YP 3.1.19 is in QA
*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/>
'''Tracking Metrics:'''<br/>
*WDD 2482 (last week 2447) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2740 (last week 2720) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1212 (last week 1188)
**Total patches found: 1128 (last week 1125)
**Patches in the Pending State: 329 (27%) [last week 322 (28%)]
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
'''YP 5.1 Milestone Dates:'''<br/>
*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:'''<br/>
*YP 4.0.18 is released.
*YP 5.0.1 is in QA.
*YP 4.0.19 build date 2024-06-03
*YP 4.0.19 Release date 2024-06-14
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 53: Line 77:


== 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:38, 14 May 2024

Yocto Project Weekly Status May 14th, 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.18 has been released
  • YP 5.0.1 rc2 is in QA.
  • YP 5.0.1 rc1 was abandoned due to high numbers of intermittent failures.
  • There are some CVE related announcements which are helpful to us:
    • There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
    • CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
  • 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.
  • The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date.
  • The WORKDIR to UNPACKDIR transition and redefinition of UNPACKDIR now has patches under testing in master-next, including updates to recipetool and devtool which pass our automated tests.
  • gcc 14 has patches pending thanks for Khem and Martin in particular. Merging the new gcc version is needed to generate new uninative tarballs to support Fedora 40 builds or any other distro using the new gcc version.
  • The project is in the process of testing a new way of hosting our autobuilder with plans to switch soon if successful. Our existing hardware is past end of life and showing increased hardware failures so is currently down on capacity meaning builds are taking longer than normal.
  • Mailing list changes now mean any google hosted email accounts have the mailing list From: address rewritten. This had impacted our ability to handle patches but key maintainers now have workarounds for this.
  • Our automated tests have been seeing a number of intermittent issues. An email was sent detailing a few of these and the response with several patches or patches in progress has been extremely helpful and they’re very gratefully received.

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.18 is released.
  • YP 5.0.1 is in QA.
  • YP 4.0.19 build date 2024-06-03
  • YP 4.0.19 Release date 2024-06-14
  • 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=86336"