Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 11th, 2024 ==
== Yocto Project Weekly Status June 18th, 2024 ==
Current Dev Position: YP 5.1 M2 <br/>
Current Dev Position: YP 5.1 M2 <br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<br/>
Line 9: Line 9:


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.19 has been through QA and is due for release
* Both YP 4.0.19 and YP 5.1 M1 have been through QA and will be released shortly
*YP 5.1 M1 rc2 is in QA
* Patch status tags are now checked for my default. Layers which don't wish this can disable it.
*RFC patches for the CVE tooling changes have been posted, help in review is appreciated
* Fedora 40 support should be almost complete. GCC 14 is the gift that keep on giving, the last issue I'm aware of is in 'expect' and there are now two competing patches for that.
*There are SPDX 3.0 patches ready for review on the mailing list
* Some larger patches are on the list and help reviewing these would be appreciated:
*There are patches proposing that missing patch Upstream-Status entries be a fatal QA error, this is likely to merge soon as there have been no objections to it.
** SPDX 3.0 from Joshua
*We have a fix for the final Fedora 40 issue, thanks Victor.
** CVE tooling from Marta
*We appreciate everyone fixing layers to work with master after recent changes, the autobuilder health is looking greener, thanks!
** bitbake-setup and configuration fragments from Alexander
*The copy_unihashes function was dropped from bitbake after the locked signature file improvements which simplifies further tooling work
* We had some fixes for the install-buildtools script which showed up a lack of automated testing for it. Adding some would be an interesting first contribution if anyone is interested.
*There is discussion on openembedded-architecture about the details around  configuration fragment tooling potentially being integrated into bitbake
*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
*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.
*Please consider signing this to show support for those changes. Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
*Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
*Through post release upgrading our patch count reduced again and is now the lowest level since July 2008!


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>

Revision as of 12:52, 18 June 2024

Yocto Project Weekly Status June 18th, 2024

Current Dev Position: YP 5.1 M2
Next Deadline: YP 5.1 M2 Build 8 July 2024

Next Team Meetings:

Key Status/Updates:

  • Both YP 4.0.19 and YP 5.1 M1 have been through QA and will be released shortly
  • Patch status tags are now checked for my default. Layers which don't wish this can disable it.
  • Fedora 40 support should be almost complete. GCC 14 is the gift that keep on giving, the last issue I'm aware of is in 'expect' and there are now two competing patches for that.
  • Some larger patches are on the list and help reviewing these would be appreciated:
    • SPDX 3.0 from Joshua
    • CVE tooling from Marta
    • bitbake-setup and configuration fragments from Alexander
  • We had some fixes for the install-buildtools script which showed up a lack of automated testing for it. Adding some would be an interesting first contribution if anyone is interested.
  • 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. Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.

Ways to contribute:

Tracking Metrics:

YP 5.1 Milestone Dates:

  • YP 5.1 M1 is in QA
  • 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 4.0.19 is ready for release.
  • 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

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

Archives