Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
(653 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 18, 2019 ==
== Yocto Project Status 8 September 2026 ==
Current Dev Position: YP 2.8 M2<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 2.8 Milestone 2 Cutoff July 14th, 2019<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


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


*SWAT lead is currently: Paul
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*SWAT team rotation: Paul -> Ross on June 21, 2019
*SWAT team rotation: Ross -> Amanda on June 28, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Key Status/Updates:'''<br/>
*Bug Triage meeting Thursday June 20th at 7:30am PDT (https://zoom.us/j/454367603)
* YP 5.0.20 is under review.
*Monthly Project Meeting Tuesday July 2nd at 8am PDT (https://zoom.us/j/990892712)
* YP 6.1 M3 is due to build and we are at feature freeze
*Twitch - Next event is Tuesday 9th July at 8am PDT (https://www.twitch.tv/yocto_project)
* There are issues with changes in bot/AI protection at github.com which are affecting our CI.
* Most M3 changes have merged, we want to mitigate the github issues before building M3.
* There is a new meta-openjdk layer: https://github.com/amarula/meta-openjdk https://lore.kernel.org/yocto-patches/xBB4.1788187111192557019.ULaN@lists.yoctoproject.org/T/#u
* AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
* There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
** Matchbox-wm segfault/xserver restart
** aarch64/x86-64 build host contamination/reproducibility issue
We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*Remaining intermittent build failures of concern:
**other qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**intermittent ptest failures in many recipes
*Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!


'''Key Status/Updates:'''<br/>
'''Ways to contribute:'''<br/>
*2.8 M1 has been through QA and is waiting on responses from YP TSC members on release readiness. It had more issues that would be ideal but most were relatively minor and are being worked upon, several with known causes now with fixes in master. As such its likely to be released.
*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=---
*Stephen is recovering from the accident and will now respond to emails. We’re pleased to have him back and wish him a continued speedy recovery!
*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/
*Mailing lists are proving to be a tricky subject. Some people are having trouble with emails not making it to the lists which we recognise is a serious issue. Equally, our groups.io plan isn’t proving workable without major user visible change due to the current domain structure we have. *It is being worked on as a priority to find a way forward.
*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.
*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
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*We’re grateful to Sandy, WindRiver and Michael for helping get patchtest back into operation. Its tests are looking like they could do with a little improvement but it is catching some issues and great to see progress with it again.
*During M2 Richard plans to look into our options for changing runqueue to better support more advanced sstate usage. This may have an impact on how quickly patches merge as the work there is involved and needs focus.
*We’d like to remind people that where test suites exist, we’d appreciate it if people would run them before they send patches, e.g. “oe-selftest -r devtool” or “oe-selftest -r wic”.


'''Planned Releases for YP 2.8:'''<br/>
'''New to the project?'''<br/>
*M1 is built and out of QA
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*M2 Cutoff 14th July
*M2 Release 26th July
*M3 Cutoff (Feature Freeze) 25th Aug
*M3 Release 6th Sept
*M4 Cutoff 30th Sept
*2.8 (M4) Final Release 25th Oct


'''Tracking Metrics:'''<br/>
*WDD 2622 (last week 2612) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1050 (last week 1039)
**Patches in the Pending State: 136 (13%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Planned upcoming dot releases:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 2.7.1 (Warrior) is planned for build imminently now that 2.8 M1 is done
*6.1 M3:
*YP 2.6.3 (Thud) is intended for build after 2.7.1 is complete and before 2.8 M2
**Build Date: w/c 2026-08-31
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2479 (last week 2478) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 6.0.3 is in review.
*Poky Patch Metrics 
**Release Date w/c 2026-08-24
**Total patches found: 1511 (last week 1507)
*YP 5.0.20 is in QA.
**Patches in the Pending State: 641 (43%) [last week 641 (43%)]
**Release Date w/c 2026-08-31
*YP 6.0.4
**Build Date w/c 2026-09-28
**Release Date w/c 2026-10-12
*YP 5.0.21
**Build Date w/c 2026-10-05
**Release Date w/c 2026-10-19
 
*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:41, 8 September 2026

Yocto Project Status 8 September 2026

Current Dev Position: YP 6.1 M3
Next Deadline: YP 6.1 M3: w/c 2026-08-31

Next Team Meetings:

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

Key Status/Updates:

We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.

  • Remaining intermittent build failures of concern:
    • other qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • intermittent ptest failures in many recipes
  • Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M3:
    • Build Date: w/c 2026-08-31
    • Release Date: w/c 2026-09-14
  • 6.1.0:
    • Build Date (M4): w/c 2026-10-12
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 6.0.3 is in review.
    • Release Date w/c 2026-08-24
  • YP 5.0.20 is in QA.
    • Release Date w/c 2026-08-31
  • YP 6.0.4
    • Build Date w/c 2026-09-28
    • Release Date w/c 2026-10-12
  • YP 5.0.21
    • Build Date w/c 2026-10-05
    • Release Date w/c 2026-10-19

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