Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(684 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status December 11, 2018 ==
== Yocto Project Status 28 April 2026 ==
Current Dev Position: YP 2.7 M1 <br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: YP 2.7 M1 Cutoff is Dec. 10, 2018<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: Chen
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*SWAT team rotation: Chen -> Armin on Nov. 14, 2018
*SWAT team rotation: Armin -> Anuj on Dec. 21, 2018
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.5.2 rc1 is in QA and is 18% complete:  See https://wiki.yoctoproject.org/wiki/2.5_QA_Status
*YP 4.0.35 is due to release
*We’re preparing for 2.7 M1 which should build this week. QA isn’t quite ready since 2.5.2 is being worked on. Most patches targeting M1 have merged at this point and apart from some QA improvement patches, M1 should be mostly ready.
*YP 5.3.4 is in QA
*The btibake persistdb patches related to the sstate hash equivalence code have merged. Any instability noticed in persistdb should be reported ASAP. The rest of the hash equivalency code is now mainly pending on some decisions about terminology and will merge early in M2.
*YP 6.0 rc1 is in QA
*Many of the most predominant oe-selftest bugs have now been resolved, there are a number of less frequent issues remaining and being worked upon. We’ve reached a point where builds aren’t continually throwing up new issues, many thanks to Ross in particular for fixing some gnarly problems and for WindRiver for taking on several of the remaining issues.
*There will be no patch review on Monday 4th May due to public holidays.
*There are patches queued in thud-next and sumo-next which backport the extra json QA reporting and oe-selftest fixes. These series are larger than normal and verge on feature backport but allow us to have better quality releases despite the changes in QA resourcing. As such we therefore believe they are justified and in the project’s interest.
*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.


'''Planned Releases for YP 2.6:'''<br/>
'''Ways to contribute:'''<br/>
*YP 2.7 M1 Cutoff is Dec. 10, 2018
*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.7 M1 Release Target is Dec. 21, 2018
*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.7 M2 Cutoff is Jan. 21, 2019
*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 2.7 M2 Release Target is Feb. 1, 2019
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*YP 2.7 M3 Cutoff is Feb. 25, 2019
*YP 2.7 M3 Release Target is Mar. 8, 2019
*YP 2.7 M4 Cutoff is Apr. 1, 2019
*YP 2.7 M4 Release Target is Apr. 26, 2019


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 2.5.2 (Sumo) is in QA.
*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.1 (Thud) will be targeted after YP 2.7 M1 is done.
*YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
*YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2295 (last week 2425) (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: 1678 (last week 1675)
**Total patches found: 1085 (last week 1078)
**Patches in the Pending State: 740 (44%) [last week 736 (44%)]
**Patches in the Pending State: 146 (13%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Key Status Links for YP:'''<br/>
'''Upcoming dot releases:'''<br/>
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status<br/>
*YP 4.0.35 is in review.
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule<br/>
*YP 5.3.4 is in QA
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features<br/>
**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
 
'''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]]

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"