Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 9: Line 9:


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.3 has been through QA with a clean report and is likely to be released
*YP 4.0.3 was released
*The CVE count for master rose sharply this week but a number of fixes were sent by Khem, thanks!
*YP 3.1.19 has been built and is in QA
*Bitbake changes in class handling merged which means classes can now be enforced to be in “global” or “recipe” scope. This handles a long standing usability issue of it not being clear which scope classes should be used in. For example, “testimage” now needs to be included via IMAGE_CLASSES and not via INHERIT. Global class inclusions in recipes such as “base” and “package” will now show a parsing error. “base” was particularly pointless and can simply be removed as it was always inherited.
*We are now at feature freeze for 4.1.
*The rust toolchain changes merged and are now being tested by default on the autobuilder but there is one intermittent issue with shebang length overflow in the SDK which still needs to be resolved
*The 4.1 build is planned as soon as we resolve the status of some pending patches. The known remaining issues are the rust automated tests, layer setup changes and gcc and rust version upgrades. We also need to fix some autobuilder errors such as the llvm reproducibility issue with mesa.
*We upgraded glibc to 2.36 and produced a new uninative version which supports this.
*Several patch series have been problematic in the last week which has put strain on our infrastructure, particularly the binutils upgrade.
*There are patches out for review for the debug path improvements. These rely on a gcc patch and small change of gcc behavior which is being discussed with upstream.
*The CVE count for master rose sharply again this week due to multiple issues in vim and tiff. The vim issues have been patched, tiff hasn’t as yet.
*There were cleanups to copyright and license headers in OE-Core and Bitbake.
*We have seen a sharp rise in the number of patches in OE-Core, particularly related to changes in new clang versions. Many of these have been submitted upstream and/or have good reasons for being present but we need to continue to work to reduce our patch burden.
*“largefile” support in oe-core was cleaned up and removed as we assume this everywhere now, completing something we said would happen in release notes a few years ago.
*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


Revision as of 14:42, 23 August 2022

Yocto Project Weekly Status August 23rd, 2022

Current Dev Position: YP 4.1 M3 (Feature Freeze)
Next Deadline: 22nd August 2022 YP 4.1 M3 Build

Next Team Meetings:

Key Status/Updates:

  • YP 4.0.3 was released
  • YP 3.1.19 has been built and is in QA
  • We are now at feature freeze for 4.1.
  • The 4.1 build is planned as soon as we resolve the status of some pending patches. The known remaining issues are the rust automated tests, layer setup changes and gcc and rust version upgrades. We also need to fix some autobuilder errors such as the llvm reproducibility issue with mesa.
  • Several patch series have been problematic in the last week which has put strain on our infrastructure, particularly the binutils upgrade.
  • The CVE count for master rose sharply again this week due to multiple issues in vim and tiff. The vim issues have been patched, tiff hasn’t as yet.
  • We have seen a sharp rise in the number of patches in OE-Core, particularly related to changes in new clang versions. Many of these have been submitted upstream and/or have good reasons for being present but we need to continue to work to reduce our patch burden.
  • 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

Ways to contribute:

YP 4.1 Milestone Dates:

  • YP 4.1 M3 build date 2022/08/22
  • 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:

  • YP 4.0.3 is released
  • YP 3.1.19 is in QA
  • YP 3.1.19 Release date 2022/09/09
  • YP 4.0.4 build date 2022/09/19
  • 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:

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