Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(646 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 16, 2019 ==
== Yocto Project Status 12 May 2026 ==
Current Dev Position: YP 2.7 M4 (2.7 rc2 is in QA)<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: YP 2.7 Release Target April 26, 2019<br/>
Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 14th May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 12th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 14th May 10am GMT and Monday 18th May 9am PDT (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 Apr. 19, 2019
*SWAT team rotation: Armin -> Anuj on Apr. 26, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
 
'''Next Team Meetings:'''<br/>
*YP 2.8 Planning meeting Tuesday April 16nd at 8am PDT (https://zoom.us/j/990892712)
*Bug Triage meeting Thursday April 18th at 7:30am PDT (https://zoom.us/j/454367603)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*Stephen is unavailable at the moment, please refer any queries to Richard
*YP 5.3.4 is due to release (has been approved)
*YP 2.6.2 was rebuilt as rc4 to include the boost upgrade revert and is due to be released today. The YP 2.6.2 rc3/4 report is summarized at https://lists.yoctoproject.org/pipermail/yocto/2019-April/044827.html and the results are at https://autobuilder.yocto.io/pub/releases/yocto-2.6.2.rc4/testresults/.
*YP 6.0 is due to release (has been approved)
*YP 2.5.3 is currently going through the QA process.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
*We’re sad to announce that we will be removing eclipse plugin builds from the autobuilder and will not be including the plugin in any future project releases. This is due to a lack of anyone able to help work on the plugin development, bug fixing or release.
*Intermittent build failures continue to be problematic
*The key fixes mentioned in last week’s status have been merged into 2.7.
*We have pruned the release artefacts, please let us know if any you would like to use are missing. We’re also interested to know which ones people actually use outside of uninative/buildtools and the BSP test images.
*A key bug in pseudo was identified which may be the root cause of the long standing glibc-locale uid “host contamination” issue. Many thanks to Peter and Otavio for the help in debugging that. A separate fix should also ensure pseudo works with newer distro coreutils and glibc versions.
*Master is open for new development
*YP 2.7 rc2 (warrior) was built successfully and is currently going through the QA process after 2.5.3 is done.
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. Please send proposals to the mailing list or raise them during the weekly status call, Paul will be collecting these into a project roadmap.
*The ptest results in 2.7 are much more stable than ever before with results being consistent from build to build. At the start of 2.8 we can make some further improvements so we take advantage of this and build upon it to reduce regressions in the system.
*In an effort to keep the patch queue under control, patches are merging to master.
*The list of issues from last week of worrying things we lack resources to improve upon remains:
**Intermittent autobuilder failures (fork running out of resources - which resources?, oe-selftest intermittent issues, gpg signing resource problems, occasional PR server failure and more)
**Build-appliance testing issues (show up on each QA report across multiple releases)
**40% valgrind ptest failures
**Known bitbake memory resident bugs
**Other ptest failures
*The 2.8 planning discussions are starting and there is a google doc summarising the discussions so far: https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/
*If people are planning to work on specific things in 2.8 please let us know so we can incorporate this into our plans. If you’re interested in working on anything in the document, please also let us know or talk with us in one of the planning meetings.


'''Planned Releases for YP 2.7:'''<br/>
'''Ways to contribute:'''<br/>
*YP 2.7 M4 Cutoff was Apr. 1, 2019
*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 M4 Release Target is Apr. 26, 2019
*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/
*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


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 2.5.3 (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


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2523  (last week 2442) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2688 (last week 2698) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1553 (last week 1553)
**Total patches found: 1087 (last week 1087)
**Patches in the Pending State: 654 (42%) [last week 655 (42%)]
**Patches in the Pending State: 146 (13%) [last week 146 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''Upcoming dot releases:'''<br/>
*YP 5.3.4 is due to release
*YP 5.0.18
**Build Date  2026-05-11
**Release Date 2026-05-25
*YP 6.0.1
**Build Date  2026-05-18
**Release Date 2026-06-01
*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.7_Status<br/>
https://wiki.yoctoproject.org/wiki/TSC<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule<br/>
https://wiki.yoctoproject.org/wiki/Yocto_2.7_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:45, 12 May 2026

Yocto Project Status 12 May 2026

Current Dev Position: YP 6.1 M1
Next Deadline: YP 6.1 M1: w/c 2026-06-08

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.3.4 is due to release (has been approved)
  • YP 6.0 is due to release (has been approved)
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
  • Intermittent build failures continue to be problematic
  • We have pruned the release artefacts, please let us know if any you would like to use are missing. We’re also interested to know which ones people actually use outside of uninative/buildtools and the BSP test images.
  • Master is open for new development
  • We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. Please send proposals to the mailing list or raise them during the weekly status call, Paul will be collecting these into a project roadmap.

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