Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(627 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status August 6, 2019 ==
== Yocto Project Status 28 April 2026 ==
Current Dev Position: YP 2.8 M3<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: YP 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, 2019<br/>
Next Deadline: YP 6.0 Release Date w/c 2026-05-04<br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 30th Apr. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 29th Apr. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 30th Apr. 10am GMT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


*SWAT lead is currently: Ross
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*SWAT team rotation: Ross -> Amanda on Aug. 9, 2019
*SWAT team rotation: Amanda -> Chen on Aug. 16, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
 
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday August 8th 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 is due for release this week
*YP 4.0.35 is due to release
*YP 2.6.3 is in QA
*YP 5.3.4 is in QA
*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
*YP 6.0 rc1 is in QA
*This release which was 2.8 will now become 3.0
*There will be no patch review on Monday 4th May due to public holidays.
*The project is working on some mentor and mentee opportunities. Please see the separate email from Nicolas on the yocto list about this.
*We continue to triage the CVEs being reported by the new tooling.
*Patches to bitbake to enable the task scheduler to react to “equivalent” build output have merged. There is more information about this major change in a separate email:
*There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
http://lists.openembedded.org/pipermail/openembedded-core/2019-August/285300.html
*There have been several issues in pseudo identified and these have been fixed in the various pseudo point releases. We will upgrade pseudo in 6.0.1 to pull these in.
*It is hoped this change should improve productivity and reduce rebuilds.
*There have been issues with 403 errors from crates.io, there is a change in bitbake to use the preferred upstream urls via their CDN.
*In making some of these changes, there were some API changes in bitbake, notably the removal of the bb.build.FuncFailed exception, the signature generator task representation changed and there were some siggen function API changes.
*The kvm cpu features issue looks to be a host system CPU microcode issue and using the latest microcode appears to have resolved the issues.
libx11-diet was removed as its not really appropriate on a modern locale aware system.
*git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback but are trying to clear the backlog.


'''Planned Releases for YP 3.0 {2.8}:'''<br/>
'''Ways to contribute:'''<br/>
*M2 is out of QA and being reviewed.
*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 - this will be YP 3.0.
*YP 3.0 {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 in QA.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2481 (last week 2466) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2788 (last week 2790) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1496 (last week 1498)
**Total patches found: 1085 (last week 1078)
**Patches in the Pending State: 615 (41%) [last week 619 (41%)]
**Patches in the Pending State: 146 (13%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''Upcoming dot releases:'''<br/>
*YP 4.0.35 is in review.
*YP 5.3.4 is in QA
**Release Date 2026-05-06
*YP 5.0.18
**Build Date  2026-05-11
**Release Date 2026-05-25
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


'''Key Status Links for YP:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features<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 14:51, 28 April 2026

Yocto Project Status 28 April 2026

Current Dev Position: YP 6.0 M4
Next Deadline: YP 6.0 Release Date w/c 2026-05-04

Next Team Meetings:

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

Key Status/Updates:

  • YP 4.0.35 is due to release
  • YP 5.3.4 is in QA
  • YP 6.0 rc1 is in QA
  • There will be no patch review on Monday 4th May due to public holidays.
  • We continue to triage the CVEs being reported by the new tooling.
  • There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
  • There have been several issues in pseudo identified and these have been fixed in the various pseudo point releases. We will upgrade pseudo in 6.0.1 to pull these in.
  • There have been issues with 403 errors from crates.io, there is a change in bitbake to use the preferred upstream urls via their CDN.
  • The kvm cpu features issue looks to be a host system CPU microcode issue and using the latest microcode appears to have resolved the issues.
  • git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
  • We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback but are trying to clear the backlog.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming dot releases:

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=86818"