Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status January 24th, 2023 ==
== Yocto Project Weekly Status January 31st, 2023 ==
Current Dev Position: YP 4.2 M2<br/>
Current Dev Position: YP 4.2 M3<br/>
Next Deadline: 23rd January 2023 YP 4.2 M2 Build<br/>
Next Deadline: 20th February 2023 YP 4.2 M3 Build<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday January 26th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday February 2nd 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday January 24th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday January 31st 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.1.2 is due to be released and YP 3.1.22 is in QA
*YP 4.0.7 and YP 4.2 M2 are in QA
*We had a few annoying intermittent autobuilder bug fixes this week, thanks to anyone who helped fix those!
*We switched to the 6.1 kernel by default for M2. Unfortunately there are a couple of intermittent issues that seem to have crept in. One is a reproducibility issue in perf, likely with some host component causing it as it only occurs on second builds. The second appears to be an intermittent networking issue accessing a python http-server for testing dnf which appeared after the kernel version change.
*Failures on the autobuilder slowed down patch testing and merging as builds took a long time to stabilize. Thankfully we believe the most frequently occurring issues have been fixed so things should speed up again a little this week.
*We are continuing to see other intermittent failures which are limiting how quickly we can merge changes. A summary of some of the key issues was sent to the mailing list: https://lists.openembedded.org/g/openembedded-core/message/176476
*CVE levels in master are becoming worrying again, help would be appreciated to address the open issues.
*There have been changes to the way the codeparser cache in bitbake stores data which should reduce cache size, reduce the times data needs to be written out and generally help performance.
*CVE levels in master are still high but there are patches in progress for most issues as I understand it.
*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.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*YP 4.1.2 and YP 3.1.22 were released
*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!
*YP 4.2 M2 is due to build this week.
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*Stable builds have been proving hard to obtain due to varying issues over many of the submitted patches. This has limited patch flow over the last week.
*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
*We were able to merge 6.1 kernel improvements and a number of good bug fixes in other areas too.
*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.
*There has been an improvement to the configurability of patch warnings/errors and patch fuzz issues will now error and stop builds by default.
*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.
*Warning/errors over missing Upstream-Status details in non-core layers appears too controversial to enable by default but the option is now available should users wish to.
*Help us resolve CVE issues: CVE metrics
*CVE levels in master are becoming worrying again, Ross helpfully summarized the situation and submitted CPE changes for some of the issues being highlighted, thanks!
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''YP 4.2 Milestone Dates:'''<br/>
'''YP 4.2 Milestone Dates:'''<br/>

Revision as of 14:18, 31 January 2023

Yocto Project Weekly Status January 31st, 2023

Current Dev Position: YP 4.2 M3
Next Deadline: 20th February 2023 YP 4.2 M3 Build

Next Team Meetings:

Key Status/Updates:

  • YP 4.0.7 and YP 4.2 M2 are in QA
  • We switched to the 6.1 kernel by default for M2. Unfortunately there are a couple of intermittent issues that seem to have crept in. One is a reproducibility issue in perf, likely with some host component causing it as it only occurs on second builds. The second appears to be an intermittent networking issue accessing a python http-server for testing dnf which appeared after the kernel version change.
  • We are continuing to see other intermittent failures which are limiting how quickly we can merge changes. A summary of some of the key issues was sent to the mailing list: https://lists.openembedded.org/g/openembedded-core/message/176476
  • There have been changes to the way the codeparser cache in bitbake stores data which should reduce cache size, reduce the times data needs to be written out and generally help performance.
  • CVE levels in master are still high but there are patches in progress for most issues as I understand it.
  • We have a growing number of bugs in bugzilla, any help with them is appreciated.

Ways to contribute:

YP 4.2 Milestone Dates:

  • YP 4.2 M2 build date 2023/01/23
  • YP 4.2 M2 Release date 2023/02/03
  • YP 4.2 M3 build date 2023/02/20
  • YP 4.2 M3 Release date 2023/03/03
  • YP 4.2 M4 build date 2023/04/03
  • YP 4.2 M4 Release date 2023/04/28

Upcoming dot releases:

  • YP 4.1.2 is released
  • YP 3.1.22 is released
  • YP 4.0.7 build date 2023/01/30
  • YP 4.0.7 Release date 2023/02/10
  • YP 3.1.23 build date 2023/02/13
  • YP 3.1.23 Release date 2023/02/24
  • YP 4.0.8 build date 2023/02/27
  • YP 4.0.8 Release date 2023/03/10
  • YP 4.1.3 build date 2023/03/06
  • YP 4.1.3 Release date 2023/03/17
  • YP 3.1.24 build date 2023/03/20
  • YP 3.1.24 Release date 2023/03/31
  • YP 4.0.9 build date 2023/04/10
  • YP 4.0.9 Release date 2023/04/21
  • YP 4.1.4 build date 2023/05/01
  • YP 4.1.4 Release date 2023/05/13
  • YP 3.1.25 build date 2023/05/08
  • YP 3.1.25 Release date 2023/05/19
  • YP 4.0.10 build date 2023/05/15
  • YP 4.0.10 Release date 2023/05/26

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=85626"