Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(363 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Feb. 23rd, 2022 ==
== Yocto Project Status 8 September 2026 ==
Current Dev Position: YP 3.5 M4<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: 4th Apr. 2022 YP 3.5 M4 build<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Feb. 25th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 10th Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Mar. 1st at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 8st Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Feb. 23rd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 10th Sept. 10am GMT and Monday 14th Sept. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Twitch -  See https://www.twitch.tv/theyoctojester
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*Next week is feature freeze for 3.5, our next LTS release
* YP 5.0.20 is under review.
*YP 3.1.14 passed QA and is due to be released
* YP 6.1 M3 is due to build and we are at feature freeze
*YP 3.2.4 rc2 is in QA (rc1 had sstate networking issues)
* There are issues with changes in bot/AI protection at github.com which are affecting our CI.  
*We’re extremely worried about the inclusive language changes since these are not anywhere near ready and the freeze deadline is in days. This is an important topic but sadly we’re simply starved of people with the right time and skills to spend on it. There is an email on the openembedded-architecture list about this.
* Most M3 changes have merged, we want to mitigate the github issues before building M3.
*The autobuilder infrastructure is planned to be offline 26-28th February for a data center move. Public services like the website, wiki and git servers will remain live but the git backend (push.yoctoproject.org) will be offline, as will the downloads and sstate services and the autobuilder/NAS.
* There is a new meta-openjdk layer: https://github.com/amarula/meta-openjdk https://lore.kernel.org/yocto-patches/xBB4.1788187111192557019.ULaN@lists.yoctoproject.org/T/#u
*We’ve upgraded to the new glibc version and have patches in testing for the new binutils release assuming some minor issues there are resolved.
* 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.
*There are changes proposed to the bitbake git fetcher handling of tags. We resolve these against the upstream repositories and the caching of the values was showing issues such as network accesses in the unpack task. We advice against using tags due to the potential for them to change, any layers using them may seen error messages depending on whether their usage is problematic.
* 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:
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT In particular, we’re struggling to understand the intermittent network issue with external hosts we’re seeing very occasionally.
** 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
*Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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=---
*There are bugs that are currently unassigned for YP 3.5. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhancements.2FBugs
*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/
*We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
*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.
*Help us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing


'''YP 3.5 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 3.5 M3 build date 2022/02/21
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 3.5 M3 Release date 2022/03/04
 
*YP 3.5 M4 build date 2022/04/04
'''Tracking Metrics:'''<br/>
*YP 3.5 M4 Release date 2022/04/29
*WDD 2622 (last week 2612) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1050 (last week 1039)
**Patches in the Pending State: 136 (13%) [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/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.14 is released
*YP 6.0.3 is in review.
*YP 3.4.2 is released
**Release Date w/c 2026-08-24
*YP 3.3.5 is in QA
*YP 5.0.20 is in QA.
*YP 3.3.5 Release date 2022/02/25
**Release Date w/c 2026-08-31
*YP 3.1.15 build date 2022/03/14
*YP 6.0.4
*YP 3.1.15 Release date 2022/03/25
**Build Date w/c 2026-09-28
*YP 3.4.3 build date 2022/03/21
**Release Date w/c 2026-10-12
*YP 3.4.3 Release date 2022/04/01
*YP 5.0.21
*YP 3.3.6 build date 2022/03/28
**Build Date w/c 2026-10-05
*YP 3.3.6 Release date 2022/04/08
**Release Date w/c 2026-10-19
*YP 3.1.16 build date 2022/04/25
*YP 3.1.16 Release date 2022/05/06


'''Tracking Metrics:'''<br/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*WDD 2652 (last week 2662) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
**Total patches found: 1202 (last week 1208)
**Patches in the Pending State: 334 (28%) [last week 334 (28%)]


'''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 55: Line 69:


== 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]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]

Latest revision as of 14:41, 8 September 2026

Yocto Project Status 8 September 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:

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
  • Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!

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 review.
    • Release Date w/c 2026-08-24
  • YP 5.0.20 is in QA.
    • 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=86874"