Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(618 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 28, 2020 ==
== Yocto Project Status 10 November 2026 ==
Current Dev Position: YP 3.1 M3 <br/>
Current Dev Position: YP 6.2 M1 - Development<br/>
Next Deadline: YP 3.1 M2 in QA - release 1/31/20<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 Jan. 30th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting - Thursday 12th Nov. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Fab. 4th  at 8am PDT (https://zoom.us/j/990892712)
*Weekly Project Engineering Sync - Tuesday 10th Nov. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Jan. 28th at 8am PDT (https://zoom.us/j/990892712)
*Yocto Project Patch Review - Thursday 12th Nov. 10am GMT and Monday 16th Nov. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Twitch - Next event is Tuesday Feb. 11th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Tip of the Week:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*The scripts in ${WORKDIR}/temp/run.XXX for shell tasks can be quickly hacked and used for standalone debugging by replacing the function call at the end with “bash -i” which will then drop you into a shell environment matching the task being debugged (minus the fakeroot context).
*Bonus marks for anyone sending a patch to add the fakeroot context as comments at the start of the scripts.
*(anyone with tips they’d like to see here, please send to Stephen or Richard)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1 M2 is in QA but has issues with build reproducibility
*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
*We’re unlikely to rebuild M2 as master has the same issues and they look like they will take a while to resolve.
*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 are now serious problems with the build reproducibility test failures on the autobuilder. We’re not sure why there is a sudden set of problems but they are real issues and causing most builds to fail. The tests will have to be disabled unless they can be resolved quickly. There are fixes merged for the CONFIG_SHELL issue and kbd and patches queued as a potential fix for makeinfo. There are more remaining issues, some have open bugs, others don’t have bugs yet. Help with any of these would be appreciated (or help filing the bugs).
*There is also a discussion about recipe specific hosttools: https://lists.openembedded.org/g/openembedded-architecture/message/2467
*We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
*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 have created a “documentation” list and a “licensing” list on the yocto project mailing list infrastructure. We believe these topics would benefit from dedicated discussions, the people involved usually aren’t interested in bulk email as would be found on other lists. The new lists can be found at: https://lists.yoctoproject.org/g/licensing/join and https://lists.yoctoproject.org/g/docs/join
*The project has adopted an updated policy on AI-generated contributions: https://docs.yoctoproject.org/contributor-guide/ai-assisted-contribution-policy.html
*There is continued concern about the number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage.
*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 continue to struggle to get clean ‘full’ builds due to the reproducibility issues in particular.
*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:
*The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.
**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


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Ways to contribute:'''<br/>
*YP 3.1 M2 release date 1/31/2020
*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 3.1 M3 build date 2/24/2020
*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.1 M3 release date 3/6/2020
*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.
*YP 3.1 M4 build date  3/30/2020
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*YP 3.1 M4 release date  4/24/2020


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 2.7.3 build date  2/10/2020
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 2.7.3 release date 2/21/2020
*YP 3.0.2 build date  2/3/2020
*YP 3.0.2 release date 2/14/2020


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2765 (last week 2758) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2636 (last week 2629) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1368 (last week 1357)
**Total patches found: 1047 (last week 1040)
**Patches in the Pending State: 545 (40%) [last week 536 (39%)]
**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: 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:'''<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/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 47: Line 73:


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