Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(491 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 28, 2020 ==
== Yocto Project Weekly Status Sept. 17th, 2024 ==
Current Dev Position: YP 3.1 M3 <br/>
Current Dev Position: YP 5.1 Feature Freeze and Bug Fixing<br/>
Next Deadline: YP 3.1 M2 in QA - release 1/31/20<br/>
Next Deadline: YP 5.1 M4 Build 30 Sept. 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Jan. 30th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday Sept. 19th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday  Fab. 4th  at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Project Engineering Sync Tuesday Sept. 17th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Jan. 28th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - See https://www.twitch.tv/theyoctojester
*Twitch - Next event is Tuesday Feb. 11th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Tip of the Week:'''<br/>
'''Key Status/Updates:'''<br/>
*The scripts in ${WORKDIR}/temp/run.XXX for shell tasks can be quickly hacked and used for standalone debugging by replacing the function call at the end with “bash -i” which will then drop you into a shell environment matching the task being debugged (minus the fakeroot context).
*YP 5.1 M3 has been released
*Bonus marks for anyone sending a patch to add the fakeroot context as comments at the start of the scripts.
*YP 4.0.21 has been released
*(anyone with tips they’d like to see here, please send to Stephen or Richard)
*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.


'''Key Status/Updates:'''<br/>
'''Ways to contribute:'''<br/>
*YP 3.1 M2 is in QA but has issues with build reproducibility
*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!
*We’re unlikely to rebuild M2 as master has the same issues and they look like they will take a while to resolve.
*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 now serious problems with the build reproducibility test failures on the autobuilder. We’re not sure why there is a sudden set of problems but they are real issues and causing most builds to fail. The tests will have to be disabled unless they can be resolved quickly. There are fixes merged for the CONFIG_SHELL issue and kbd and patches queued as a potential fix for makeinfo. There are more remaining issues, some have open bugs, others don’t have bugs yet. Help with any of these would be appreciated (or help filing the bugs).
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
*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 have created a “documentation” list and a “licensing” list on the yocto project mailing list infrastructure. We believe these topics would benefit from dedicated discussions, the people involved usually aren’t interested in bulk email as would be found on other lists. The new lists can be found at: https://lists.yoctoproject.org/g/licensing/join and https://lists.yoctoproject.org/g/docs/join
*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.
*There is continued concern about the number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
*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.
*We continue to struggle to get clean ‘full’ builds due to the reproducibility issues in particular.
*Help us resolve CVE issues: CVE metrics
*The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.1 M2 release date 1/31/2020
*WDD 2739 (last week 2734) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.1 M3 build date 2/24/2020
*OE-Core/Poky Patch Metrics
*YP 3.1 M3 release date 3/6/2020
**Total patches found: 1067 (last week 1067)
*YP 3.1 M4 build date  3/30/2020
**Patches in the Pending State: 176 (16%) [last week 176 (16%)]
*YP 3.1 M4 release date  4/24/2020
*https://autobuilder.yocto.io/-release/patchmetrics/


'''Planned upcoming dot releases:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 2.7.3 build date  2/10/2020
*YP 5.1 M3 is released.
*YP 2.7.3 release date 2/21/2020
*YP 5.1 M4 Build date 2024-09-30
*YP 3.0.2 build date 2/3/2020
*YP 5.1 M4 Release date 2024-10-25
*YP 3.0.2 release date 2/14/2020


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2765 (last week 2758) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.0.21 is released.
*Poky Patch Metrics 
*YP 5.0.4 Build Date 2024-09-23
**Total patches found: 1368 (last week 1357)
*YP 5.0.4 Release Date 2024-10-04
**Patches in the Pending State: 545 (40%) [last week 536 (39%)]
*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 47: Line 62:


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

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"