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.2 M1 is due to be built this week, likely once we merge a few remaining patches and hopefully some CVE fixes.
*YP 4.2 M1 and YP 4.0.6 passed QA and are due for release.
*Thanks to everyone who attended or helped contribute to the Yocto Summit, it seemed to be a success and had some good presentations!
*Builds on the autobuilder are problematic at present due to connection losses with the controller machine. We understand the cause and will be migrating the controller to a new server/location to address this.
*There are a number of bitbake patches pending with an unresolved dilemma on functionality versus parsing speeds.
*That, combined with OOM issues from recent bitbake cache changes meant patches are merging more slowly this week.
*CVEs in master have risen with 7 across 5 components, help in bringing the numbers down would be appreciated
*There are a number of bitbake patches pending which are a bit more invasive than usual. These are aiming to address:
*We are starting to see some rough plans around Y2038, largefile support and some other topics, thanks to all those helping move this forward, there has been some useful discussion and we look forward to seeing the changes!
**memory issues seen with the recent cache changes and bitbake -S
**UI hangs where the bitbake server has crashed/hung or otherwise failed
**issues where bitbake may have removed another server instances bitbake.sock network socket file
**console interaction issues where bitbake may not respond to Ctrl+C
**event handler race issues around datastore accesses
*The OE TSC decided in favour of adding export flag expansion despite the performance impact so that patch will be queued.
*CVE levels in master are concerning again
*With some debugging, the bitbake.sock disappearance was potentially identified and also issues with OOM process killing locking up bitbake’s server and UI were studied.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*There will be no status report next week, the next will be 3rd January 2023.


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

Revision as of 15:48, 20 December 2022

Yocto Project Weekly Status December 20th, 2022

Current Dev Position: YP 4.2 M2
Next Deadline: 23th January 2023 YP 4.2 M2 Build

Next Team Meetings:

Key Status/Updates:

  • YP 4.2 M1 and YP 4.0.6 passed QA and are due for release.
  • Builds on the autobuilder are problematic at present due to connection losses with the controller machine. We understand the cause and will be migrating the controller to a new server/location to address this.
  • That, combined with OOM issues from recent bitbake cache changes meant patches are merging more slowly this week.
  • There are a number of bitbake patches pending which are a bit more invasive than usual. These are aiming to address:
    • memory issues seen with the recent cache changes and bitbake -S
    • UI hangs where the bitbake server has crashed/hung or otherwise failed
    • issues where bitbake may have removed another server instances bitbake.sock network socket file
    • console interaction issues where bitbake may not respond to Ctrl+C
    • event handler race issues around datastore accesses
  • The OE TSC decided in favour of adding export flag expansion despite the performance impact so that patch will be queued.
  • CVE levels in master are concerning again
  • With some debugging, the bitbake.sock disappearance was potentially identified and also issues with OOM process killing locking up bitbake’s server and UI were studied.
  • We have a growing number of bugs in bugzilla, any help with them is appreciated.
  • There will be no status report next week, the next will be 3rd January 2023.

Ways to contribute:

YP 4.2 Milestone Dates:

  • YP 4.2 M1 is ready for released
  • YP 4.2 M2 build date 2023/01/23
  • YP 4.2 M2 Release date 2023/02/03
  • YP 4.2 M3 build date 2023/02/20
  • YP 4.2 M3 Release date 2023/03/03
  • YP 4.2 M4 build date 2023/04/03
  • YP 4.2 M4 Release date 2023/04/28

Upcoming dot releases:

  • YP 4.0.6 is out of QA
  • YP 4.1.2 build date 2023/01/09
  • YP 4.1.2 Release date 2023/01/20
  • YP 3.1.22 build date 2023/01/16
  • YP 3.1.22 Release date 2023/01/27
  • YP 4.0.7 build date 2023/01/30
  • YP 4.0.7 Release date 2023/02/10
  • YP 3.1.23 build date 2023/02/13
  • YP 3.1.23 Release date 2023/02/24
  • YP 4.0.8 build date 2023/02/27
  • YP 4.0.8 Release date 2023/03/10
  • YP 4.1.3 build date 2023/03/06
  • YP 4.1.3 Release date 2023/03/17
  • YP 3.1.24 build date 2023/03/20
  • YP 3.1.24 Release date 2023/03/31
  • YP 4.0.9 build date 2023/04/10
  • YP 4.0.9 Release date 2023/04/21
  • YP 4.1.4 build date 2023/05/01
  • YP 4.1.4 Release date 2023/05/13
  • YP 3.1.25 build date 2023/05/08
  • YP 3.1.25 Release date 2023/05/19
  • YP 4.0.10 build date 2023/05/15
  • YP 4.0.10 Release date 2023/05/26

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