Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(161 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status March 19th, 2024 ==
== Yocto Project Status 6 October 2026 ==
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Current Dev Position: YP 6.2 M1 - Development<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<br/>
Next Deadline: YP 6.1 M4: w/c 2026-10-12<br/>


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.0 M3 has been through QA. There is one major issue, we will likely release M3 and fix that in M4.
*YP 6.1 is in QA
*YP 4.0.17 is in QA.
*YP 6.0.4 is pending with QA.
*There is a regression on beaglebone testing where X is no longer starting which was found during M3 QA. Fixes are under discussion for this and will be in M4.
*Blacksail and master are now on separate branches and have diverged.
*A key worry now is the documentation for the release, especially given it is an LTS. There are emails on the docs list about this, help is much appreciated.
*Patches for 6.2 have started merging into master
*The opkg lock issue with systemd images continues to be a significant concern for the release. We do now have a way to reproduce the bug and it is due to “opkg configure” being executed in a postinstall script whilst opkg install has the lock.
*There are changes to the pypi class so that PYPI_PACKAGE is the normalised name
*There is a uninative issue showing up with newer distros due to the glibc changes where the pthread library is no longer separate. There are patches in testing to try and mitigate against this.
*python3-pytz moved from core to meta-oe, if you notice anything using it, it is a sign the dependencies may be obsolete
*There are multiple other failures occurring on the autobuilder but no specific pattern has been identified as yet. One test build had 4 different failures, and 2 of them were new never seen before issues. There is also some kind of issue with devtool/recipe tool test isolation in selftest which needs to be tracked down.
*There are issues where we could accept help:
*The previously reported CVE database update issue has been mitigated for now but further improvements to the autobuilder process for generating the metrics may still be needed.
**Matchbox-wm segfault/xserver restart
**aarch64/x86-64 build host contamination/reproducibility issue - thanks for the work and fixes so far on this.
**Remaining github.com references in bitbake-selftest
*Bitbake’s network disabling has recently been enhanced to include landlock support.
*This week is Open Source Summit EU and Yocto Project Developer Day in Prague! Contact Paul or Megan if you are attending and want to meet up with other Yocto Project folks, especially if you’re new to our community.
**Regular meetings on Tuesday and Thursday will be canceled, including the Tech call (Tue 6th), Patch review call (Thu 8th) and Bug triage call (Thu 8th).


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*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 identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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/
*There are bugs that are currently unassigned for YP 5.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
*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.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. 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.
 
*Help us resolve CVE issues: CVE metrics
'''New to the project?'''<br/>
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''YP 5.0 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 5.0 M3 is ready for release.
*WDD 2644 (last week 2643) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0 M4 build date  2024/04/01
*OE-Core/Poky Patch Metrics
*YP 5.0 M4 Release date 2024/04/30
**Total patches found: 1057 (last week 1053)
**Patches in the Pending State: 135 (13%) [last week 135 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/3
 
'''Upcoming development releases:'''<br/>
*6.1.0: in QA
**Release Date: w/c 2026-11-02


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.17 is in QA.
*YP 6.0.4 in QA
*YP 4.3.4 build date 2024/03/25
**Release Date w/c 2026-10-12
*YP 4.3.4 Release date 2024/04/05
*YP 5.0.21
*YP 3.1.33 build date 2024/04/15
**Build Date w/c 2026-10-05
*YP 3.1.33 Release date 2024/04/26
**Release Date w/c 2026-10-19
*YP 4.0.18 build date 2024/04/22
*YP 4.0.18 Release date 2024/05/03
*YP 4.0.19 build date 2024/06/03
*YP 4.0.19 Release date 2024/06/14


'''Tracking Metrics:'''<br/>
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*WDD 2706 (last week 2688) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1148 (last week 1148)
**Patches in the Pending State: 249 (22%) [last week 249 (22%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''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 54: Line 58:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]

Latest revision as of 14:13, 6 October 2026

Yocto Project Status 6 October 2026

Current Dev Position: YP 6.2 M1 - Development
Next Deadline: YP 6.1 M4: w/c 2026-10-12

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.1 is in QA
  • YP 6.0.4 is pending with QA.
  • Blacksail and master are now on separate branches and have diverged.
  • Patches for 6.2 have started merging into master
  • There are changes to the pypi class so that PYPI_PACKAGE is the normalised name
  • python3-pytz moved from core to meta-oe, if you notice anything using it, it is a sign the dependencies may be obsolete
  • There are issues where we could accept help:
    • Matchbox-wm segfault/xserver restart
    • aarch64/x86-64 build host contamination/reproducibility issue - thanks for the work and fixes so far on this.
    • Remaining github.com references in bitbake-selftest
  • Bitbake’s network disabling has recently been enhanced to include landlock support.
  • This week is Open Source Summit EU and Yocto Project Developer Day in Prague! Contact Paul or Megan if you are attending and want to meet up with other Yocto Project folks, especially if you’re new to our community.
    • Regular meetings on Tuesday and Thursday will be canceled, including the Tech call (Tue 6th), Patch review call (Thu 8th) and Bug triage call (Thu 8th).

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1.0: in QA
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 6.0.4 in QA
    • 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=86891"