Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 16th, 2024 ==
== Yocto Project Weekly Status Sept. 10th, 2024 ==
Current Dev Position: YP 5.1 M2 <br/>
Current Dev Position: YP 5.1 Feature Freeze and Bug Fixing<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<br/>
Next Deadline: YP 5.1 M4 Build 30 Sept. 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday July 18th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday Sept. 12th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday July 16th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync Tuesday Sept. 10th at 8 am PST (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.20 is in QA
*YP 5.1 M3 is due to be released
*YP 5.1 M2 is due to be built now SPDX 3.0 has merged
*YP 4.0.21 is in QA
*SPDX 3.0 has merged, thanks Joshua, Marta and everyone else who has worked on this.
*We are now at feature freeze and working on bug fixing for the final 5.1 release builds
*We’ve chosen to make SPDX 3.0 the default since it is much more suited to what we do.
*Due to timing of autobuilder infrastructure changes, vacations, no release blocking bugs and also seemingly limited availability of people to help with general bug fixing, we are considering an early M4 build, maybe even this week. If that would cause problems for anyone, please let Richard/the TSC know ASAP.
*A number of QA checks were moved from WARN_QA to ERROR_QA. The intention is to allow recipes to be marked up with known issues rather than have builds with warnings people tend to ignore, or ideally have the issues fixed.
*Support for TCLIBCAPPEND was dropped.
*If layers choose to change ERROR_QA, please do it on a per layer basis with an override, not globally,
*We updated to only support the “styhead” layer series namespace.
*An upcoming version of Yocto Project Compatible will require some subset of the ERROR_QA checks to be tested and passed for the layer to be compatible.
*The new autobuilder infrastructure is showing a number of challenges including some new bugs, new intermittent issues, challenges with new distros and a new reproducibility issue but we’re working through them
*Debug optimization handling was changed, the DEBUG_FLAGS variable was dropped in favor of a new DEBUG_LEVELFLAG which allows distros to more easily change recipe debug levels, in particular to control size.
*There is discussion around configuration file markup/syntax related to fragment management on the architecture list, targeting 5.2.
*The autobuilder has been running into space issues and we analyzed space usage in a build. Patches are proposed to drop the debug symbols for on target llvm to reduce space usage (along with teaks to qemu and openssl) as the output size is effectively unusable currently. Further work on minimizing disk usage would be very welcome and there is a direct relationship with build speed too.
*Upcoming Event: For those attending OSS EU in Vienna, Yocto Project Developer Day Sept. 19th 9am-5pm. 
*Autobuilder test result/output indexing has been moved to a specific autobuilder job so the work is more visible to all users (the ‘indexing’ builder). The script has been optimized and the output html cleaned up by Sovereign Tech *Fund sponsorship through their contractors: https://autobuilder.yocto.io/pub/non-release/
*Register here: https://events.linuxfoundation.org/open-source-summit-europe/features/co-located-events/#yocto-project-developer-day
*Some larger patches still need help with review these would be appreciated:
**Improved CVE tooling from Marta
**kernel fitimage changes from Adrian
**bitbake-setup and configuration fragments from Alexander
*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
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc. We tested rust 1.78 with master and there is a long list of reported issues on the mailing list unfortunately. Rust 1.77 has a much smaller list of problems at least in initial testing.


'''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 is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
*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.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_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
Line 36: Line 31:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2787 (last week 2822) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2734 (last week 2764) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1082 (last week 1075)
**Total patches found: 1067 (last week 1057)
**Patches in the Pending State: 178 (16%) [last week 178 (17%)]
**Patches in the Pending State: 176 (16%) [last week 177 (17%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 5.1 Milestone Dates:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 5.1 M2 Build date 2024-07-08
*YP 5.1 M3 is ready for release.
*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 Build date 2024-09-30
*YP 5.1 M4 Release date 2024-10-25
*YP 5.1 M4 Release date 2024-10-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.20 is in QA
*YP 4.0.21 is in QA.
*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 Build Date 2024-09-23
*YP 5.0.4 Release Date 2024-10-04
*YP 5.0.4 Release Date 2024-10-04

Latest revision as of 14:51, 10 September 2024

Yocto Project Weekly Status Sept. 10th, 2024

Current Dev Position: YP 5.1 Feature Freeze and Bug Fixing
Next Deadline: YP 5.1 M4 Build 30 Sept. 2024

Next Team Meetings:

Key Status/Updates:

  • YP 5.1 M3 is due to be released
  • YP 4.0.21 is in QA
  • We are now at feature freeze and working on bug fixing for the final 5.1 release builds
  • Due to timing of autobuilder infrastructure changes, vacations, no release blocking bugs and also seemingly limited availability of people to help with general bug fixing, we are considering an early M4 build, maybe even this week. If that would cause problems for anyone, please let Richard/the TSC know ASAP.
  • Support for TCLIBCAPPEND was dropped.
  • We updated to only support the “styhead” layer series namespace.
  • The new autobuilder infrastructure is showing a number of challenges including some new bugs, new intermittent issues, challenges with new distros and a new reproducibility issue but we’re working through them
  • There is discussion around configuration file markup/syntax related to fragment management on the architecture list, targeting 5.2.
  • Upcoming Event: For those attending OSS EU in Vienna, Yocto Project Developer Day Sept. 19th 9am-5pm.
  • Register here: https://events.linuxfoundation.org/open-source-summit-europe/features/co-located-events/#yocto-project-developer-day

Ways to contribute:

  • 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 is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
  • 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.

Tracking Metrics:

YP 5.1 Milestone Dates:

  • YP 5.1 M3 is ready for release.
  • YP 5.1 M4 Build date 2024-09-30
  • YP 5.1 M4 Release date 2024-10-25

Upcoming dot releases:

  • YP 4.0.21 is in QA.
  • 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=86442"