Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(658 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 30, 2019 ==
== Yocto Project Status 10 November 2026 ==
Current Dev Position: YP 2.8 M3<br/>
Current Dev Position: YP 6.2 M1 - Development<br/>
Next Deadline: YP 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, 2019<br/>
Next Deadline: YP 6.2 M1: w/c 2026-12-21 <br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
 
*Bug Triage meeting - Thursday 12th Nov. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*SWAT lead is currently: Paul
*Weekly Project Engineering Sync - Tuesday 10th Nov. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*SWAT team rotation: Paul -> Ross on Aug. 2, 2019
*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: Ross -> Amanda on Aug. 9, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*Bug Triage meeting Thursday August 1st at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting August 6th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - Next event is August 6th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.8 M2 rc1 is in QA which is due to complete on Wednesday
*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
*YP 2.6.3 will build to go into QA on Wednesday
*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.
*We have a new “newcomer” bug category which are bugs suited to someone new to the project. These can be seen here: https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs
*There is also a discussion about recipe specific hosttools: https://lists.openembedded.org/g/openembedded-architecture/message/2467
*The Yocto Project TSC has determined how it plans to operate and put the details into the appropriate wiki page: https://wiki.yoctoproject.org/wiki/TSC. It is intended as a decision making body of last resort, if there are issues people wish it to address, please raise them with one of its members.
*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.
*After discussion in various places its been agreed that the next project release will be “3.0”, to replace “2.8”. The 2.8 placeholder may continue to be used, particularly in the bugzilla. There are many good reasons to bump the version, the most recent being the runqueue changes allowing build optimizations based upon output equivalence (see below) but also including the new project governance, the autobuilder, improved test coverage any many other things.
*The project has adopted an updated policy on AI-generated contributions: https://docs.yoctoproject.org/contributor-guide/ai-assisted-contribution-policy.html
*There are patches available which enable runqueue optimisations based on output comparisons of tasks. This removes the need to run later tasks if the output is unchanged and is based upon the previous hash equivalence server work. This feature should be a significant win for the users and is now working to a level where we’ll likely make this a key feature of the next release. These patches are being tested in master-next at present.
*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 are also changes in -next which are being considered which change several bitbake APIs around runqueue. The feeling is now may be the best time to clean up several interfaces. If there are other API fixes people want to see, now is a good time to mention them.
*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 project is working on some mentor and mentee opportunities. Please see the separate email from Nicolas on the yocto list about this.
**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 Releases for YP 2.8:'''<br/>
'''Ways to contribute:'''<br/>
*M2 is in QA
*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=---
*M2 Release 26th July
*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/
*M3 Cutoff (Feature Freeze) 25th Aug
*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.
*M3 Release 6th Sept
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*M4 Cutoff 30th Sept
*2.8 (M4) Final Release 25th Oct


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 2.7.2 (Warrior) is planned for after 2.8 M2  release.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and before 2.8 M3.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2483 (last week 2489) (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: 1499 (last week 1502)
**Total patches found: 1047 (last week 1040)
**Patches in the Pending State: 623 (42%) [last week 630 (42%)]
**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:'''<br/>
'''Upcoming development releases:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status<br/>
*6.1.0: is due for release
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule<br/>
*YP 6.2 M1
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features<br/>
**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/>
https://wiki.yoctoproject.org/wiki/TSC<br/>


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