Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(637 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status September 3, 2019 ==
== Yocto Project Status 25 August 2026 ==
Current Dev Position: YP 2.8 M4 Feature Freeze<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 3.0 Final Release 25th Oct<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
*SWAT lead is currently: Paul
*Bug Triage meeting - Thursday 27th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*SWAT team rotation: Paul -> Ross on Sept. 13, 2019
*Weekly Project Engineering Sync  - Tuesday 25th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*SWAT team rotation: Ross -> Amanda on Sept. 20, 2019
*Yocto Project Patch Review - Thursday 27th Aug. 10am GMT and Monday 31st Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*Bug Triage meeting Thursday Sept 12th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Tuesday Oct. 1st at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Sept. 10th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - Next event is Tuesday Sept. 10th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We’re now in feature freeze for 3.0 and working on bug fixing for final release
*YP 6.0.3 is in QA.
*We have not built M3 yet as some work still remains for us to be feature complete and ready for QA. This puts us behind schedule but the plan is to complete the key features we’ve planned rather than adhere strictly to dates. We hope to make up time during M4 by having M3 at high quality and take advantage of our automation.
*YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
*RP is away for the rest of the week which means M3 progress will be limited this week, Ross will queue patches.
*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!
*Key 3.0 changes have now merged:
*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.
**5.2 linux-libc-kernel-headers
*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.
**5.2 kernel recipes by default for all reference BSPs
*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:
**Removal of LSB and poky-lsb and replacement with alt config testing
**Matchbox-wm segfault/xserver restart
**systemd by default for poky-altcfg
**aarch64/x86-64 build host contamination/reproducibility issue
**Patches have significantly reduced the dependency on python2
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.
**Reproducible builds are now being tested for core-image-minimal
*Remaining intermittent build failures of concern:
**Automated toolchain testsuite tests (binutils, gcc, glibc)
**other qemu ‘hang’ type issues on ARM
*Key blocking issues for M3 that have been fixed:
**sometimes yocto-check-layer is showing checksum mismatch issues
**Systemtap issues with 5.2 were debugged and patches sent/merged upstream
**intermittent ptest failures in many recipes
**5.2 dmesg on qemuarm64 fixed
**qemumips hang when using highmem root caused and worked around (for now)
**mdadm ptest timeout worked around
**quilt and libevent ptest regressions from M2 resolved
*Remaining issues blocking M3:
**systemd boot failure on qemumips
**strace ptest timeout
**Hash equivalence performance problems (RP has a simple idea to ~double speed)
**Hash equivalence bugs
**Toolchain testsuite relocation bugs (Nathan working on it)
*Hash Equivalency status:
**Ideas about removing some dependency information from the hashes to allow faster bulk queries aren’t viable so the current codebase approach is correct
**we need to rework the client/server communication to scale to the autobuilder
**there are some bugs in the code the autobuilder continues to expose
**we have cases where its not 100% clear what the correct behaviour should be
**test cases are proving to be problematic to write in a maintainable way
*Documentation - Due to illness Scott is unavailable for the next month or two so doc patches will be handled by Richard or Ross in the short term. We’ll likely limit them to correctness issues and defer any substantial new text. If anyone has availability and skills to work on the manuals please talk to us. We’re aware there is a patch backlog.
*If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+Stephen.


'''Planned Releases for YP 3.0 {2.8}:'''<br/>
'''Ways to contribute:'''<br/>
*M3 Release 6th Sept
*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=---
*M4 Cutoff 30th Sept - this will be YP 3.0.
*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 3.0 {2.8 (M4)} Final Release 25th Oct
*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


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 2.7.2 (Warrior) is planned for after YP 3.0 release.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 2.6.4 (Thud) is planned for after YP 2.7.2  release.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2413 (last week 2413) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2659 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1470 (last week 1474)
**Total patches found: 1028 (last week 1030)
**Patches in the Pending State: 611 (42%) [last week 611 (42%)]
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''Upcoming development releases:'''<br/>
*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:'''<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


'''Key Status Links for YP:'''<br/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features<br/>


'''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 72: Line 68:


== 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]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2019 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"