Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(531 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 9, 2019 ==
== Yocto Project Weekly Status June 25th, 2024 ==
Current Dev Position: YP 2.7 M4 (New feature Freeze has begun.)<br/>
Current Dev Position: YP 5.1 M2 <br/>
Next Deadline: YP 2.7 M3 Release Target was Mar. 8, 2019 and it should release today<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<br/>
 
'''SWAT Team Rotation:'''<br/>
 
*SWAT lead is currently: Amanda
*SWAT team rotation: Amanda -> Chen on Apr. 12, 2019
*SWAT team rotation: Chen -> Armin on Apr. 19, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*YP 2.8 Planning meeting Tuesday April 2nd at 8am PDT (https://zoom.us/j/990892712)
*Bug Triage meeting Thursday June 27th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday April 4th at 7:30am PDT (https://zoom.us/j/454367603)
*Weekly Engineering Sync Tuesday June 25th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.7 M3 rc1 will be released today. The YP 2.7 M3 rc1 report is summarized at https://lists.yoctoproject.org/pipermail/yocto/2019-April/044667.html and the results are at https://autobuilder.yocto.io/pub/releases/yocto-2.7_M3.rc1/testresults/.
*YP 4.0.19  and YP 5.1 M1 were released
*YP 2.5.3 and YP 2.6.2 stable releases were built and have been submitted to QA
*YP 5.0.2 was built and is entering QA.
*YP 2.6.2 is currently going through the QA process with YP 2.5.3 queued behind it.  
*There were some great patch status cleanups, thanks Alexander (will show in next week’s metrics)
*Process issues in the way ptest was being processed by QA have been discovered which mean the previous ptest results are not comparable with the new QA process. For consistency going forward we will be using the new QA process as the definitive results and will be comparing for regressions based upon these.
*There is a patch to improve the way the *FLAGS variables operate. It is possible this may change behavior in some corner cases but the usability improvements mean we’re likely to merge the patch and address any issues that arise.
*The “warrior” branches for 2.7 have been created and the metadata updated, patches are being slowed in line with release stablisation with increasingly critical fixes only.
*Some larger patches are on the list and help reviewing these would be appreciated:
*The remaining things which are planned for YP 2.7 M4 before we have the final 2.7 rc1 build are:
**Adding SPDX 3.0 from Joshua
**Upgrading -tiny to the 5.0 linux-yocto kernel (currently 4.18)
**Improved CVE tooling from Marta
**Removal of the 4.18 kernel
**bitbake-setup and configuration fragments from Alexander
**Fixing the python3 ptest timeout and result status issues
*We had some fixes for the install-buildtools script which showed a lack of automated testing for it. Adding some would be an interesting first contribution if anyone is interested.
**Fixing some of the util-linux ptest failures
*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
**Potentially integrating a key and long time puzzling pseudo issue
**Please consider signing this to show support for those changes.
**Integrating qemumips shutdown issues identified in the kernel
**Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
**Continue to investigate python3 testsuite hang on 5.0+ kernels (trying to get help upstream)
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
*Worrying things which we don’t have good plans for currently (mainly lack of people to help with):
 
**Intermittent autobuilder failures (fork running out of resources - which resources?, oe-selftest intermittent issues, gpg signing resource problems, occasional PR server failure and more)
'''Ways to contribute:'''<br/>
**Build-appliance testing issues (show up on each QA report across multiple releases)
*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!
**40% valgrind ptest failures
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
**Known bitbake memory resident bugs
*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
**Other ptest failures
*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.
*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/
*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.
*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.
*Help us resolve CVE issues: CVE metrics
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''Planned Releases for YP 2.7:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 2.7 M4 Cutoff is Apr. 1, 2019
*WDD 2787 (last week 2779) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 2.7 M4 Release Target is Apr. 26, 2019
*OE-Core/Poky Patch Metrics
**Total patches found: 1076 (last week 1072)
**Patches in the Pending State: 205 (19%) [last week 205 (19%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''Planned upcoming dot releases:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 2.5.3 (Sumo) is in QA.
*YP 5.1 M1 is released.
*YP 2.6.2 (Thud) is in QA.
*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


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2442 (last week 2418) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.0.19 is released.
*Poky Patch Metrics 
*YP 5.0.2 is built.
**Total patches found: 1542 (last week 1538)
*YP 5.0.2 Release Date 2024-07-05
**Patches in the Pending State: 654 (42%) [last week 656 (43%)]
*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


'''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 ==
*[[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]]

Revision as of 14:38, 25 June 2024

Yocto Project Weekly Status June 25th, 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 4.0.19 and YP 5.1 M1 were released
  • YP 5.0.2 was built and is entering QA.
  • There were some great patch status cleanups, thanks Alexander (will show in next week’s metrics)
  • There is a patch to improve the way the *FLAGS variables operate. It is possible this may change behavior in some corner cases but the usability improvements mean we’re likely to merge the patch and address any issues that arise.
  • 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
  • We had some fixes for the install-buildtools script which showed a lack of automated testing for it. Adding some would be an interesting first contribution if anyone is interested.
  • 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
    • Please consider signing this to show support for those changes.
    • Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
  • We continue to have trouble tracking down the rust reproducibility problem in rustdoc.

Ways to contribute:

Tracking Metrics:

YP 5.1 Milestone Dates:

  • YP 5.1 M1 is released.
  • 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 4.0.19 is released.
  • YP 5.0.2 is built.
  • 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

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86372"