Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(862 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== Yocto Project Status 21 April 2026 ==
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: YP 6.0 M4 Build Date 2026-04-20<br/>


== Yocto Project Weekly Status Jan. 22, 2018 ==
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday Apr. 23rd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 21st 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 23rd 10am GMT and Monday Apr. 27th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


Current Dev Position: YP 2.5 M2 development
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
Next Deadline: YP 2.5 M2 cut off was 1/15/18


SWAT team rotation: Armin -> Ross on Jan. 19, 2018.
'''Key Status/Updates:'''<br/>
SWAT team rotation: Ross -> Juro on Jan. 26, 2018.
*YP 5.0.17 was released
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
*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.


Key Status/Updates:
'''Ways to contribute:'''<br/>
YP 2.5 M1 rc3 is out of QA and should be released imminently. There were some minor issues but we’ll address these as part of M2. See: https://wiki.yoctoproject.org/wiki/WW03_-_2018-1-18-_Full_Test_Cycle_-_2.5_M1_rc3 and see: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status#Milestone_1_-_Target_Dec._15.2C_2017
*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=---
With a round of security released fixes likely to land shortly, we’ll likely wait for these before we roll M2.
*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/
The Automatic Upgrade Helper (AUH) ran, now based on devtool functionality and testing against a wider set of architectures and build options. This looks likely to easy recipe maintenance and increase productivity for people and I’d like to thank Alex for his work on this. There is much it could do better but it is continuing to evolve and become easier to use which is great to see.
*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.
The AUH emails have triggered a good batch of recipe upgrades. QEMU was also upgraded (which can often cause problems).
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
I sent out a separate summary of changes which are happening to the Autobuilder, people on the SWAT team need to be especially aware of this http://lists.openembedded.org/pipermail/openembedded-architecture/2018-January/000694.html
The long queued python recipe changes including its manifest have landed. We tested this as far as we could in core and I know there is some fall out in other layers, help and patience to work through the issues is appreciated. Patches pending against the python recipes will need to be rebased and resent.
There have been some significant changes to cmake, ninja and meson and meson is now the default for some recipes. There were some significant gettext cleanups.


Planned upcoming dot releases:
'''New to the project?'''<br/>
YP 2.4.2 (Rocko) will be built when a stable version of the spectre/meltdown patches are ready.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
YP 2.3.4 (Pyro) will be built when a stable version of the spectre/meltdown patches are ready.
YP 2.2.3 (Morty) rc1 is in QA, see https://wiki.yoctoproject.org/wiki/2.2_QA_Status.  This will not contain the spectre/meltdown patches as they’re not ready yet.


Key YP 2.5 Dates are:
'''Tracking Metrics:'''<br/>
YP 2.5 M2 cut off is past, it should be built as soon as a decision on the spectre/meltdown patches is made.
*WDD 2790 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
YP 2.5 M2 release of 1/26/18
*OE-Core/Poky Patch Metrics
YP 2.5 M3 cut off of 2/19/18
**Total patches found: 1078 (last week 1072)
YP 2.5 M3 release of 3/2/18
**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
YP 2.5 M4 cut off of 4/2/18
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
YP 2.5 M4 release of 4/27/18


Tracking Metrics:
'''Upcoming dot releases:'''<br/>
WDD 2657 (last week 2672)
*YP 5.0.17 was released.
(https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.0.35 is in QA.
*YP 5.3.4
**Build Date  2026-04-20
**Release Date 2026-05-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


Key Status Links for YP:
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
https://wiki.yoctoproject.org/wiki/TSC<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features


[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
== Archives ==
 
*[[2026 Yocto Project Weekly Status Archive]]
== Yocto Project Status Jan. 16, 2018 ==
*[[2025 Yocto Project Weekly Status Archive]]
 
*[[2024 Yocto Project Weekly Status Archive]]
Current Dev Position: YP 2.5 M2 development
*[[2023 Yocto Project Weekly Status Archive]]
Next Deadline: YP 2.5 M2 cut off was 1/15/18
*[[2022 Yocto Project Weekly Status Archive]]
 
*[[2021 Yocto Project Weekly Status Archive]]
SWAT team rotation: Joshua -> Armin on Jan. 12, 2018.
*[[2020 Yocto Project Weekly Status Archive]]
SWAT team rotation: Armin -> Ross on Jan. 19, 2018.
*[[2019 Yocto Project Weekly Status Archive]]
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
*[[2018 Yocto Project Weekly Status Archive]]
 
Key Status/Updates:
• 2.3.3 and 2.4.1 were released. These releases do not contain spectre/meltdown patches/fixes as those are still being worked on and haven’t merged yet.
• We are mostly up to date with patch queues although there are some bigger series which are still being tested/reviewed and are still pending
• Due to testing problems with 2.5 M1 rc3, it is still undergoing QA testing and is 90% complete. We are continuing to have some QA transition/infrastructure issues. See: https://wiki.yoctoproject.org/wiki/2.5_QA_Status.
• A separate update on the spectre/meltdown status and the project has been sent out to the oe-core mailing list.
 
Planned upcoming dot releases:
YP 2.4.2 (Rocko) will be built when a stable version of the spectre/meltdown patches has been proven ready.
YP 2.3.4 (Pyro) will be built when a stable version of the spectre/meltdown patches has been proven ready.
YP 2.2.3 (Morty) rc1 is in QA, see https://wiki.yoctoproject.org/wiki/2.2_QA_Status.  We are considering holding this release candidate and building another when a stable version of the spectre/meltdown patches has been proven ready.
 
Key YP 2.5 Dates are:
YP 2.5 M1 rc3 is in QA, see above link.
YP 2.5 M2 cut off is past, it should be built as soon as the spectre/meltdown patches are ready and have been proven ready.
YP 2.5 M2 release of 1/26/18
YP 2.5 M3 cut off of 2/19/18
YP 2.5 M3 release of 3/2/18
YP 2.5 M4 cut off of 4/2/18
YP 2.5 M4 release of 4/27/18
 
Tracking Metrics: WDD 2672 (last week 2700)
(https://wiki.yoctoproject.org/charts/combo.html)
 
Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features
 
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

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"