Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status December 12th, 2023 ==
== Yocto Project Weekly Status December 19th, 2023 ==
Current Dev Position: YP 5.0 M1<br/>
Current Dev Position: YP 5.0 M1<br/>
Next Deadline: 4th December 2023 YP 5.0 M1 build<br/>
Next Deadline: 15th January 2024 YP 5.0 M2 build<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday December 14th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday December 21st at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday December 12th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday December 19th 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.2.4 and YP 4.3.1 were released
*YP 3.1.30 is due to be released
*YP 4.3.1 carries a release note about the intermittent failures that are causing problems for the builds, we’re lacking capacity to address several of them.
*YP 4.0.15 and YP 5.0 M1 rc3 are in QA
*YP 3.1.30 rc2 is in QA
*The intermittent issues on the autobuilder continue to cause problems and along with issues in the regression reports, these lead to several rebuilds of M1.
*The YP 5.0 M1 build is still pending, we’re hoping for several intermittent issue fixes first
*The intermittent issues are slowing down patch testing and merging. We simply don't have enough people to fix the issues quickly enough and the people we do have are struggling. This is now slowing down stable releases too.
*The intermittent issues on the autobuilder are causing problems for master branch development and stable releases and this is slowing down patch testing and merging. We simply don't have enough people to fix the issues quickly enough and the people we do have are struggling. This is now slowly down point release approvals too as a knock on effect.
*We have realized there are problems with the serial port code in qemu which may be resulting in some hangs or other issues. We will likely end up removing the “dumper” code (target command and monitor) to improve performance and reduce the side effects that code is currently causing.
*We plan to disable the rust selftest code in the hope this allows us to upgrade the version since we’re rapidly falling behind. The upgrades also break zvariant and the limited reproducibility testing we had working unfortunately.
*Python3-maturin support merged, thanks Tim.
*Several important fixes for useradd functionality have merged.
*Rust updated to 1.71.1 but further updates are blocked on reproducibility issues.
*Patches for python-maturin support have been proposed but there are challenges with reproducibility currently hindering merging.
*Two small changes to dependencies for strace and util-linux were identified which should make a big difference to unlocking dependency chains and improving build performance, thanks Yoann. Small changes like these can make a big difference to performance overall.
*An issue in configuration in one of the selftests was identified which was preventing sstate reuse. Fixing this should improve build times by removing the need to build those separate artifacts.
*Regarding bugs, even if you can’t fix a bug, submitting a failing test case that can reproduce the issue significantly improves the chances it might get fixed.
*Regarding bugs, even if you can’t fix a bug, submitting a failing test case that can reproduce the issue significantly improves the chances it might get fixed.
*There will be no project public meetings on 26th, 28th December and 2nd January.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 29: Line 31:


'''YP 5.0 Milestone Dates:'''<br/>
'''YP 5.0 Milestone Dates:'''<br/>
*YP 5.0 M1 build date 2023/12/04
*YP 5.0 M1 is in QA.
*YP 5.0 M1 Release date 2023/12/15
*YP 5.0 M2 build date  2024/01/15
*YP 5.0 M2 build date  2024/01/15
*YP 5.0 M2 Release date 2024/01/24
*YP 5.0 M2 Release date 2024/01/24
Line 39: Line 40:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.2.4 is released.
*YP 3.1.30 is ready for release.
*YP 4.3.1 is released.
*YP 4.0.15 is in QA.
*YP 3.1.30 is in QA.
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29
*YP 4.3.2 build date 2024/01/08
*YP 4.3.2 build date 2024/01/08
*YP 4.3.2 Release date 2024/01/19
*YP 4.3.2 Release date 2024/01/19

Revision as of 15:51, 19 December 2023

Yocto Project Weekly Status December 19th, 2023

Current Dev Position: YP 5.0 M1
Next Deadline: 15th January 2024 YP 5.0 M2 build

Next Team Meetings:

Key Status/Updates:

  • YP 3.1.30 is due to be released
  • YP 4.0.15 and YP 5.0 M1 rc3 are in QA
  • The intermittent issues on the autobuilder continue to cause problems and along with issues in the regression reports, these lead to several rebuilds of M1.
  • The intermittent issues are slowing down patch testing and merging. We simply don't have enough people to fix the issues quickly enough and the people we do have are struggling. This is now slowing down stable releases too.
  • We have realized there are problems with the serial port code in qemu which may be resulting in some hangs or other issues. We will likely end up removing the “dumper” code (target command and monitor) to improve performance and reduce the side effects that code is currently causing.
  • Python3-maturin support merged, thanks Tim.
  • Rust updated to 1.71.1 but further updates are blocked on reproducibility issues.
  • Two small changes to dependencies for strace and util-linux were identified which should make a big difference to unlocking dependency chains and improving build performance, thanks Yoann. Small changes like these can make a big difference to performance overall.
  • An issue in configuration in one of the selftests was identified which was preventing sstate reuse. Fixing this should improve build times by removing the need to build those separate artifacts.
  • Regarding bugs, even if you can’t fix a bug, submitting a failing test case that can reproduce the issue significantly improves the chances it might get fixed.
  • There will be no project public meetings on 26th, 28th December and 2nd January.

Ways to contribute:

YP 5.0 Milestone Dates:

  • YP 5.0 M1 is in QA.
  • YP 5.0 M2 build date 2024/01/15
  • YP 5.0 M2 Release date 2024/01/24
  • YP 5.0 M3 build date 2024/02/19
  • YP 5.0 M3 Release date 2024/03/01
  • YP 5.0 M4 build date 2024/04/01
  • YP 5.0 M4 Release date 2024/04/30

Upcoming dot releases:

  • YP 3.1.30 is ready for release.
  • YP 4.0.15 is in QA.
  • YP 4.3.2 build date 2024/01/08
  • YP 4.3.2 Release date 2024/01/19
  • YP 3.1.31 build date 2024/01/22
  • YP 3.1.31 Release date 2024/02/02
  • YP 4.0.16 build date 2024/01/29
  • YP 4.0.16 Release date 2024/02/09
  • YP 4.3.3 build date 2024/02/12
  • YP 4.3.3 Release date 2024/02/23
  • YP 3.1.32 build date 2024/03/04
  • YP 3.1.32 Release date 2024/03/15
  • YP 4.0.17 build date 2024/03/11
  • YP 4.0.17 Release date 2024/03/22
  • 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