Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(437 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Aug. 4, 2020 ==
== Yocto Project Weekly Status Oct. 1st, 2024 ==
Current Dev Position: YP 3.2 M3<br/>
Current Dev Position: YP 5.1 release built and awaiting release notes<br/>
Next Deadline: YP 3.2 M3 build date 2020/8/31<br/>
Next Deadline: YP 5.1 M4 Release date 2024-10-25<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Aug 6th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday Oct. 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Aug 4th at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Project Engineering Sync Tuesday Oct. 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Aug 11th 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/>
*3.1.2 was released
*YP 5.1 rc1 (final release) is in QA, the final work item is updating the documentation. Help to write and review release notes and migration guides is greatly appreciated.
*3.2 M2 is currently under QA
*YP 5.0.4 is out of QA and under review for release.
*We continue to see qemumips systemd (poky-altcfg) image testing failures for unknown  reasons although it does seem linked to the poor performance of mips emulation under qemu.  
*master and styhead have now diverged, so be aware of this if you’re tracking git branches.
*The project has published a plan related to use of inclusive language within the project (covering Yocto Project and OpenEmbedded). This was posted to the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/inclusive_language_summary/75821819
*The new release series name is available in OE-Core master, ‘walnascar’ aka ‘walna’ verbally. Users are encouraged to update their master/devel branches to this.
*Documentation covering the potential “future directions” for Yocto Project has been published: https://lists.openembedded.org/g/openembedded-architecture/topic/yocto_project_future/75845140
*Early testing shows problems in Fedora 41 related to pseudo. Help in debugging and root causing appreciated.
*You can see the rest of 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.
*The Ubuntu 24.04 with NFS issue has been resolved, but unless we respin the release build will not be fixed in 5.1.0. A fix is already integrated into bitbake and will be in the first point release.
*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
*Migration to the new autobuilder is proceeding with regular users now encouraged to trigger builds on the new cluster to stress test and identify any issues.
*Help with any of the recent failed AUH recipe upgrades would also be appreciated.
*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.
*There is discussion around configuration file markup/syntax related to fragment management on the architecture list, targeting 5.2.
*For 5.2 it would be helpful to have rough development plans for areas of the project if anyone is able to help document a rough roadmap/plan for them. The following areas are known to be being or need working on:
**Autobuilder
**Binary Distro
**Bitbake config fragments
**Bitbake setup process/tooling
**GUI screen shot QA test
**IDE Plugin development
**Layer Index
**Patchtest
**Security Tooling
**Swatbot
**Toaster
*If there are other areas we should have plans for, please let us know.


'''YP 3.2 Milestone Dates:'''<br/>
'''Ways to contribute:'''<br/>
*YP 3.2 M2 build is in QA
*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!
*YP 3.2 M2 Release date 2020/8/7
*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
*YP 3.2 M3 build date 2020/8/31
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*YP 3.2 M3 Release date 2020/9/11
*There are bugs that are currently unassigned for YP 5.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_Unassigned_Enhancements/Bugs
*YP 3.2 M4 build date 2020/10/5
*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.
*YP 3.2 M4 Release date 2020/10/30
*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.


'''Planned upcoming dot releases:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.0.4 build date 2020/8/10
*WDD 2704 (last week 2749) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.0.4 release date 2020/8/21
*OE-Core/Poky Patch Metrics
*YP 3.1.2 is released
**Total patches found: 1067 (last week 1067)
*YP 3.1.3 build date 2020/9/14
**Patches in the Pending State: 176 (16%) [last week 176 (16%)]
*YP 3.1.3 release date 2020/9/25
*https://autobuilder.yocto.io/-release/patchmetrics/


'''Tracking Metrics:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*WDD 2402 (last week 2415) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.1 M4 Release date 2024-10-25
*Poky Patch Metrics 
 
**Total patches found: 1271 (last week 1281)
'''Upcoming dot releases:'''<br/>
**Patches in the Pending State: 495 (39%) [last week 498 (39%)]
*YP 5.0.4 is ready for release.
*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 44: Line 65:


== 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:43, 1 October 2024

Yocto Project Weekly Status Oct. 1st, 2024

Current Dev Position: YP 5.1 release built and awaiting release notes
Next Deadline: YP 5.1 M4 Release date 2024-10-25

Next Team Meetings:

Key Status/Updates:

  • YP 5.1 rc1 (final release) is in QA, the final work item is updating the documentation. Help to write and review release notes and migration guides is greatly appreciated.
  • YP 5.0.4 is out of QA and under review for release.
  • master and styhead have now diverged, so be aware of this if you’re tracking git branches.
  • The new release series name is available in OE-Core master, ‘walnascar’ aka ‘walna’ verbally. Users are encouraged to update their master/devel branches to this.
  • Early testing shows problems in Fedora 41 related to pseudo. Help in debugging and root causing appreciated.
  • The Ubuntu 24.04 with NFS issue has been resolved, but unless we respin the release build will not be fixed in 5.1.0. A fix is already integrated into bitbake and will be in the first point release.
  • Migration to the new autobuilder is proceeding with regular users now encouraged to trigger builds on the new cluster to stress test and identify any issues.
  • 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.
  • There is discussion around configuration file markup/syntax related to fragment management on the architecture list, targeting 5.2.
  • For 5.2 it would be helpful to have rough development plans for areas of the project if anyone is able to help document a rough roadmap/plan for them. The following areas are known to be being or need working on:
    • Autobuilder
    • Binary Distro
    • Bitbake config fragments
    • Bitbake setup process/tooling
    • GUI screen shot QA test
    • IDE Plugin development
    • Layer Index
    • Patchtest
    • Security Tooling
    • Swatbot
    • Toaster
  • If there are other areas we should have plans for, please let us know.

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.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_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 M4 Release date 2024-10-25

Upcoming dot releases:

  • YP 5.0.4 is ready for release.
  • 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