Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(562 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 21, 2020 ==
== Yocto Project Status 21 April 2026 ==
Current Dev Position: YP 3.1 Review for release <br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: YP 3.1 release date 2020/4/24<br/>
Next Deadline: YP 6.0 M4 Build Date 2026-04-20<br/>


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1 will be released imminently
*YP 5.0.17 was released
*We’re pleased to be able to announce that the stable maintainer for the 3.1 LTS release will be Steve Sakoman
*YP 6.0 M3 was released
*YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
*YP 4.0.35 is in QA
*The 3.2 planning document where we’ve been discussing potential 3.2 developments is available at: https://docs.google.com/document/d/100bTV-etO0joh6rAkcr7smlZ9iuENG_8BtaXs_vb54c/edit?usp=sharing
*YP 6.0 M4 is due to build
*Master branch development will open up later this week, there are already some patches queued and tested in master-next
*We continue to triage the CVEs being reported by the new tooling.
*There is discussion on the openembedded-architecture list about a particularly troublesome multilib issue which doesn’t appear to have any good resolution at present.
*Various fixes have merged or are planned to merge before the M4 release build:
*We are aware of some issues with bug trend metrics this week due to server transitions and are working to resolve those.
**Various CVE issue resolutions from CVE triage
**Reproducibility issues with strace/apr-util
**Make race in groff
**Shadow-native tallylog issue fix
**Upgrade of barebox to align with an LTS release
**Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
**Sbom-cve-check upgrade (along with dependencies)
*Issues still pending:
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
**Intermittent wic failures on the autobuilder
*At this point we will likely run the release build as the remaining issues aren’t critical to end users and we have no clear timeframe for resolution of them
git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The final whinlatter build is happening this week.


'''YP 3.1 Dates'''<br/>
'''Ways to contribute:'''<br/>
*YP 3.1 M4 In review for release
*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=---
*YP 3.1 M4 Release date 2020/4/24
*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/
*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


'''YP 3.2 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 3.2 M1 build date 2020/6/16
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 3.2 M1 Release date 2020/6/26
*YP 3.2 M2 build date 2020/7/27
*YP 3.2 M2 Release date 2020/8/7
*YP 3.2 M3 build date 2020/8/31
*YP 3.2 M3 Release date 2020/9/11
*YP 3.2 M4 build date 2020/10/5
*YP 3.2 M4 Release date 2020/10/30


'''Planned upcoming dot releases:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.0.3 build date 2020/5/4
*WDD 2790 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.0.3 release date 2020/5/15
*OE-Core/Poky Patch Metrics
*YP 2.7.4 build date 2020/5/18
**Total patches found: 1078 (last week 1072)
*YP 2.7.4 release date 2020/5/29
**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
*YP 3.1.1 build date 2020/6/29
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
*YP 3.1.1 release date 2020/7/10
*YP 3.0.4 build date 2020/8/10
*YP 3.0.4 release date 2020/8/21
*YP 3.1.2 build date 2020/9/14
*YP 3.1.2 release date 2020/9/25


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2577 (last week 2577) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.17 was released.
*Poky Patch Metrics  
*YP 4.0.35 is in QA.
**Total patches found: 1364 (last week 1364)
*YP 5.3.4
**Patches in the Pending State: 538 (39%) [last week 538 (39%)]
**Build Date 2026-04-20
**Release Date 2026-05-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


'''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 54: Line 61:


== 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]]
*[[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:47, 21 April 2026

Yocto Project Status 21 April 2026

Current Dev Position: YP 6.0 M4
Next Deadline: YP 6.0 M4 Build Date 2026-04-20

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.17 was released
  • YP 6.0 M3 was released
  • YP 4.0.35 is in QA
  • YP 6.0 M4 is due to build
  • We continue to triage the CVEs being reported by the new tooling.
  • Various fixes have merged or are planned to merge before the M4 release build:
    • Various CVE issue resolutions from CVE triage
    • Reproducibility issues with strace/apr-util
    • Make race in groff
    • Shadow-native tallylog issue fix
    • Upgrade of barebox to align with an LTS release
    • Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
    • Sbom-cve-check upgrade (along with dependencies)
  • Issues still pending:
    • 32bit x86 kvm seemingly broken with certain CPU features (#16074)
    • Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
    • Intermittent wic failures on the autobuilder
  • At this point we will likely run the release build as the remaining issues aren’t critical to end users and we have no clear timeframe for resolution of them

git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.

  • We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
  • The final whinlatter build is happening this week.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming dot releases:

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