Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(465 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status February 18, 2020 ==
== Yocto Project Weekly Status July 2nd, 2024 ==
Current Dev Position: YP 3.1 M3  - At Feature Freeze <br/>
Current Dev Position: YP 5.1 M2 <br/>
Next Deadline: YP 3.1 M3 build date 2/24/2020<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Feb. 27th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday July 4th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday  Mar. 3rd at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday July 2nd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Feb. 25th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - See https://www.twitch.tv/theyoctojester
*Twitch - See http://www.twitch.tv/letoatreidesthe2nd


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.7.3 rc1 is in QA with the report due next week.
*YP 5.0.2 is in QA.
*YP 3.0.2 rc2 was rebuilt to remove a broken bash CVE patch, rc3 had automated QA only and is now due for release.
*YP 5.2 M2 is due to build next week.
*We are now at the date for M3 which is feature freeze. We are not yet in a position where we can build M3 as there are a number of open high blocking bugs but patches will need to start tapering down to bug fix only. More invasive or unplanned features will no longer be accepted.
*An issue with code content in python library functions and their effect on task hashes was identified and improvements have merged to bitbake for this.
*We have a serious issue with hashequiv but a patch in progress for that. There is also a usability issue raised with hashequiv and this can only realistically be fixed in M4, it means changing the UI message handling within bitbake.
*A patch changing the way the *FLAGS variables operate merged.
*We continue to see automated test failures with master, most are long standing issues which we’re struggling to resolve. A minority now have had their causes narrowed down or are now reproducible at will which should help but there is concern about the others.
*An autobuilder migration blocking issue with cpu emulation under qemu+KVM was identified and worked around by kernel tweaks, thanks Bruce.
*Some recent changes like psplash systemd support have introduced a race causing intermittent build failures. We had thought those resolved but they reappeared after merging.
*Some larger patches are on the list and help reviewing these would be appreciated:
*Alex Kanavin has quietly but very effectively been fixing ptest failures and we now have only a very small number of non-toolchain tests failing, thanks Alex!
**Adding SPDX 3.0 from Joshua
*We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
**Improved CVE tooling from Marta
*The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.
**bitbake-setup and configuration fragments from Alexander
*There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
**The letter has proved helpful in discussions and helping influence changes at CISA and the CVE Project so has already been useful.
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc. We tested rust 1.78 with master and there is a long list of reported issues on the mailing list unfortunately.


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Ways to contribute:'''<br/>
*YP 3.1 M3 build date 2/24/2020
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*YP 3.1 M3 release date 3/6/2020
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*YP 3.1 M4 build date  3/30/2020
*There are bugs that are currently unassigned for YP 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_Unassigned_Enhancements/Bugs
*YP 3.1 M4 release date  4/24/2020
*We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
*Help us resolve CVE issues: CVE metrics
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''Planned upcoming dot releases:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 2.7.3 built and in QA
*WDD 2802 (last week 2787) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 2.7.3 release date 2/21/2020
*OE-Core/Poky Patch Metrics
*YP 3.0.2 release soon
**Total patches found: 1072 (last week 1076)
*YP 3.0.3 build date  5/4/2020
**Patches in the Pending State: 179 (17%) [last week 205 (19%)]
*YP 3.0.3 release date 5/15/2020
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*YP 2.7.4 build date  5/18/2020
*YP 2.7.4 release date 5/29/2020


'''Tracking Metrics:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*WDD 2665 (last week 2710) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.1 M2 Build date 2024-07-08
*Poky Patch Metrics 
*YP 5.1 M2 Release date 2024-07-19
**Total patches found: 1356 (last week 1360)
*YP 5.1 M3 Build date 2024-08-26
**Patches in the Pending State: 543 (40%) [last week 546 (40%)]
*YP 5.1 M3 Release date 2024-09-06
*YP 5.1 M4 Build date 2024-09-30
*YP 5.1 M4 Release date 2024-10-25
 
'''Upcoming dot releases:'''<br/>
*YP 5.0.2 is in QA.
*YP 5.0.2 Release Date 2024-07-05
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.20 Release Date 2024-07-26
*YP 5.0.3 Build Date 2024-08-12
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.21 Build Date 2024-09-09
*YP 4.0.21 Release Date 2024-09-20
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.22 Build Date 2024-10-14
*YP 4.0.22 Release Date 2024-10-25
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.23 Release Date 2024-11-29


'''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 45: Line 68:


== Archives ==
== Archives ==
*[[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]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 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:40, 2 July 2024

Yocto Project Weekly Status July 2nd, 2024

Current Dev Position: YP 5.1 M2
Next Deadline: YP 5.1 M2 Build 8 July 2024

Next Team Meetings:

Key Status/Updates:

  • YP 5.0.2 is in QA.
  • YP 5.2 M2 is due to build next week.
  • An issue with code content in python library functions and their effect on task hashes was identified and improvements have merged to bitbake for this.
  • A patch changing the way the *FLAGS variables operate merged.
  • An autobuilder migration blocking issue with cpu emulation under qemu+KVM was identified and worked around by kernel tweaks, thanks Bruce.
  • Some larger patches are on the list and help reviewing these would be appreciated:
    • Adding SPDX 3.0 from Joshua
    • Improved CVE tooling from Marta
    • bitbake-setup and configuration fragments from Alexander
  • There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
    • The letter has proved helpful in discussions and helping influence changes at CISA and the CVE Project so has already been useful.
  • We continue to have trouble tracking down the rust reproducibility problem in rustdoc. We tested rust 1.78 with master and there is a long list of reported issues on the mailing list unfortunately.

Ways to contribute:

Tracking Metrics:

YP 5.1 Milestone Dates:

  • YP 5.1 M2 Build date 2024-07-08
  • YP 5.1 M2 Release date 2024-07-19
  • YP 5.1 M3 Build date 2024-08-26
  • YP 5.1 M3 Release date 2024-09-06
  • YP 5.1 M4 Build date 2024-09-30
  • YP 5.1 M4 Release date 2024-10-25

Upcoming dot releases:

  • YP 5.0.2 is in QA.
  • YP 5.0.2 Release Date 2024-07-05
  • YP 4.0.20 Build Date 2024-07-15
  • YP 4.0.20 Release Date 2024-07-26
  • YP 5.0.3 Build Date 2024-08-12
  • YP 5.0.3 Release Date 2024-08-23
  • YP 4.0.21 Build Date 2024-09-09
  • YP 4.0.21 Release Date 2024-09-20
  • YP 5.0.4 Build Date 2024-09-23
  • YP 5.0.4 Release Date 2024-10-04
  • YP 4.0.22 Build Date 2024-10-14
  • YP 4.0.22 Release Date 2024-10-25
  • YP 5.0.5 Build Date 2024-11-11
  • YP 5.0.5 Release Date 2024-11-22
  • YP 4.0.23 Build Date 2024-11-18
  • YP 4.0.23 Release Date 2024-11-29

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Archives