Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(168 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 21st, 2022 ==
== Yocto Project Weekly Status March 26th, 2024 ==
Current Dev Position: YP 4.1 M2<br/>
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Next Deadline: 11th July 2022 YP 4.1 M2 Build<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday June 30th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday March 28th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday July 5th at 8 am  PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday March 26th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday June 28th 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.0.2 is due to build this week however we want to fix one bitbake logging regression first.
*YP 5.0 M3 has been released.
*A fix has been merged for a logging regression found in bitbake where the first message to the console during parsing would be shown but subsequent ones would not.  
*YP 4.0.17 is under review and due for release.
*Fedora 36 is causing problems on the autobuilder since it drops support for the scp protocol requiring sftp on target instead to exchange files. Dropbear does not have sftp support. We need scp to perform several of our image tests.  We can add sftp to both dropbear and openssh images however that then causes dev-pkg conflicts since openssh and dropbear cannot be installed at the same time but are pulled in by openssh-dev and dropbear-dev.
*Steve is taking patches for Dunfell until around April 8 in preparation for an April 15 build. This will be the last release of dunfell.
*As such we’re proposing to change -dev package dependencies to become rrecommends instead of rdepends. This does radically change the contents of some images but in a way which is much more correct.
*There was a regression on beaglebone in 5.0 M3 where X11 wasn’t working but this has been fixed in master ready for the release.
*There is a potential follow up change to change injected symlink dependencies from rdepends to rrecommends as well, which reduces the delta  of “dev-pkg” featured images even more.
*A key worry now is the documentation for the release, especially given it is an LTS. There are emails on the docs list about this, help is much appreciated.
*There are also problems in the cve-check selftests causing other build failures.
*For M4, we are still hoping to transition to a different public hash equivalence server before release. We have stopped taking general point release upgrades to recipes unless there is a security or other key reason to take them. *The key remaining fix needed before building is for the opkg lock issue.
*Various npm fixes were merged, thanks Enrico.
*The opkg lock issue is now understood but the best fix is still under discussion/ development.
*There are problems with rust-cross-canadian, it has never worked correctly for the full set of different targets cross-canadian might be set to. Help to fix that would be much appreciated.
*One set of the problematic autobuilder failures was tracked down to a queued but  unmerged bitbake patch. There are other intermittent issues which still need to be root caused, at least one failure was also due to system load issues.
*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
*We continue to watch the NIST NVD (CVE database) issue and await further information about what the future holds there (https://nvd.nist.gov/ - “You will temporarily see delays in analysis efforts during this transition”)


'''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: 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.1 See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.1_Unassigned_Enhancements.2FBugs
*There are bugs that are currently unassigned for YP 5.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_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 us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
*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.


'''YP 4.1 Milestone Dates:'''<br/>
'''YP 5.0 Milestone Dates:'''<br/>
*YP 4.1 M2 build date 2022/07/11
*YP 5.0 M3 is released.
*YP 4.1 M2 Release date 2022/07/22
*YP 5.0 M4 build date 2024/04/01
*YP 4.1 M3 build date 2022/08/22
*YP 5.0 M4 Release date 2024/04/30
*YP 4.1 M3 Release date 2022/09/02
*YP 4.1 M4 build date 2022/10/03
*YP 4.1 M4 Release date 2022/10/28


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.2 build date 2022/06/27
*YP 4.0.17 is out of QA.
*YP 4.0.2 Release date 2022/07/08
*YP 4.3.4 build date 2024/03/25
*YP 3.1.18 build date 2022/07/18
*YP 4.3.4 Release date 2024/04/05
*YP 3.1.18 Release date 2022/07/29
*YP 3.1.33 build date 2024/04/15
*YP 4.0.3 build date 2022/08/08
*YP 3.1.33 Release date 2024/04/26
*YP 4.0.3 Release date 2022/08/19
*YP 4.0.18 build date 2024/04/22
*YP 3.1.19 build date 2022/08/29
*YP 4.0.18 Release date 2024/05/03
*YP 3.1.19 Release date 2022/09/09
*YP 4.0.19 build date 2024/06/03
*YP 4.0.4 build date 2022/09/19
*YP 4.0.19 Release date 2024/06/14
*YP 4.0.4 Release date 2022/09/30
*YP 3.1.20 build date 2022/10/10
*YP 3.1.20 Release date 2022/10/21
*YP 4.0.5 build date 2022/10/31
*YP 4.0.5 Release date 2022/11/11


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2400 (last week 2430) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2703 (last week 2706) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1151 (last week 1160)
**Total patches found: 1156 (last week 1148)
**Patches in the Pending State: 326 (28%) [last week 326 (28%)]
**Patches in the Pending State: 249 (22%) [last week 249 (22%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


Line 61: Line 55:


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

Revision as of 14:43, 26 March 2024

Yocto Project Weekly Status March 26th, 2024

Current Dev Position: YP 5.0 M4 - Final Release
Next Deadline: 1st April 2024 YP 5.0 M4 build

Next Team Meetings:

Key Status/Updates:

  • YP 5.0 M3 has been released.
  • YP 4.0.17 is under review and due for release.
  • Steve is taking patches for Dunfell until around April 8 in preparation for an April 15 build. This will be the last release of dunfell.
  • There was a regression on beaglebone in 5.0 M3 where X11 wasn’t working but this has been fixed in master ready for the release.
  • A key worry now is the documentation for the release, especially given it is an LTS. There are emails on the docs list about this, help is much appreciated.
  • For M4, we are still hoping to transition to a different public hash equivalence server before release. We have stopped taking general point release upgrades to recipes unless there is a security or other key reason to take them. *The key remaining fix needed before building is for the opkg lock issue.
  • The opkg lock issue is now understood but the best fix is still under discussion/ development.
  • One set of the problematic autobuilder failures was tracked down to a queued but unmerged bitbake patch. There are other intermittent issues which still need to be root caused, at least one failure was also due to system load issues.
  • We continue to watch the NIST NVD (CVE database) issue and await further information about what the future holds there (https://nvd.nist.gov/ - “You will temporarily see delays in analysis efforts during this transition”)

Ways to contribute:

YP 5.0 Milestone Dates:

  • YP 5.0 M3 is released.
  • YP 5.0 M4 build date 2024/04/01
  • YP 5.0 M4 Release date 2024/04/30

Upcoming dot releases:

  • YP 4.0.17 is out of QA.
  • 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:

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

Archives