Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(536 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 2, 2019 ==
== Yocto Project Weekly Status July 2nd, 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<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<br/>
 
'''SWAT Team Rotation:'''<br/>
 
*SWAT lead is currently: Ross
*SWAT team rotation: Ross -> Amanda on Apr. 5, 2019
*SWAT team rotation: Amanda -> Chen on Apr. 12, 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) or see the invite on the mailing list at: (https://lists.yoctoproject.org/pipermail/yocto/2019-April/044654.html)  
*Bug Triage meeting Thursday July 4th 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 July 2nd 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/>
*The QA report for M3 rc1 is available. This is the first time we’ve used the new QA process so we’re still understanding how the new format for the data works out. There are some issues but right now we believe we’ll aim to fix these before the final release build and proceed to that with the first build of M4 aiming for next week.
*YP 5.0.2 is in QA.
*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 5.2 M2 is due to build next week.
*2.5.3 and 2.6.2 stable releases were built and submitted to QA last 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.
*The “warrior” branches for 2.7 have been created and the metadata updated. This will have a ripple effect across the layers as they update to match this. This process is important as it allows layers to indicate which versions of the project they are compatible with.
*A patch changing the way the *FLAGS variables operate merged.
*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/
*An autobuilder migration blocking issue with cpu emulation under qemu+KVM was identified and worked around by kernel tweaks, thanks Bruce.
*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.
*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:'''<br/>
*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!
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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
*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 Releases for YP 2.7:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 2.7 M4 Cutoff is Apr. 1, 2019
*WDD 2802 (last week 2787) (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: 1072 (last week 1076)
**Patches in the Pending State: 179 (17%) [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 M2 Build date 2024-07-08
*YP 2.6.2 (Thud) is in QA.
*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 5.0.2 is in QA.
*Poky Patch Metrics 
*YP 5.0.2 Release Date 2024-07-05
**Total patches found: 1542 (last week 1538)
*YP 4.0.20 Build Date 2024-07-15
**Patches in the Pending State: 654 (42%) [last week 656 (43%)]
*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]]

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

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