Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(85 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status May 9th, 2023 ==
== Yocto Project Weekly Status April 30th, 2024 ==
Current Dev Position: YP 4.3 M1<br/>
Current Dev Position: YP 5.1 M1 <br/>
Next Deadline: 5th June 2023 YP 4.3 M1 build date<br/>
Next Deadline: YP 5.1 M1 Build 20 May 2024<br/>


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.2 rc3 has passed QA and is pending TSC approval for release.
*YP 5.0 has been released!
*YP 4.1.4 is now in QA.
*Huge thanks to everyone who contributed to 5.0
*Patches are merging into master for 4.3.
*YP 3.1.33 has passed QA and is due to release
*Emails to all currently listed maintainers have been sent to check the entries are up to date. If anyone is interested in taking on maintenance of any unassigned recipes, please send a patch.
*YP 4.0.18 is in QA.
*We discovered warnings were not being correctly handled on the autobuilder after the buildbot controller upgrade. That should now be fixed but it means some regressions may have crept in, we’re working to confirm if that is the case or not.
*Updates to graphing on the patch/CVE metrics page merged
*We’re in the process of adding checks to ensure that ptests returning no test results trigger warnings. This should ensure we catch this situation earlier since ptests should always return at least one test result. python3-cryptography is an example of a recipe that recently regressed unnoticed in this way.
*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, which would improve our ability to analyze CVEs, and that of many other projects (including other distros) to do so too.
*We continue to watch the NIST NVD (CVE database) situation, the lack of CPE information is problematic for us and we are considering what alternatives we have. The CVE Project announced support for more information fields on CVEs which is a good start.
*Some CVE information is being provided for issues in meta-openembedded, this has been provided with help from the Sovereign Tech Fund.
*The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date.  
*There are proposals on the openembedded-architecture list to rework how do_unpack works, switching it from WORKDIR to a new variable and changing some directory layout.
 


'''Ways to contribute:'''<br/>
'''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: patchtest, layerindex, 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!
*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 identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*There are bugs that are currently unassigned for YP 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
*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.
*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 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.
Line 25: Line 30:
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''YP 4.2 Milestone Dates:'''<br/>
*YP 4.2 was released


'''YP 4.3 Milestone Dates:'''<br/>
'''YP 5.1 Milestone Dates:'''<br/>
*YP 4.3 M1 build date 2023/06/05
*YP 5.1 M1 Build date 2024-05-20
*YP 4.3 M1 Release date 2023/06/16
*YP 5.1 M1 Release date 2024-05-31
*YP 4.3 M2 build date 2023/07/17
*YP 5.1 M2 Build date 2024-07-08
*YP 4.3 M2 Release date 2023/07/28
*YP 5.1 M2 Release date 2024-07-19
*YP 4.3 M3 build date 2023/08/28
*YP 5.1 M3 Build date 2024-08-26
*YP 4.3 M3 Release date 2023/09/08
*YP 5.1 M3 Release date 2024-09-06
*YP 4.3 M4 build date 2023/10/02
*YP 5.1 M4 Build date 2024-09-30
*YP 4.3 M4 Release date 2023/10/27
*YP 5.1 M4 Release date 2024-10-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.1.4 is released
*YP 3.1.33 is in QA
*YP 3.1.25 is in QA
*YP 4.0.18 is in QA
*YP 3.1.25 Release date 2023/05/19
*YP 4.0.18 Release date 2024-05-03
*YP 4.0.10 build date 2023/05/15
*YP 5.0.1 Build Date 2024-05-13
*YP 4.0.10 Release date 2023/05/26
*YP 5.0.1 Release Date 2024-05-24
*YP 4.2.1 build date 2023/05/22
*YP 4.0.19 build date 2024-06-03
*YP 4.2.1 Release date 2023/06/02
*YP 4.0.19 Release date 2024-06-14
*YP 3.1.26 build date 2023/06/19
*YP 5.0.2 Build Date 2024-06-24
*YP 3.1.26 Release date 2023/06/30
*YP 5.0.2 Release Date 2024-07-05
*YP 4.0.11 build date 2023/06/26
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.11 Release date 2023/07/07
*YP 4.0.20 Release Date 2024-07-26
*YP 4.2.2 build date 2023/07/10
*YP 5.0.3 Build Date 2024-08-12
*YP 4.2.2 Release date 2023/07/21
*YP 5.0.3 Release Date 2024-08-23
*YP 3.1.27 build date 2023/07/31
*YP 4.0.21 Build Date 2024-09-09
*YP 3.1.27 Release date 2023/08/11
*YP 4.0.21 Release Date 2024-09-20
*YP 4.0.12 build date 2023/08/07
*YP 5.0.4 Build Date 2024-09-23
*YP 4.0.12 Release date 2023/08/18
*YP 5.0.4 Release Date 2024-10-04
*YP 4.2.3 build date 2023/08/28
*YP 4.0.22 Build Date 2024-10-14
*YP 4.2.3 Release date 2023/09/08
*YP 4.0.22 Release Date 2024-10-25
*YP 3.1.28 build date 2023/09/18
*YP 5.0.5 Build Date 2024-11-11
*YP 3.1.28 Release date 2023/09/29
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.13 build date 2023/09/25
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.13 Release date 2023/10/06
*YP 4.0.23 Release Date 2024-11-29
*YP 3.1.29 build date 2023/10/30
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.14 build date 2023/11/06
*YP 4.0.14 Release date 2023/11/17
*YP 4.2.4 build date 2023/11/13
*YP 4.2.4 Release date 2023/11/24
*YP 3.1.30 build date 2023/12/11
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2517 (last week 2512) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2728 (last week 2714) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1201 (last week 1203)
**Total patches found: 1125 (last week 1140)
**Patches in the Pending State: 278 (23%) [last week 278 (23%)]
**Patches in the Pending State: 221 (20%) [last week 245 (21%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


Line 84: Line 77:


== Archives ==
== Archives ==
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]

Latest revision as of 14:47, 30 April 2024

Yocto Project Weekly Status April 30th, 2024

Current Dev Position: YP 5.1 M1
Next Deadline: YP 5.1 M1 Build 20 May 2024

Next Team Meetings:

Key Status/Updates:

  • YP 5.0 has been released!
  • Huge thanks to everyone who contributed to 5.0
  • YP 3.1.33 has passed QA and is due to release
  • YP 4.0.18 is in QA.
  • Updates to graphing on the patch/CVE metrics page merged
  • 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, which would improve our ability to analyze CVEs, and that of many other projects (including other distros) to do so too.
  • We continue to watch the NIST NVD (CVE database) situation, the lack of CPE information is problematic for us and we are considering what alternatives we have. The CVE Project announced support for more information fields on CVEs which is a good start.
  • Some CVE information is being provided for issues in meta-openembedded, this has been provided with help from the Sovereign Tech Fund.
  • The project is sponsoring Syslinbit to separate out our CVE tooling from the build system into a standalone tool so that it can be used on software manifests of output at a later date.
  • There are proposals on the openembedded-architecture list to rework how do_unpack works, switching it from WORKDIR to a new variable and changing some directory layout.


Ways to contribute:


YP 5.1 Milestone Dates:

  • YP 5.1 M1 Build date 2024-05-20
  • YP 5.1 M1 Release date 2024-05-31
  • 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 3.1.33 is in QA
  • YP 4.0.18 is in QA
  • YP 4.0.18 Release date 2024-05-03
  • YP 5.0.1 Build Date 2024-05-13
  • YP 5.0.1 Release Date 2024-05-24
  • YP 4.0.19 build date 2024-06-03
  • YP 4.0.19 Release date 2024-06-14
  • YP 5.0.2 Build Date 2024-06-24
  • 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

Tracking Metrics:

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

Archives