Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(86 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status August 29th, 2023 ==
== Yocto Project Weekly Status Sept. 17th, 2024 ==
Current Dev Position: YP 4.3 Feature Freeze<br/>
Current Dev Position: YP 5.1 Feature Freeze and Bug Fixing<br/>
Next Deadline: 28th August 2023 YP 4.3 M3 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 August 31st 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday Sept. 19th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday August 29th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync Tuesday Sept. 17th 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/>
*We are now at feature freeze for 4.3.
*YP 5.1 M3 has been released
*YP 4.0.12 was released
*YP 4.0.21 has been released
*YP 4.2.3 is due to be released
*YP 5.1 rc1 (final release) is being built
*The qemuppc ssh command hangs continues to be a mystery. It seems to be something in recent master that regressed it but it isn’t the kernel, the binutils upgrade, systemd or glibc or qemu. We’ve not seen any other hangs so the x86 issues may have been something else.
*There are YP 5.2 proposed milestone dates https://docs.google.com/document/d/1TDrD9nFjosvLHa7EfL_Y1-1slK7u5Am6NZV6QRF2P6s/edit - please review and let us know if there are any concerns.
*The acl/xattr changes are blocked on a hard requirement on tar 1.35, it is unclear how we’d achieve that in all cases.
*The final pieces of the release were merged:
*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.
**sanity test for Ubuntu 24.04 userns/apparmor issue added
*We continue to see intermittent ptest failures for glib-networking and openssh, help would be much appreciated.
**TCLIBCAPPEND properly deprecated
*The M3 build will depend upon reaching conclusions in several of these areas
**toaster fixtures tweaked
*We’re happy to be able to announce that some of the work in the RFQ will now be progressing, specifically that:
**buildtools updated
**Marta Rybczynska will be working on the security topic
**non-deterministic libsdl2 configure issue fixed
**Alexander Kanvin will be working on the core workflow topic
**gitsm configparser change reverted
**Savoir-faire Linux will be working on the toaster and VSCode topics
**many other varied and useful fixes
**BayLibre will be working on the patchtest and project tooling topics
*Since there is now an rc build heading to QA, master and styhead will diverge. There are some patches in master-next which were deemed too late/risky for the release (including the gomod class changes)
The other remaining topic areas should be announced soon.
*The new autobuilder has had NAS problems when scaled to final size, those are being worked on but it will delay switching to the new system a little.
We’d also note that Tim Orling (Konsulko) will be working on the layer index.
*There is discussion around configuration file markup/syntax related to fragment management on the architecture list, targeting 5.2.


'''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 34: Line 35:
*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 build date  2023/08/28
*WDD 2739 (last week 2734) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.3 M3 Release date 2023/09/08
*OE-Core/Poky Patch Metrics
*YP 4.3 M4 build date 2023/10/02
**Total patches found: 1067 (last week 1067)
*YP 4.3 M4 Release date 2023/10/27
**Patches in the Pending State: 176 (16%) [last week 176 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
 
'''YP 5.1 Milestone Dates:'''<br/>
*YP 5.1 M3 is released.
*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 4.0.12 is released
*YP 4.0.21 is released.
*YP 4.2.3 is ready for release
*YP 5.0.4 Build Date 2024-09-23
*YP 3.1.28 build date 2023/09/18
*YP 5.0.4 Release Date 2024-10-04
*YP 3.1.28 Release date 2023/09/29
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.13 build date 2023/09/25
*YP 4.0.22 Release Date 2024-10-25
*YP 4.0.13 Release date 2023/10/06
*YP 5.0.5 Build Date 2024-11-11
*YP 3.1.29 build date 2023/10/30
*YP 5.0.5 Release Date 2024-11-22
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.14 build date 2023/11/06
*YP 4.0.23 Release Date 2024-11-29
*YP 4.0.14 Release date 2023/11/17
*YP 4.2.4 build date 2023/11/13
*YP 4.2.4 Release date 2023/11/24
*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 2500 (last week 2488) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1188 (last week 1183)
**Patches in the Pending State: 258 (22%) [last week 258 (22%)]
*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 69: Line 62:


== 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]]

Latest revision as of 14:49, 17 September 2024

Yocto Project Weekly Status Sept. 17th, 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 has been released
  • YP 4.0.21 has been released
  • YP 5.1 rc1 (final release) is being built
  • There are YP 5.2 proposed milestone dates https://docs.google.com/document/d/1TDrD9nFjosvLHa7EfL_Y1-1slK7u5Am6NZV6QRF2P6s/edit - please review and let us know if there are any concerns.
  • The final pieces of the release were merged:
    • sanity test for Ubuntu 24.04 userns/apparmor issue added
    • TCLIBCAPPEND properly deprecated
    • toaster fixtures tweaked
    • buildtools updated
    • non-deterministic libsdl2 configure issue fixed
    • gitsm configparser change reverted
    • many other varied and useful fixes
  • Since there is now an rc build heading to QA, master and styhead will diverge. There are some patches in master-next which were deemed too late/risky for the release (including the gomod class changes)
  • The new autobuilder has had NAS problems when scaled to final size, those are being worked on but it will delay switching to the new system a little.
  • There is discussion around configuration file markup/syntax related to fragment management on the architecture list, targeting 5.2.

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 released.
  • 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 released.
  • 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=86449"