Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(453 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Apr. 13, 2021 ==
== Yocto Project Status 21 July 2026 ==
Current Dev Position: YP 3.4 M1<br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: 7th June 2021 YP 3.4 M1 build<br/>
Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Apr. 22nd at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 23rd July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday May 4th at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 21st July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Apr. 20th at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 23rd July 10am GMT and Monday 27th July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Twitch -  See https://www.twitch.tv/theyoctojester
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.3 has been released. Thanks go to everyone who contributed to it!
*YP 6.0.2 has been released
*YP 3.1.7 has come cleanly through QA and is pending TSC approval for release.
*YP 5.0.19 is due to release
*The YP TSC has now served for two years, thanks go to the outgoing TSC (Armin, Denys, Khem, Richard, Ross) who have been instrumental in a number of significant project developments over that time such as the LTS, definition of processes and resourcing the project. Some of the work isn’t immediately obvious but has shaped the project and should ensure a stable and positive future direction.
*YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
*New TSC members are now being chosen for the next two years. Three of the TSC seats have now been (re-)elected by the YP members and those seats are being filled by Richard (chair), Khem and Ross. Two are elected by the OE community and there will be a call for candidates coming soon from the OE board to the OE membership.
*Some invasive LICENSE changes have merged into master:
*The master branch has opened for 3.4 development and a number of patches queued during release of 3.3 have now merged.
**We now require the LICENSE field to match SPDX identifiers.
*There may be interest in a new command, “bitbake-getvar” being proposed on the bitbake mailing list and in master-next. This makes it easier to see the history of a single variable and also makes a neat example of using the tinfoil API. We are also considering other similar helper commands (maybe along the lines of the ‘bb’ tool) with a view to making things easier for new users.
**The build will issue warnings when this isn’t the case.
*Intermittent autobuilder issues continue to occur and are now at a record high level. 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 are working to identify the load pattern on the infrastructure that seems to trigger these.
**Non SPDX licenses will need to be of the form LicenseRef-XXX
**CLOSED is no longer a valid value.  
**‘WITH’ license exceptions are now supported
Big thanks for Joshua for getting us to the point where we can finally clean this up!
*We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
*A couple of further pseudo related issues were identified, one with linkat flags and one with openat2 (tar related/triggered). We hope to have patches merged soon.
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. The review calls are running out of time each meeting which limits progress.
**We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
**several qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are bugs that are currently unassigned for YP 3.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enhancements.2FBugs
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*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.
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
 
'''New to the project?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''YP 3.3 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.3 is released.
*WDD 2719 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1019 (last week 1019+)
**Patches in the Pending State: 144 (14%) [last week 145 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 3.4 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 3.4 M1 build date 2021/06/07
*6.1 M2:
*YP 3.4 M1 Release date 2021/06/18
**Build Date: w/c 2026-07-20
*YP 3.4 M2 build date 2021/07/12
**Release Date: w/c 2026-08-03
*YP 3.4 M2 Release date 2021/07/23
*6.1 M3:
*YP 3.4 M3 build date 2021/08/23
**Build Date: w/c 2026-08-31
*YP 3.4 M3 Release date 2021/09/03
**Release Date: w/c 2026-09-14
*YP 3.4 M4 build date 2021/10/04
*6.1.0:
*YP 3.4 M4 Release date 2021/10/29
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02


'''Planned upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.7 is out of QA.
*YP 5.0.19 due to release
*YP 3.1.7 release date 2021/04/09
**Release Date w/c 2026-07-13
*YP 3.2.4 build date 2021/05/3
*YP 6.0.3
*YP 3.2.4 release date 2021/05/14
**Build Date w/c 2026-08-10
*YP 3.1.8 build date 2021/05/17
**Release Date w/c 2026-08-24
*YP 3.1.8 release date 2021/05/28
*YP 5.0.20
*YP 3.3.1 build date 2021/05/24
**Build Date w/c 2026-08-17
*YP 3.3.1 release date 2021/06/04
**Release Date w/c 2026-08-31
*YP 3.1.9 build date 2021/06/21
*YP 3.1.9 release date 2021/07/02
*YP 3.1.10 build date 2021/07/26
*YP 3.1.10 release date 2021/08/06
*YP 3.3.2 build date 2021/08/09
*YP 3.3.2 release date 2021/08/20
*YP 3.1.11 build date 2021/09/13
*YP 3.1.11 release date 2021/9/24


'''Tracking Metrics:'''<br/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*WDD 2745 (last week 2737) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics 
**Total patches found: 1287 (last week 1318)
**Patches in the Pending State: 493 (38%) [last week 493 (37%)]


'''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 64: Line 77:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 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:50, 21 July 2026

Yocto Project Status 21 July 2026

Current Dev Position: YP 6.1 M2
Next Deadline: YP 6.1 M2: w/c 2026-07-20

Next Team Meetings:

Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

  • YP 6.0.2 has been released
  • YP 5.0.19 is due to release
  • YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
  • Some invasive LICENSE changes have merged into master:
    • We now require the LICENSE field to match SPDX identifiers.
    • The build will issue warnings when this isn’t the case.
    • Non SPDX licenses will need to be of the form LicenseRef-XXX
    • CLOSED is no longer a valid value.
    • ‘WITH’ license exceptions are now supported

Big thanks for Joshua for getting us to the point where we can finally clean this up!

  • We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
  • Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
  • A couple of further pseudo related issues were identified, one with linkat flags and one with openat2 (tar related/triggered). We hope to have patches merged soon.
  • Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. The review calls are running out of time each meeting which limits progress.
    • We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
    • several qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • siggen reset issues (“ResourceWarning: unclosed transport”)
    • groff build race issues
    • intermittent ptest failures in many recipes
  • For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M2:
    • Build Date: w/c 2026-07-20
    • Release Date: w/c 2026-08-03
  • 6.1 M3:
    • Build Date: w/c 2026-08-31
    • Release Date: w/c 2026-09-14
  • 6.1.0:
    • Build Date (M4): w/c 2026-10-12
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 5.0.19 due to release
    • Release Date w/c 2026-07-13
  • YP 6.0.3
    • Build Date w/c 2026-08-10
    • Release Date w/c 2026-08-24
  • YP 5.0.20
    • Build Date w/c 2026-08-17
    • Release Date w/c 2026-08-31

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=86852"