Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(501 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Jan. 12, 2021 ==
== Yocto Project Status 10 November 2026 ==
Current Dev Position: YP 3.3 M2 development<br/>
Current Dev Position: YP 6.2 M1 - Development<br/>
Next Deadline: 18th January 2021 YP 3.3 M2 build<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. 14th at 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)
*Monthly Project Meeting Tuesday Feb. 2nd at 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)
*Weekly Engineering Sync Tuesday Jan. 12th at 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)
*Twitch -  See https://www.twitch.tv/theyoctojester
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*Patches for 3.3 M2 development are being tested and merged. We have one week left before M2 is due to be built.
*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
*It was a mixed week for builds and patches, several reproducibility issues appeared and issues also appeared after patches had merged in the second or third build after that due to state reuse and differences between worker distros. This makes merging the patches challenging.
*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.
*In particular, an upgrade to qemu 5.2.0 did merge. That upgrade includes a change to the underlying build system and the patchset was significantly rationalised which may cause issues. In particular, issues on centos hosts were eventually traced to the mmap_min_addr setting being too low (65536 now seems to be the useful minimum).
*There is also a discussion about recipe specific hosttools: https://lists.openembedded.org/g/openembedded-architecture/message/2467
*We are now tracking intermittent ptest failures and a number of bugs have been opened for these, we don’t as yet have people able to work on them though.
*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.
*CVE metrics are starting to trend down again but we still have 56 “open” CVEs against master and more in gatesgath/dunfell so help in further reducing the number would be appreciated.
*The project has adopted an updated policy on AI-generated contributions: https://docs.yoctoproject.org/contributor-guide/ai-assisted-contribution-policy.html
*Intermittent autobuilder issues continue to occur and with more invasive changes and higher rebuild rates, the numbers are increasing again. 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
*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:'''<br/>
'''Ways to contribute:'''<br/>
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 that are currently unassigned for YP 3.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enhancements.2FBugs
*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/
*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.
*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
 
'''New to the project?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''YP 3.3 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.3 M2 build date 2021/01/18
*WDD 2636 (last week 2629) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.3 M2 Release date 2021/01/29
*OE-Core/Poky Patch Metrics
*YP 3.3 M3 build date 2021/03/01
**Total patches found: 1047 (last week 1040)
*YP 3.3 M3 Release date 2021/03/12
**Patches in the Pending State: 135 (13%) [last week 135 (13%)]
*YP 3.3 M4 build date 2021/04/05
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/3
*YP 3.3 M4 Release date 2021/04/30


'''Planned upcoming dot releases:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 3.1.5 build date 2021/01/11
*6.1.0: is due for release
*YP 3.1.5 release date 2021/01/22
*YP 6.2 M1
*YP 3.2.2 build date 2021/02/08
**Build Date w/c 2026-12-07
*YP 3.2.2 release date 2021/02/19
**Release Date w/c 2026-12-21
*YP 3.1.6 build date 2021/02/22
*YP 6.2 M2
*YP 3.1.6 release date 2021/03/05
**Build Date w/c 2027-01-18
*YP 3.1.7 build date 2021/03/22
**Release Date w/c 2027-02-01
*YP 3.1.7 release date 2021/04/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


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2587 (last week 2598) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 6.1.1
*Poky Patch Metrics 
**Build Date w/c 2026-11-16
**Total patches found: 1298 (last week 1311)
**Release Date w/c 2026-11-30
**Patches in the Pending State: 503 (39%) [last week 507 (39%)]
*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 50: 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]]
*[[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"