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...")
 
 
(899 intermediate revisions by 7 users not shown)
Line 1: Line 1:
Subject: Yocto Project Status WW04’18
== Yocto Project Status 10 November 2026 ==
Current Dev Position: YP 6.2 M1 - Development<br/>
Next Deadline: YP 6.2 M1: w/c 2026-12-21 <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 12th Nov. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10th Nov. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Nov. 10am GMT and Monday 16th Nov. 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
*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
With a round of security released fixes likely to land shortly, we’ll likely wait for these before we roll M2.
*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.
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.
*There is also a discussion about recipe specific hosttools: https://lists.openembedded.org/g/openembedded-architecture/message/2467
The AUH emails have triggered a good batch of recipe upgrades. QEMU was also upgraded (which can often cause problems).
*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.
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
*The project has adopted an updated policy on AI-generated contributions: https://docs.yoctoproject.org/contributor-guide/ai-assisted-contribution-policy.html
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 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
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.
*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


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 2636 (last week 2629) (https://wiki.yoctoproject.org/charts/combo.html)
(https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1047 (last week 1040)
**Patches in the Pending State: 135 (13%) [last week 135 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/3


Key Status Links for YP:
'''Upcoming development releases:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.5_Status
*6.1.0: is due for release
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Schedule
*YP 6.2 M1
https://wiki.yoctoproject.org/wiki/Yocto_2.5_Features
**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


[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.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:'''<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 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"