Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(644 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 30, 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/>
 
*SWAT lead is currently: Paul
*SWAT team rotation: Paul -> Anuj on May. 3, 2019
*SWAT team rotation: Anuj -> Ross on May. 10, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday May 2nd at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting - Thursday 14th May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*YP 2.8 Planning meeting Tuesday May 7th at 8am PDT (https://zoom.us/j/990892712)  
*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)


'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*Stephen is going to be unavailable for several weeks, please refer any queries to Richard
*YP 5.3.4 is due to release (has been approved)
*YP 2.5.3 was released.
*YP 6.0 is due to release (has been approved)
*YP 2.7 is out of QA but pending answers to some questions on the QA report and the final pieces of release process.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
*Huge kudos this week go to Armin for work on test automation of some of the manual tests
*Intermittent build failures continue to be problematic
*We’ve merged ltp test automation which is now being run automatically on the autobuilder on a-full builds.
*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 continues to take patches, somewhat slowed by host specific build issues with vte-native
*Master is open for new development
*WDD, our bug tracking metric is high and there are few people helping with bugs.
*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 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.
*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


'''Ways to contribute:'''<br/>
*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 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 Releases for YP 2.7:'''<br/>
'''New to the project?'''<br/>
*YP 2.7 M4 Cutoff was Apr. 1, 2019
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 2.7 M4 Release Target is Apr. 26, 2019


'''Planned upcoming dot releases:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 2.6.3 (Thud) is in planning
*WDD 2688 (last week 2698) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1087 (last week 1087)
**Patches in the Pending State: 146 (13%) [last week 146 (13%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2593 (last week 2598) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.3.4 is due to release
*Poky Patch Metrics  
*YP 5.0.18
**Total patches found: 1565 (last week 1553)
**Build Date 2026-05-11
**Patches in the Pending State: 655 (42%) [last week 654 (42%)]
**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"