Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(Created page with "Subject: Yocto Project Status WW04’18 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...")
 
 
(888 intermediate revisions by 7 users not shown)
Line 1: Line 1:
Subject: Yocto Project Status WW04’18
== Yocto Project Status 25 August 2026 ==
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


Current Dev Position: YP 2.5 M2 development
'''Next Team Meetings:'''<br/>
Next Deadline: YP 2.5 M2 cut off was 1/15/18
*Bug Triage meeting - Thursday 27th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync  - Tuesday 25th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 27th Aug. 10am GMT and Monday 31st Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


SWAT team rotation: Armin -> Ross on Jan. 19, 2018.
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
SWAT team rotation: Ross -> Juro on Jan. 26, 2018.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Key Status/Updates:
'''Key Status/Updates:'''<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
*YP 6.0.3 is in QA.
With a round of security released fixes likely to land shortly, we’ll likely wait for these before we roll M2.
*YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
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.
*For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
The AUH emails have triggered a good batch of recipe upgrades. QEMU was also upgraded (which can often cause problems).
*AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
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
*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
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 are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
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.
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*Remaining intermittent build failures of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**intermittent ptest failures in many recipes


Planned upcoming dot releases:
'''Ways to contribute:'''<br/>
YP 2.4.2 (Rocko) will be built when a stable version of the spectre/meltdown patches are ready.
*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.3.4 (Pyro) will be built when a stable version of the spectre/meltdown patches are ready.
*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/
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.
*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


Key YP 2.5 Dates are:
'''New to the project?'''<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.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
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:
'''Tracking Metrics:'''<br/>
WDD 2657 (last week 2672)
*WDD 2659 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
(https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1028 (last week 1030)
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


Key Status Links for YP:
'''Upcoming development releases:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
*6.1 M3:
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
**Build Date: w/c 2026-08-31
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features
**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


[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
'''Upcoming dot releases:'''<br/>
*YP 6.0.3 is in QA.
**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
*YP 6.0.4
**Build Date w/c 2026-09-28
**Release Date w/c 2026-10-12
*YP 5.0.21
**Build Date w/c 2026-10-05
**Release Date w/c 2026-10-19
 
*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/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
 
== 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]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]

Latest revision as of 14:45, 25 August 2026

Yocto Project Status 25 August 2026

Current Dev Position: YP 6.1 M3
Next Deadline: YP 6.1 M3: w/c 2026-08-31

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.0.3 is in QA.
  • YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
  • For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
  • AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
  • We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
  • There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
    • Matchbox-wm segfault/xserver restart
    • aarch64/x86-64 build host contamination/reproducibility issue

We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.

  • Remaining intermittent build failures of concern:
    • other qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • intermittent ptest failures in many recipes

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 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.3 is in QA.
    • 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
  • YP 6.0.4
    • Build Date w/c 2026-09-28
    • Release Date w/c 2026-10-12
  • YP 5.0.21
    • Build Date w/c 2026-10-05
    • Release Date w/c 2026-10-19

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