Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(392 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Aug. 25, 2020 ==
== Yocto Project Weekly Status May 14th, 2024 ==
Current Dev Position: YP 3.2 M3<br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: YP 3.2 M3 build date 2020/8/31 - FEATURE FREEZE<br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Aug 27th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday May 16th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Sept. 1st at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday May 14th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Aug 25th at 8am PDT (https://zoom.us/j/990892712)
*Twitch -  See https://www.twitch.tv/theyoctojester
*Twitch -  See https://www.twitch.tv/theyoctojester


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.0.4 was released
*YP 4.0.18 has been released
*M3 is due to close at the end of the week and this is the feature freeze point for 3.2
*YP 5.0.1 rc2 is in QA.
*After much debugging, we’ve concluded the bitbake cooker/server launch process is terminally flawed, you can’t fork a python process into two independent python processes and have the internal python state machinery work correctly. *As such, we’re going to have to make some major changes to the way the bitbake cooker/server startup happens.
*YP 5.0.1 rc1 was abandoned due to high numbers of intermittent failures.
*On a positive note, those server changes have forced many of the memory resident bitbake bugs to the surface and the new code appears to fix them, bringing memres bitbake much closer to being usable, maybe even becoming a default in this release if testing goes well.
*There are some CVE related announcements which are helpful to us:
*There is concern about invasive changes like this with regard to LTS/dunfell where these bitbake bugs are also present. Ultimately we will make a decision about backporting based upon patch stability and user feedback from the LTS users.
**There was a CVE 5.1 Record format announcement with changes that encourage more useful data from our perspective
*The number of autobuilder intermittent bugs has continued to rise unfortunately. 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 with any of these would be much appreciated, unfortunately it is proving hard to find anyone interested in helping figure these out and they significantly hamper our testing.
**CISA announced on linkedin the creation of https://github.com/cisagov/vulnrichment
*One way to help the project is to help us with bugs that are currently unassigned but ideally needed during YP 3.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhancements.2FBugs
*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
*There is a proposal on the bitbake list to remove globbing support from file:// urls. Usage of these urls currently breaks source file checksumming which users don’t realise, it can’t be fixed in a sane way so and the most common use cases has easy alternatives such as referencing a directory as a file:// url without globs so removing globbing support appears to be the best way forward.
**Please consider signing this to show support for those changes.
*We have switched to the 5.8 kernel by default, it's taken a while to get through all the different issues but we appear to be there now, thanks to Bruce for working through many of them!
**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.
*Some long standing musl SDK issues should be resolved now.
*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/>
*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 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.
*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.2 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.2 M3 build date 2020/8/31
*WDD 2740 (last week 2720) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.2 M3 Release date 2020/9/11
*OE-Core/Poky Patch Metrics
*YP 3.2 M4 build date 2020/10/5
**Total patches found: 1128 (last week 1125)
*YP 3.2 M4 Release date 2020/10/30
**Patches in the Pending State: 221 (20%) [last week 221 (20%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''Planned upcoming dot releases:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 3.0.4 was released
*YP 5.1 M1 Build date 2024-05-20
*YP 3.1.3 build date 2020/9/14
*YP 5.1 M1 Release date 2024-05-31
*YP 3.1.3 release date 2020/9/25
*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


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2424 (last week 2429) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.0.18 is released.
*Poky Patch Metrics 
*YP 5.0.1 is in QA.
**Total patches found: 1273 (last week 1271)
*YP 4.0.19 build date 2024-06-03
**Patches in the Pending State: 502 (39%) [last week 495 (39%)]
*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 43: Line 77:


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

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"