Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 23rd, 2024 ==
== Yocto Project Weekly Status May 7th, 2024 ==
Current Dev Position: YP 5.0 preparing to build rc2 <br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: 1st April 2024 YP 5.0 M4 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 April 25th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday May 9th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday April 23rd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday May 7th 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 rc1 is building but has many (6+) failures in the build so will have to be abandoned.
*YP 3.1.33 has been released
*The final dunfell build will follow 5.0 into QA.
*YP 4.0.18 is due to be released
*The master branch has diverged from scarthgap.
*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.
*For 5.0, we were able to switch to the new hash equivalence server however the need for websockets complicated the worker configuration and needed new buildtools tarball versions which are causing various problems.
*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.  
*During the rc1 build as well as pip and setuptools issues within buildtools, we also saw a qemuppc boot issue, an instance of the spdx dependency problem, an sstate mirror issue and a github network error. This highlights how important fixing these is over the release cycle. The volume of these may impact our ability to maintain the LTS.
*There are proposals on the openembedded-architecture list to rework how do_unpack works, switching it from WORKDIR to a new variable and changing some directory layout.  
*Thanks to everyone who sent documentation patches, we’re in much better shape with the migration guide and release notes now. Further improvements are still very welcome.
*The introduction of UNPACKDIR has happened, maintainers should be able to improve their S=WORKDIR recipes (which should use S, not WORKDIR/UNPACKDIR) and fix the common use of WORKDIR in do_compile/do_install to access files from SRC_URI which should now be UNPACKDIR.
*The “Binary Distro” work is now well underway and there are PR Server passthrough and image testing patches under review. The wiki page has had a number of policy/process proposals documented, help is welcome to help improve these, or highlight where further documentation is needed.
*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.
*There are patches for improving the build performance graphs in review. Sample output from the changes is here and here.
*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.
*There are also patches under review for the patch/cve metrics page to improve the usability.
*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.
*We continue to watch the NIST NVD (CVE database) situation, the recent update didn’t clarify much. Unfortunately there doesn’t appear to be a clear path forward as yet but using data directly from MITRE may help give partial information. These issues are making it hard to know what to include in the 5.0 release as it isn’t clear which changes are security related.


'''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!
*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.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 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 29: 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 5.0 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 5.0 is in QA
*WDD 2720 (last week 2728) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0 M4 Release date 2024/04/30
*OE-Core/Poky Patch Metrics
**Total patches found: 1125 (last week 1125)
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''YP 5.1 Proposed Milestone Dates:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 5.1 M1 Build date 2024-05-20
*YP 5.1 M1 Build date 2024-05-20
*YP 5.1 M1 Release date 2024-05-31
*YP 5.1 M1 Release date 2024-05-31
Line 44: Line 46:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.33 is in QA
*YP 3.1.33 is released.
*YP 3.1.33 Release date 2024-04-26
*YP 4.0.18 is ready for release.
*YP 4.0.18 is in QA
*YP 4.0.18 Release date 2024-05-03
*YP 4.0.18 Release date 2024-05-03
*YP 5.0.1 Build Date 2024-05-13
*YP 5.0.1 Build Date 2024-05-13
Line 68: Line 69:
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.23 Release Date 2024-11-29
*YP 4.0.23 Release Date 2024-11-29
'''Tracking Metrics:'''<br/>
*WDD 2714 (last week 2719) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1140 (last week 1173)
**Patches in the Pending State: 249 (21%) [last week 249 (21%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''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/>

Latest revision as of 14:44, 7 May 2024

Yocto Project Weekly Status May 7th, 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 3.1.33 has been released
  • YP 4.0.18 is due to be released
  • 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.
  • There are proposals on the openembedded-architecture list to rework how do_unpack works, switching it from WORKDIR to a new variable and changing some directory layout.
  • The introduction of UNPACKDIR has happened, maintainers should be able to improve their S=WORKDIR recipes (which should use S, not WORKDIR/UNPACKDIR) and fix the common use of WORKDIR in do_compile/do_install to access files from SRC_URI which should now be UNPACKDIR.
  • 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.

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 3.1.33 is released.
  • YP 4.0.18 is ready for release.
  • YP 4.0.18 Release date 2024-05-03
  • YP 5.0.1 Build Date 2024-05-13
  • YP 5.0.1 Release Date 2024-05-24
  • 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=86330"