Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(856 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== Yocto Project Status 24 March 2026 ==
Current Dev Position: YP 6.0 M3<br/>
Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>


== Yocto Project Weekly Status Jan. 22, 2018 ==
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 26th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Mar. 10am GMT and Monday 30th Mar. 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 6.0 M2 has been released.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
*YP 4.0.34 is due to be released.
*YP 5.3.3 is in review after QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are many key changes needed still missing.  
**Issues still pending:
**Splitting wic into an external tool.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*Issues that are mostly known quantities still needing work:
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
**Fixing yocto-check-layer to work with –machines
*Issues that were resolved this week:
**Switching to pkg-config.
**Allowing non-destructive git fetcher updates for bitbake-setup (further tweaks still being discussed)
*We are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due to xattrs)
*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.


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 2841 (last week 2866) (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: 1069 (last week 1081)
YP 2.5 M3 release of 3/2/18
**Patches in the Pending State: 152 (14%) [last week 151 (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:
'''YP 6.0 Milestone Dates:'''<br/>
WDD 2657 (last week 2672)
*YP 6.0 M2 was released.
(https://wiki.yoctoproject.org/charts/combo.html)
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04


Key Status Links for YP:
'''Upcoming dot releases:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
*YP 4.0.34 ready for release.
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
*YP 5.3.3 is in review.
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05


[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>


== Yocto Project Status Jan. 16, 2018 ==
== Archives ==
 
*[[2026 Yocto Project Weekly Status Archive]]
Current Dev Position: YP 2.5 M2 development
*[[2025 Yocto Project Weekly Status Archive]]
Next Deadline: YP 2.5 M2 cut off was 1/15/18
*[[2024 Yocto Project Weekly Status Archive]]
 
*[[2023 Yocto Project Weekly Status Archive]]
SWAT team rotation: Joshua -> Armin on Jan. 12, 2018.
*[[2022 Yocto Project Weekly Status Archive]]
SWAT team rotation: Armin -> Ross on Jan. 19, 2018.
*[[2021 Yocto Project Weekly Status Archive]]
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
*[[2020 Yocto Project Weekly Status Archive]]
 
*[[2019 Yocto Project Weekly Status Archive]]
Key Status/Updates:
*[[2018 Yocto Project Weekly Status Archive]]
• 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!]
 
== Yocto Project Weekly Status Jan. 8, 2018 ==
 
Current Dev Position: YP 2.5 M2 development
Next Deadline: YP 2.5 M2 cut off of 1/15/18
 
SWAT team rotation: Cal -> Joshua on Jan. 5, 2018.
SWAT team rotation: Joshua -> Armin on Jan. 12, 2018.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
 
Key Status/Updates:
• 2.3.3 and 2.4.1 are likely due to imminently release, we tracked down the performance regressions to some kind of infrastructure issue which is still being investigated.
• The automated testing issues have mostly been resolved now and this has meant we’ve run a series of builds for master and the stable release branches. As such, the backlog of patches against morty, pyro, rocko and master are substantially reduced after this weekend.
• Armin’s help with the stable patch queues is much appreciated.
• Due to testing problems with 2.5 M1 rc1, particular from the qemu APIC hangs, we have put a new build, rc3 into QA. The QA of YP 2.5 M1 rc3 is about 2% complete.  See: https://wiki.yoctoproject.org/wiki/2.5_QA_Status
• We’re aware there are some serious security issues around at the moment. We’ve been stalled partly as maintainers are returning from vacation, partly as fixes are only now becoming available. As fixes are available we will waterfall these into the branches. One of the reasons we’ve focused on clearing the other patches queued is so we can quickly test and merge these and then proceed with another set of point releases.
 
Planned upcoming dot releases:
YP 2.4.1 (Rocko) rc1 is out of QA, and should be released this week.
YP 2.3.3 (Pyro) rc1 is out of QA, and should be released this week.
YP 2.2.3 (Morty) rc1 is in QA, see https://wiki.yoctoproject.org/wiki/2.2_QA_Status.
 
Key YP 2.5 Dates are:
YP 2.5 M1 rc1 is in QA, see above link.
YP 2.5 M2 cut off of 1/15/18
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 2700 (last week 2764)
(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!]
 
== Yocto Project Weekly Status Jan. 2, 2018 ==
 
Current Dev Position: YP 2.5 M2 development
Next Deadline: YP 2.5 M2 cut off of 1/15/18
 
SWAT team rotation: Maxin -> Rebecca on Dec. 22, 2017.
SWAT team rotation: Rebecca -> Cal on Dec. 29, 2017.
SWAT team rotation: Cal -> Joshua on Jan. 5, 2018.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
 
Key Status/Updates:
• Things have been slow over the holiday season but things should be back to normal by the end of this week.
• The QA of YP 2.4.1 rc1 is complete.  See: https://wiki.yoctoproject.org/wiki/WW51_-_2017-12-21-_Full_Test_Cycle_-_2.4.1_rc1.
• The QA of YP 2.3.3 rc1 is complete. See: https://wiki.yoctoproject.org/wiki/WW51_-_2017-12-20-_Full_Test_Cycle_-_2.3.3_rc1.
• For 2.3.3 and 2.4.1 we have some questions about performance issues which the QA process potentially identified and we need to investigate these before any release can be made.
• The QA of YP 2.5 M1 rc1 is about 68% complete.  See: https://wiki.yoctoproject.org/wiki/2.5_QA_Status
• The QA of YP 2.2.3 rc1 is about 24% complete. See: https://wiki.yoctoproject.org/wiki/2.2_QA_Status.
• The kvm apic hang is resolved for qemux86-64 with a workaround. The workaround doesn’t work for qemux86 but there is another patch pending to address this.
• We keep seeing phantom “inode space” issues with the NFS setup on the autobuilder across all releases. I think we’re likely to give in and change the disk space monitoring on the infrastructure to ignore this as its breaking too many builds and likely not worth tracking down further.
• There are other suspected repository concurrency issues on the infrastructure causing failures and we’ve disabled buildhistory to allow builds to work until that is resolved.
• We’re hopeful with these changes in place we can get some kind of build stability back and have a better chance at merging patches again.
 
Planned upcoming dot releases:
YP 2.4.1 (Rocko) rc1 is out of QA, see above link. 
YP 2.3.3 (Pyro) rc1 is out of QA, see above link.
YP 2.2.3 (Morty) rc1 is in QA, see above link.
 
Key YP 2.5 Dates are:
YP 2.5 M1 rc1 is in QA, see above link.
YP 2.5 M2 cut off of 1/15/18
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 2764 (last week 2719)
(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:43, 24 March 2026

Yocto Project Status 24 March 2026

Current Dev Position: YP 6.0 M3
Next Deadline: YP 6.0 M3 Build Date 2026-03-23

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.0 M2 has been released.
  • YP 4.0.34 is due to be released.
  • YP 5.3.3 is in review after QA.
  • YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
  • YP 6.0 M3 is now due to build however there are many key changes needed still missing.
    • Issues still pending:
    • Splitting wic into an external tool.
    • Deprecation of ltp (upstream dropped runltp and mandate kirk)
    • How to improve DEBUG_BUILD?
    • DISTRO_FEATURES defaults improvements.
    • SBOM/cve-check changes.
    • AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
  • Issues that are mostly known quantities still needing work:
    • x86 kvm seemingly broken with certain CPU features (#16074)
    • Failure to generate regression reports in release builds
    • Reconcile poky and OE-Core defaults templates.
    • Resolve Fedora 43 selftest failures
    • Fixing yocto-check-layer to work with –machines
  • Issues that were resolved this week:
    • Switching to pkg-config.
    • Allowing non-destructive git fetcher updates for bitbake-setup (further tweaks still being discussed)
  • We are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due to xattrs)
  • 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.

Ways to contribute:

New to the project?

Tracking Metrics:

YP 6.0 Milestone Dates:

  • YP 6.0 M2 was released.
  • YP 6.0 M3 Build Date 2026-03-23
  • YP 6.0 M3 Release Date 2026-04-08
  • YP 6.0 M4 Build Date 2026-04-13
  • YP 6.0 M4 Release Date 2026-05-04

Upcoming dot releases:

  • YP 4.0.34 ready for release.
  • YP 5.3.3 is in review.
  • YP 5.0.17 Build Date 2026-03-30
  • YP 5.0.17 Release Date 2026-04-15
  • YP 4.0.35 Build Date 2026-04-06
  • YP 4.0.35 Release Date 2026-04-22
  • YP 5.3.4 Build Date 2026-04-20
  • YP 5.3.4 Release Date 2026-05-06
  • YP 5.0.18 Build Date 2026-04-27
  • YP 5.0.18 Release Date 2026-05-13
  • YP 5.0.19 Build Date 2026-05-26
  • YP 5.0.19 Release Date 2026-06-05

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