Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(37 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status November 21st, 2023 ==
== Yocto Project Weekly Status April 23rd, 2024 ==
Current Dev Position: YP 5.0 M1<br/>
Current Dev Position: YP 5.0 in QA <br/>
Next Deadline: 4th December 2023 YP 5.0 M1 build<br/>
Next Deadline: YP 5.0 Release by 30 April 2024<br/>
 


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday November 23, 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday April 25th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday November 21st at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday April 23rd 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
<br/>
 
'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.14 and YP 3.1.29 were released
*YP 5.0 rc4 is in QA.
*YP 4.2.4  has passed QA and under discussion pending release
*YP 3.1.33, The final dunfell build will follow 5.0 into QA.
*Toaster news:
*YP 4.0.18 is behind 3.1.33 for QA.
**Testing for toaster is now starting to be enabled on the autobuilder although not all tests are currently passing and there are host specific issues.  
*YP 5.0 rc2 was abandoned after issues with git in buildtools were found caused by a curl regression. 5.0 rc3 had further buildtools issues from configuration problems. 5.0 rc4 was built cleanly and went into QA to replace rc2.
**The ability to view existing builds is being extended to allow debugging use of toaster even if the original build didn’t use it
*The master branch has diverged from scarthgap and we’re trying to keep up to date with incoming patches there.
*In support of the above, BB_DEFAULT_EVENTLOG is being proposed as enabled by default in bitbake.conf so that an event log is stored for all builds. This could be useful for debugging outside of toaster in other tools too. There is a small performance/disk footprint overhead but this should be offset by the useful debug data.
*There are also patches under review for the patch/cve metrics page to improve the usability as well as build performance graphing improvements.
*The length of builds (world and oe-selftest) continues to be a concern.
*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
*When running the first nanbield stable series builds, our LTS maintainer remarked on being unable to get successful green builds. We did make significant improvements on the intermittent issues prior to release but clearly not enough unfortunately. Troubling issues include:
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.
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15005 - parsing failure on ubuntu2004/debian11 systems, maybe python/pthreads related with host python
*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.
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15166 - debuginfod issues (Ross has some debugging improvements pending)
*Some CVE information is being provided for issues in meta-openembedded, this has been provided with help from the Sovereign Tech Fund.
**Devtool “initial_rev” race issue, an example failure: https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/6082/steps/14/logs/stdio
*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.  
**several intermittent pstest issues
*There have been several fixes for meta-openembedded reproducibility issues and fixes for mirroring/CVE reporting on stable release branches, thanks Yoann.
 
 
<br/>


'''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.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.3_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.
*Help us resolve CVE issues: CVE metrics  
*Help us resolve CVE issues: CVE metrics  
*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 5.0 Milestone Dates:'''<br/>
'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 M1 build date 2023/12/04
*YP 5.0 is in QA
*YP 5.0 M1 Release date 2023/12/15
*YP 5.0 M2 build date  2024/01/15
*YP 5.0 M2 Release date 2024/01/24
*YP 5.0 M3 build date  2024/02/19
*YP 5.0 M3 Release date 2024/03/01
*YP 5.0 M4 build date  2024/04/01
*YP 5.0 M4 Release date 2024/04/30
*YP 5.0 M4 Release date 2024/04/30


'''YP 5.1 Milestone Dates:'''<br/>
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.29 build date 2023/10/30
*YP 3.1.33 is in QA
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.18 is in QA
*YP 4.0.14 build date 2023/11/06
*YP 4.0.18 Release date 2024-05-03
*YP 4.0.14 Release date 2023/11/17
*YP 5.0.1 Build Date 2024-05-13
*YP 4.2.4 build date 2023/11/13
*YP 5.0.1 Release Date 2024-05-24
*YP 4.2.4 Release date 2023/11/24
*YP 4.0.19 build date 2024-06-03
*YP 4.3.1 build date 2023/11/27
*YP 4.0.19 Release date 2024-06-14
*YP 4.3.1 Release date 2023/12/08
*YP 5.0.2 Build Date 2024-06-24
*YP 3.1.30 build date 2023/12/11
*YP 5.0.2 Release Date 2024-07-05
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.20 Build Date 2024-07-15
*YP 4.0.15 build date 2023/12/18
*YP 4.0.20 Release Date 2024-07-26
*YP 4.0.15 Release date 2023/12/29
*YP 5.0.3 Build Date 2024-08-12
*YP 4.3.2 build date 2024/01/08
*YP 5.0.3 Release Date 2024-08-23
*YP 4.3.2 Release date 2024/01/19
*YP 4.0.21 Build Date 2024-09-09
*YP 3.1.31 build date 2024/01/22
*YP 4.0.21 Release Date 2024-09-20
*YP 3.1.31 Release date 2024/02/02
*YP 5.0.4 Build Date 2024-09-23
*YP 4.0.16 build date 2024/01/29
*YP 5.0.4 Release Date 2024-10-04
*YP 4.0.16 Release date 2024/02/09
*YP 4.0.22 Build Date 2024-10-14
*YP 4.3.3 build date 2024/02/12
*YP 4.0.22 Release Date 2024-10-25
*YP 4.3.3 Release date 2024/02/23
*YP 5.0.5 Build Date 2024-11-11
*YP 3.1.32 build date 2024/03/04
*YP 5.0.5 Release Date 2024-11-22
*YP 3.1.32 Release date 2024/03/15
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.17 build date 2024/03/11
*YP 4.0.23 Release Date 2024-11-29
*YP 4.0.17 Release date 2024/03/22
*YP 4.3.4 build date 2024/03/25
*YP 4.3.4 Release date 2024/04/05
*YP 3.1.33 build date 2024/04/15
*YP 3.1.33 Release date 2024/04/26
*YP 4.0.18 build date 2024/04/22
*YP 4.0.18 Release date 2024/05/03
*YP 4.0.19 build date 2024/06/03
*YP 4.0.19 Release date 2024/06/14
 


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2517 (last week 2533) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2714 (last week 2719) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1177 (last week 1177)
**Total patches found: 1140 (last week 1173)
**Patches in the Pending State: 253 (21%) [last week 253 (21%)]
**Patches in the Pending State: 249 (21%) [last week 249 (21%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''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 96: Line 80:


== 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]]

Revision as of 14:49, 23 April 2024

Yocto Project Weekly Status April 23rd, 2024

Current Dev Position: YP 5.0 in QA
Next Deadline: YP 5.0 Release by 30 April 2024

Next Team Meetings:

Key Status/Updates:

  • YP 5.0 rc4 is in QA.
  • YP 3.1.33, The final dunfell build will follow 5.0 into QA.
  • YP 4.0.18 is behind 3.1.33 for QA.
  • YP 5.0 rc2 was abandoned after issues with git in buildtools were found caused by a curl regression. 5.0 rc3 had further buildtools issues from configuration problems. 5.0 rc4 was built cleanly and went into QA to replace rc2.
  • The master branch has diverged from scarthgap and we’re trying to keep up to date with incoming patches there.
  • There are also patches under review for the patch/cve metrics page to improve the usability as well as build performance graphing improvements.
  • 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.
  • 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.

Ways to contribute:

YP 5.0 Milestone Dates:

  • YP 5.0 is in QA
  • YP 5.0 M4 Release date 2024/04/30

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

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