Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(624 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status November 5, 2019 ==
== Yocto Project Status 25 August 2026 ==
Current Dev Position: YP 3.1 M1 <br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 3.1 M1 build Dec. 2, 2019<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


'''SWAT Team Rotation:'''<br/>
'''Next Team Meetings:'''<br/>
*SWAT lead is currently: Armin
*Bug Triage meeting - Thursday 27th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*SWAT team rotation: Armin-> Anuj on Nov. 8, 2019
*Weekly Project Engineering Sync  - Tuesday 25th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*SWAT team rotation: Anuj -> Chen on Nov. 15, 2019
*Yocto Project Patch Review - Thursday 27th Aug. 10am GMT and Monday 31st Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
*Bug Triage meeting Thursday Nov. 7th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Tuesday Nov. 5th at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Nov. 12th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - Next event is Tuesday Nov. 12th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*The project presence at ELC-E in Lyon was strong, thanks to everyone who contributed, be it through presentations, helping with the booth, visiting the booth or attending or assisting with the summit!
*YP 6.0.3 is in QA.
*YP 2.6.4 was released
*YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
*Patches have continued to merge and master is staying roughly current with the pending patch queue. The autobuilder is still suffering a number of intermittent failures which will start to hamper future development. We’re likely going to have to pause and address those before other development can continue.
*For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
*In particular, issues with pseudo on fedora30 have become apparent due to its use of the new statx() syscall.
*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.
*YP 2.7.2 has been built and is now in QA
*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
*The YP TSC worked on and shared a proposal on how an LTS release could work which is available at: https://docs.google.com/document/d/1AwAFDf52f_FoXksbHEVUMlu4hpcI0JMGVG-Kj_sUkyc/
*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:
*We have begun collecting ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
**Matchbox-wm segfault/xserver restart
*If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+Stephen.
**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


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Ways to contribute:'''<br/>
*YP 3.1 M1 Proposed build date 12/2/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 3.1 M1 Proposed release date 12/13/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/
*YP 3.1 M2 Proposed build date 1/20/2020
*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 3.1 M2 Proposed release date 1/31/2020
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*YP 3.1 M3 Proposed build date 2/24/2020
*YP 3.1 M3 Proposed release date 3/6/2020
*YP 3.1 M4 Proposed build date  3/30/2020
*YP 3.1 M4 Proposed release date  4/24/2020


'''Planned upcoming dot releases:'''<br/>
'''New to the project?'''<br/>
*YP 3.0.1 has patches being queued in poky-contrib
*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.2 (Warrior) is in QA.
*YP 2.6.4 (Thud) was released


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2518 (last week 2493) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2659 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1446 (last week 1441)
**Total patches found: 1028 (last week 1030)
**Patches in the Pending State: 579 (40%) [last week 579 (40%)]
**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
 
'''Upcoming development releases:'''<br/>
*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:'''<br/>
*YP 6.0.3 is in QA.
**Release Date w/c 2026-08-24
*YP 5.0.20
**Build Date w/c 2026-08-17
**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


'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 50: Line 68:


== 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, 25 August 2026

Yocto Project Status 25 August 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:

  • YP 6.0.3 is in QA.
  • YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
  • For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
  • 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.
  • We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
  • 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

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 QA.
    • Release Date w/c 2026-08-24
  • YP 5.0.20
    • Build Date w/c 2026-08-17
    • 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