Weekly Status: Difference between revisions

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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.5 M3 has been released.
*YP 3.1.15 is due to be released
*YP 3.1.15 is now in QA
*YP 3.4.3 is due to build
*There are patches proposed to move python3-cryptography to OE-Core from meta-oe/meta-python. It is late in the cycle but the current location is causing issues for several layers and it appears to be the right thing to do before kirkstone is released.
*We decided to merge in a number of python recipes which allow us to build the sphinx documentation. These are used by our documentation build process and many of the dependencies were things which likely should have been in core anyway.
*There is a proposal to switch from pip to installer to handle installation of python modules. With some development, the path becomes clear in hindsight and this is another change where it seems to make sense to do it now.
*There was a small performance tweak to bitbake’s codeparser cache code which seems to show around a 10% parsing speed improvement
*Other than the above, we should be seeing the recent python changes settling down.
*We have continued to take other minimal impact upgrades and this is having a positive impact on CVE numbers. We are looking likely to take the recently released libtool 2.4.7 since this is similar to 2.4.6 but keeps us current with upstream. Some recipes may need to clear out stale libtool m4 macros if version mismatch errors are seen.
*There were some tweaks to the tasks display in knotty merged.
*Toaster has seen further fixes and should be ready for release.
*We took an upgrade to mesa 22 which drops dri1 support on the basis it stands the release in a better long term position.
*The AVAILABLE_LICENSES variable was removed since it has parsing overhead, had bad implications for task hashes and is no longer needed by any of the core code.
*We have continued to take other minimal impact upgrades and this is having a positive impact on CVE numbers.
*Some changes are being proposed to the documentation build process which should make version handling in releases easier and less error prone.
*Toaster has seen a number of fixes recently and should be in a stronger position for release with a move to an LTS django version, thanks Tim and David.
*Help in completing the migration documentation would be much appreciated.
*If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
*If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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
*Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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:46, 22 March 2022

Yocto Project Weekly Status Mar. 22nd, 2022

Current Dev Position: YP 3.5 M4
Next Deadline: 4th Apr. 2022 YP 3.5 M4 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.1.15 is due to be released
  • YP 3.4.3 is due to build
  • We decided to merge in a number of python recipes which allow us to build the sphinx documentation. These are used by our documentation build process and many of the dependencies were things which likely should have been in core anyway.
  • There was a small performance tweak to bitbake’s codeparser cache code which seems to show around a 10% parsing speed improvement
  • We have continued to take other minimal impact upgrades and this is having a positive impact on CVE numbers. We are looking likely to take the recently released libtool 2.4.7 since this is similar to 2.4.6 but keeps us current with upstream. Some recipes may need to clear out stale libtool m4 macros if version mismatch errors are seen.
  • Toaster has seen further fixes and should be ready for release.
  • The AVAILABLE_LICENSES variable was removed since it has parsing overhead, had bad implications for task hashes and is no longer needed by any of the core code.
  • Some changes are being proposed to the documentation build process which should make version handling in releases easier and less error prone.
  • If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
  • Intermittent issues continue to be at record high levels and help is very much welcome in trying to resolve them. 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 3.5 Milestone Dates:

  • YP 3.5 M4 build date 2022/04/04
  • YP 3.5 M4 Release date 2022/04/29

Upcoming dot releases:

  • YP 3.1.15 is near release.
  • YP 3.4.3 build date 2022/03/21
  • YP 3.4.3 Release date 2022/04/01
  • YP 3.3.6 build date 2022/03/28
  • YP 3.3.6 Release date 2022/04/08
  • YP 3.1.16 build date 2022/04/25
  • YP 3.1.16 Release date 2022/05/06

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