Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(216 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Feb. 15th, 2022 ==
== Yocto Project Weekly Status May 14th, 2024 ==
Current Dev Position: YP 3.5 M3<br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: 21th Feb. 2022 YP 3.5 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 Feb. 17th  at 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)
*Monthly Project Meeting Tuesday Mar. 1st 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)
*Weekly Engineering Sync Tuesday Feb. 15th 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/>
*Next week is feature freeze for 3.5, our next LTS release
*YP 4.0.18 has been released
*YP 3.1.14 passed QA and is due to be released
*YP 5.0.1 rc2 is in QA.
*YP 3.2.4 rc2 is in QA (rc1 had sstate networking issues)
*YP 5.0.1 rc1 was abandoned due to high numbers of intermittent failures.
*We’re extremely worried about the inclusive language changes since these are not anywhere near ready and the freeze deadline is in days. This is an important topic but sadly we’re simply starved of people with the right time and skills to spend on it. There is an email on the openembedded-architecture list about this.
*There are some CVE related announcements which are helpful to us:
*The autobuilder infrastructure is planned to be offline 26-28th February for a data center move. Public services like the website, wiki and git servers will remain live but the git backend (push.yoctoproject.org) will be offline, as will the downloads and sstate services and the autobuilder/NAS.
**There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
*We’ve upgraded to the new glibc version and have patches in testing for the new binutils release assuming some minor issues there are resolved.
**CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
*There are changes proposed to the bitbake git fetcher handling of tags. We resolve these against the upstream repositories and the caching of the values was showing issues such as network accesses in the unpack task. We advice against using tags due to the potential for them to change, any layers using them may seen error messages depending on whether their usage is problematic.
*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 record 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 In particular, we’re struggling to understand the intermittent network issue with external hosts we’re seeing very occasionally.
**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:'''<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 3.5 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.5 M3 build date 2022/02/21
*WDD 2740 (last week 2720) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.5 M3 Release date 2022/03/04
*OE-Core/Poky Patch Metrics
*YP 3.5 M4 build date 2022/04/04
**Total patches found: 1128 (last week 1125)
*YP 3.5 M4 Release date 2022/04/29
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
*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/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.14 is out of QA
*YP 4.0.18 is released.
*YP 3.4.2 is in QA
*YP 5.0.1 is in QA.
*YP 3.4.2 Release date 2022/02/18
*YP 4.0.19 build date 2024-06-03
*YP 3.3.5 build date 2022/02/14
*YP 4.0.19 Release date 2024-06-14
*YP 3.3.5 Release date 2022/02/25
*YP 5.0.2 Build Date 2024-06-24
*YP 3.1.15 build date 2022/03/14
*YP 5.0.2 Release Date 2024-07-05
*YP 3.1.15 Release date 2022/03/25
*YP 4.0.20 Build Date 2024-07-15
*YP 3.4.3 build date 2022/03/21
*YP 4.0.20 Release Date 2024-07-26
*YP 3.4.3 Release date 2022/04/01
*YP 5.0.3 Build Date 2024-08-12
*YP 3.3.6 build date 2022/03/28
*YP 5.0.3 Release Date 2024-08-23
*YP 3.3.6 Release date 2022/04/08
*YP 4.0.21 Build Date 2024-09-09
*YP 3.1.16 build date 2022/04/25
*YP 4.0.21 Release Date 2024-09-20
*YP 3.1.16 Release date 2022/05/06
*YP 5.0.4 Build Date 2024-09-23
 
*YP 5.0.4 Release Date 2024-10-04
'''Tracking Metrics:'''<br/>
*YP 4.0.22 Build Date 2024-10-14
*WDD 2662 (last week 2665) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.0.22 Release Date 2024-10-25
*Poky Patch Metrics
*YP 5.0.5 Build Date 2024-11-11
**Total patches found: 1208 (last week 1213)
*YP 5.0.5 Release Date 2024-11-22
**Patches in the Pending State: 334 (28%) [last week 338 (28%)]
*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 56: 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"