Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(870 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== Yocto Project Status 14 July 2026 ==
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>


== Yocto Project Weekly Status Feb. 5, 2018 ==
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 16th July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync  - Tuesday 14th July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 16th July 10am GMT and Monday 20th July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


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


SWAT team rotation: Juro -> Paul on Feb. 2, 2018.
'''Key Status/Updates:'''<br/>
SWAT team rotation: Paul -> Tracy on Feb. 9, 2018.
*YP 6.0.2 is due to release
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
*YP 5.0.19 is in review
*M2 is next week!
*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
*We are happy to report we worked with Free BSD upstream and have resolved the NFS open/lock issue with a kernel patch that was impacting the autobuilder.
*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 have become aware we should ideally replace eudev with a minimal udev build from systemd instead similar to what some other distros are doing.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*The layer.conf changes are likely to be deferred to 6.2 due to lack of time to gather community consensus before feature freeze.
*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
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto


Key Status/Updates:
'''Ways to contribute:'''<br/>
YP 2.5 M2 has been built and is pending QA. The M2 milestone contains the linux-yocto kernel backports and gcc upgrade for the spectre and meltdown security issues.
*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 2.2.3 is mostly through QA, some issues have been identified with newer host distro releases; however, these are likely something we’d address with 2.2.4.
*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/
autobuilder.yoctoproject.org continues to be unavailable as we continue to develop the new autobuilder codebase to replace the current heavily customized buildbot one.
*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.
There are some changes to runqueue in bitbake about to land (currently in -next) which bring some risk of dependency problems in recrdeptask and recideptask handling, it's worth keeping in mind if task dependencies issues appear shortly after those merge.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing


Planned upcoming dot releases:
'''New to the project?'''<br/>
YP 2.4.2 (Rocko) will be built shortly, once there is QA bandwidth available.
*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) rc2 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 is in QA.
*WDD 2689 (last week 2689) (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: 1019 (last week 1037)
YP 2.5 M3 release of 3/2/18
**Patches in the Pending State: 145 (14%) [last week 145 (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 development releases:'''<br/>
WDD 2638 (last week 2630)
*6.1 M2:
(https://wiki.yoctoproject.org/charts/combo.html)
**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


Key Status Links for YP:
'''Upcoming dot releases:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
*YP 6.0.2 is due to release
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
**Release Date w/c 2026-07-06
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features
*YP 5.0.19 is in review
**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 Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


[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 Weekly Status Jan. 29, 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: Ross -> Juro on Jan. 26, 2018.
*[[2022 Yocto Project Weekly Status Archive]]
SWAT team rotation: Juro -> Tracy on Feb. 2, 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]]
YP 2.5 M1 rc3 was released.
Fixes for spectre and meltdown are in master and also in the rocko branches for both gcc (updated to 7.3) and linux-yocto.
We will likely consolidate a few further patches (such as genericx86 and other meta-yotcto-bsp updates) and then build and QA both 2.5 M2 and 2.4.2.
Work on the autobuilder changes continues but means autobuilder.yoctoproject.org is not being used in production (autobuilder.yocto.io aka ‘the new cluster’) is.
There were a number of lock related issues with the yocto.io builder over the weekend which are being investigated.
 
Planned upcoming dot releases:
YP 2.4.2 (Rocko) will be built shortly.
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:
YP 2.5 M2 cut off is past, it should be built shortly.
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 2630 (last week 2657)
(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. 22, 2018 ==
 
Current Dev Position: YP 2.5 M2 development
Next Deadline: YP 2.5 M2 cut off was 1/15/18
 
SWAT team rotation: Armin -> Ross on Jan. 19, 2018.
SWAT team rotation: Ross -> Juro on Jan. 26, 2018.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
 
Key Status/Updates:
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
With a round of security released fixes likely to land shortly, we’ll likely wait for these before we roll M2.
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.
The AUH emails have triggered a good batch of recipe upgrades. QEMU was also upgraded (which can often cause problems).
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:
YP 2.4.2 (Rocko) will be built when a stable version of the spectre/meltdown patches are ready.
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:
YP 2.5 M2 cut off is past, it should be built as soon as a decision on the spectre/meltdown patches is made.
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 2657 (last week 2672)
(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. 16, 2018 ==
 
Current Dev Position: YP 2.5 M2 development
Next Deadline: YP 2.5 M2 cut off was 1/15/18
 
SWAT team rotation: Joshua -> Armin on Jan. 12, 2018.
SWAT team rotation: Armin -> Ross on Jan. 19, 2018.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
 
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!]
 
== 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:44, 14 July 2026

Yocto Project Status 14 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 is due to release
  • YP 5.0.19 is in review
  • M2 is next week!
  • 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
  • We are happy to report we worked with Free BSD upstream and have resolved the NFS open/lock issue with a kernel patch that was impacting the autobuilder.
  • 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 have become aware we should ideally replace eudev with a minimal udev build from systemd instead similar to what some other distros are doing.
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
  • The layer.conf changes are likely to be deferred to 6.2 due to lack of time to gather community consensus before feature freeze.
  • 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
  • We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto

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 6.0.2 is due to release
    • Release Date w/c 2026-07-06
  • YP 5.0.19 is in review
    • 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=86850"