Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(80 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status September 12th, 2023 ==
== Yocto Project Weekly Status Sept. 3rd, 2024 ==
Current Dev Position: YP 4.3 M4 (Feature Freeze)<br/>
Current Dev Position: YP 5.1 Feature Freeze and Bug Fixing<br/>
Next Deadline: 2nd October 2023 YP 4.3 M4 build date<br/>
Next Deadline: YP 5.1 M4 Build 30 Sept. 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday September 14th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*YP 5.1 M3 is in QA
*Weekly Engineering Sync Tuesday September 12th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*We are now at feature freeze and working on bug fixing for the final 5.1 release builds
*Twitch -  See https://www.twitch.tv/theyoctojester
*Some limited recipe upgrades may be taken in M4 depending on their value of bug fixes vs breaking changes/features.
 
*Fixes to make ERROR_QA only rebuild tasks it directly affects were merged, which will improve sstate reuse from the project servers significantly.
'''Key Status/Updates:'''<br/>
*There is discussion around configuration file markup/syntax related to fragment management on the architecture list, targeting 5.2.
*We are now at feature freeze for 4.3 and 4.3 M3 is in QA
*Upcoming Event:  For those attending OSS EU in Vienna, Yocto Project Developer Day Sept. 19th 9am-5pm. 
*The numpy reproducibility issue is not solved unfortunately
*Register here: https://events.linuxfoundation.org/open-source-summit-europe/features/co-located-events/#yocto-project-developer-day
*There are continuing intermittent ptest issues for openssh and glib-networking amongst other issues
*The testing for qemuppc and qemumips/qemumips64 has been reduced and we’re no longer testing core-image-sato-sdk on these platforms.
*SPDX manifests are now enabled by default for OE-Core/nodistro as well as poky.
*Patches have been resubmitted to radically alter the do_unpack process for license compliance reasons. The code is complex and hard to understand and will have a performance impact on builds as well as making things hard to debug. *The risk of not taking the changes is that for some legal departments, the SPDX data isn’t detailed enough. The compromise between performance and ease of use vs. legal requirements is a tough one. We don’t really want to have two codepaths either. Feedback/review on the series welcome.
*We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
**Marta Rybczynska will be working on the security topic
**Alexander Kanvin will be working on the core workflow topic
**Savoir-faire Linux will be working on the toaster and VSCode topics
**BayLibre will be working on the patchtest and project tooling topics
**Michael Opdenacker (Bootlin) will be working on the binary distro topic
**Smile will be working on the meta-openembedded topic area
We’d also note that Tim Orling (Konsulko) will be working on the layer index.


'''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: patchtest, layerindex, 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 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_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 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 33: Line 22:
*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 4.3 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 4.3 M3 is in QA
*WDD 2764 (last week 2759) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.3 M4 build date 2023/10/02
*OE-Core/Poky Patch Metrics
*YP 4.3 M4 Release date 2023/10/27
**Total patches found: 1057 (last week 1070)
**Patches in the Pending State: 176 (17%) [last week 177 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
 
'''YP 5.1 Milestone Dates:'''<br/>
*YP 5.1 M3 in QA.
*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.28 build date 2023/09/18
*YP 4.0.21 Build Date 2024-09-09
*YP 3.1.28 Release date 2023/09/29
*YP 4.0.21 Release Date 2024-09-20
*YP 4.0.13 build date 2023/09/25
*YP 5.0.4 Build Date 2024-09-23
*YP 4.0.13 Release date 2023/10/06
*YP 5.0.4 Release Date 2024-10-04
*YP 3.1.29 build date 2023/10/30
*YP 4.0.22 Build Date 2024-10-14
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.22 Release Date 2024-10-25
*YP 4.0.14 build date 2023/11/06
*YP 5.0.5 Build Date 2024-11-11
*YP 4.0.14 Release date 2023/11/17
*YP 5.0.5 Release Date 2024-11-22
*YP 4.2.4 build date 2023/11/13
*YP 4.0.23 Build Date 2024-11-18
*YP 4.2.4 Release date 2023/11/24
*YP 4.0.23 Release Date 2024-11-29
*YP 3.1.30 build date 2023/12/11
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29
 
'''Tracking Metrics:'''<br/>
*WDD 2530 (last week 2500) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1186 (last week 1185)
**Patches in the Pending State: 255 (22%) [last week 254 (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/>
Line 65: Line 50:


== Archives ==
== Archives ==
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]

Revision as of 14:37, 3 September 2024

Yocto Project Weekly Status Sept. 3rd, 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:

  • YP 5.1 M3 is in QA
  • We are now at feature freeze and working on bug fixing for the final 5.1 release builds
  • Some limited recipe upgrades may be taken in M4 depending on their value of bug fixes vs breaking changes/features.
  • Fixes to make ERROR_QA only rebuild tasks it directly affects were merged, which will improve sstate reuse from the project servers significantly.
  • 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 in QA.
  • 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 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=86437"