Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 13: Line 13:
*We are keeping roughly up to date with version upgrades, thanks to those working on that.
*We are keeping roughly up to date with version upgrades, thanks to those working on that.
*We renamed the create-spdx class to include a version in the name as it became clear the output is specific to that version of SPDX and will need changes for 3.0.
*We renamed the create-spdx class to include a version in the name as it became clear the output is specific to that version of SPDX and will need changes for 3.0.
oe-selftest is now working much better on arm hosts (thanks Ross).
*oe-selftest is now working much better on arm hosts (thanks Ross).
*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.
*We need to form a plan for handling the Y2038 issue on 32 bit platforms. There don’t appear to be easy solutions so a flag day adding to CFLAGS looks like it may be the only realistic option.
*We need to form a plan for handling the Y2038 issue on 32 bit platforms. There don’t appear to be easy solutions so a flag day adding to CFLAGS looks like it may be the only realistic option.

Revision as of 15:36, 15 November 2022

Yocto Project Weekly Status November 15th, 2022

Current Dev Position: YP 4.2 M1
Next Deadline: 5th December 2022 YP 4.2 M1 Build

Next Team Meetings:

Key Status/Updates:

  • YP 4.1.1 is in QA.
  • Patches continue to flow steadily into master.
  • We are keeping roughly up to date with version upgrades, thanks to those working on that.
  • We renamed the create-spdx class to include a version in the name as it became clear the output is specific to that version of SPDX and will need changes for 3.0.
  • oe-selftest is now working much better on arm hosts (thanks Ross).
  • We have a growing number of bugs in bugzilla, any help with them is appreciated.
  • We need to form a plan for handling the Y2038 issue on 32 bit platforms. There don’t appear to be easy solutions so a flag day adding to CFLAGS looks like it may be the only realistic option.
  • It was great to see some interesting bitbake patches/fixes.

Ways to contribute:

YP 4.2 Milestone Dates:

  • YP 4.2 M1 build date 2022/12/05
  • YP 4.2 M1 Release date 2022/12/16
  • 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.1.1 is in QA
  • YP 4.1.1 Release date 2022/11/25
  • YP 3.1.21 build date 2022/11/28
  • YP 3.1.21 Release date 2022/12/09
  • YP 4.0.6 build date 2022/12/12
  • YP 4.0.6 Release date 2022/12/23
  • 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