Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 4 August 2026 ==
== Yocto Project Status 10 November 2026 ==
Current Dev Position: YP 6.1 M3<br/>
Current Dev Position: YP 6.2 M1 - Development<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>
Next Deadline: YP 6.2 M1: w/c 2026-12-21 <br/>


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


'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 6.1 M2 is due for release
*There is a proposal and proof of concept for changes to layer configuration and setup out for discussion/review: https://lists.openembedded.org/g/openembedded-architecture/message/2463
*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:
*The proposed layer changes will likely be more invasive than many of the recent changes but also incorporate a number of new features and improvements which will make them useful to everyone and allow various cleanups of existing code.
**Matchbox-wm segfault/xserver restart
*There is also a discussion about recipe specific hosttools: https://lists.openembedded.org/g/openembedded-architecture/message/2467
**aarch64/x86-64 build host contamination/reproducibility issue
*The Yocto Project wiki has undergone significant cleanup, mostly with removal of obsolete pages/information. We plan to migrate the remaining data to a different solution. If anyone is able to help with review of content, please let us know.
    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.
*The project has adopted an updated policy on AI-generated contributions: https://docs.yoctoproject.org/contributor-guide/ai-assisted-contribution-policy.html
*Remaining intermittent build failures  of concern:
*There was a widely reported security issue with musl+openssh. The project has published details on the situation here: https://lists.yoctoproject.org/g/yocto-security/message/1728
**other qemu ‘hang’ type issues on ARM
*We had some positive response to our request for help with the issues highlighted from the bug triage team last week. Further help is requested with the following devtool & recipetool issues:
**sometimes yocto-check-layer is showing checksum mismatch issues
**go recipes are not devtool upgradeable (#14944)
**siggen reset issues (“ResourceWarning: unclosed transport”)
**recipetool create should add tag= for git SRC_URI (#15816)
**intermittent ptest failures in many recipes
*We have moved a couple of planned releases forward by a week to avoid needing to make a release during the end of the year holidays.
*Some class cleanups were merged which did require tweaks to some metadata:
**6.1.1:    2026-11-23
**https://lore.kernel.org/openembedded-core/20260802102854.3952760-1-richard.purdie@linuxfoundation.org/
**6.0.5:    2026-11-30
**See the “The series does break some things, notably” section
**5.0.22:  2026-12-07
*Some invasive LICENSE changes have merged into master:
**6.2 M1:  2026-12-14
**We now require the LICENSE field to match SPDX identifiers.
**The build will issue warnings when this isn’t the case.
**Non SPDX licenses will need to be of the form LicenseRef-XXX
**CLOSED is no longer a valid value.
**‘WITH’ license exceptions are now supported
Big thanks to Joshua for getting us to the point where we can finally clean this up!
*We continue to work on the backlog of patches which has slightly reduced and we’re trying to catch up with AUH updates.
*Toolchain upgrades merged to glibc and bintuils with many other recipe version updates too.  
*Rust is now using a shared work directory which reduces disk usage significantly.
*There have been further important fixes in pseudo which were included in the latest upgrade.
*The new uninative does not have i686 build host support. This will mean i686 build host support with uninative will no longer be possible out the box when that is merged to the LTS branches. It is unlikely anyone should be using that!


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 47: Line 36:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2694 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2636 (last week 2629) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1029 (last week 1021)
**Total patches found: 1047 (last week 1040)
**Patches in the Pending State: 141 (14%) [last week 141 (14%)]
**Patches in the Pending State: 135 (13%) [last week 135 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/3


'''Upcoming development releases:'''<br/>
'''Upcoming development releases:'''<br/>
*6.1 M2: due for release
*6.1.0: is due for release
**Release Date: w/c 2026-08-03
*YP 6.2 M1
*6.1 M3:
**Build Date w/c 2026-12-07
**Build Date: w/c 2026-08-31
**Release Date w/c 2026-12-21
**Release Date: w/c 2026-09-14
*YP 6.2 M2
*6.1.0:
**Build Date w/c 2027-01-18
**Build Date (M4): w/c 2026-10-12
**Release Date w/c 2027-02-01
**Release Date: w/c 2026-11-02
*YP 6.2 M3
**Build Date w/c 2027-03-01
**Release Date w/c 2027-03-15
*YP 6.2.0
**Build Date w/c 2027-04-26
**Release Date w/c 2027-05-03


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 6.0.3 due to release
*YP 6.1.1
**Release Date w/c 2026-08-24
**Build Date w/c 2026-11-16
*YP 5.0.20
**Release Date w/c 2026-11-30
**Build Date w/c 2026-08-17
*YP 6.0.5
**Release Date w/c 2026-08-31
**Build Date w/c 2026-11-23
 
**Release Date w/c 2026-12-07
*YP 5.0.22
**Build Date w/c 2026-11-30
**Release Date w/c 2026-12-14
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


Latest revision as of 15:48, 10 November 2026

Yocto Project Status 10 November 2026

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

Next Team Meetings:

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

Key Status/Updates:

  • There is a proposal and proof of concept for changes to layer configuration and setup out for discussion/review: https://lists.openembedded.org/g/openembedded-architecture/message/2463
  • The proposed layer changes will likely be more invasive than many of the recent changes but also incorporate a number of new features and improvements which will make them useful to everyone and allow various cleanups of existing code.
  • There is also a discussion about recipe specific hosttools: https://lists.openembedded.org/g/openembedded-architecture/message/2467
  • The Yocto Project wiki has undergone significant cleanup, mostly with removal of obsolete pages/information. We plan to migrate the remaining data to a different solution. If anyone is able to help with review of content, please let us know.
  • The project has adopted an updated policy on AI-generated contributions: https://docs.yoctoproject.org/contributor-guide/ai-assisted-contribution-policy.html
  • There was a widely reported security issue with musl+openssh. The project has published details on the situation here: https://lists.yoctoproject.org/g/yocto-security/message/1728
  • We had some positive response to our request for help with the issues highlighted from the bug triage team last week. Further help is requested with the following devtool & recipetool issues:
    • go recipes are not devtool upgradeable (#14944)
    • recipetool create should add tag= for git SRC_URI (#15816)
  • We have moved a couple of planned releases forward by a week to avoid needing to make a release during the end of the year holidays.
    • 6.1.1: 2026-11-23
    • 6.0.5: 2026-11-30
    • 5.0.22: 2026-12-07
    • 6.2 M1: 2026-12-14

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1.0: is due for release
  • YP 6.2 M1
    • Build Date w/c 2026-12-07
    • Release Date w/c 2026-12-21
  • YP 6.2 M2
    • Build Date w/c 2027-01-18
    • Release Date w/c 2027-02-01
  • YP 6.2 M3
    • Build Date w/c 2027-03-01
    • Release Date w/c 2027-03-15
  • YP 6.2.0
    • Build Date w/c 2027-04-26
    • Release Date w/c 2027-05-03

Upcoming dot releases:

  • YP 6.1.1
    • Build Date w/c 2026-11-16
    • Release Date w/c 2026-11-30
  • YP 6.0.5
    • Build Date w/c 2026-11-23
    • Release Date w/c 2026-12-07
  • YP 5.0.22
    • Build Date w/c 2026-11-30
    • Release Date w/c 2026-12-14
  • 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:
https://wiki.yoctoproject.org/wiki/TSC

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86913"