Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(87 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 11th, 2023 ==
== Yocto Project Weekly Status March 26th, 2024 ==
Current Dev Position: YP 4.2 M4<br/>
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Next Deadline: 28th April 2023 YP 4.2 Release<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday April13h 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday March 28th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday April 11th 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday March 26th 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 rc2 is now in QA
*YP 5.0 M3 has been released.
*YP 4.0.9 is being built
*YP 4.0.17 is under review and due for release.
*Due to some concerns about crate urls, 4.2 rc1 was abandoned and rc2 built.
*Steve is taking patches for Dunfell until around April 8 in preparation for an April 15 build. This will be the last release of dunfell.
*linux-yocto is no longer excluded from CVE reporting on master, thanks to all who have helped triage the CVE list for the kernel. https://autobuilder.yocto.io/pub/non-release/patchmetrics/cve-status-master.txt
*There was a regression on beaglebone in 5.0 M3 where X11 wasn’t working but this has been fixed in master ready for the release.
*We’re happy to announce that Steve Sakoman is going to be supporting the mickledore stable series.
*A key worry now is the documentation for the release, especially given it is an LTS. There are emails on the docs list about this, help is much appreciated.
*The langdale release series will now wind down after one final point release
*For M4, we are still hoping to transition to a different public hash equivalence server before release. We have stopped taking general point release upgrades to recipes unless there is a security or other key reason to take them. *The key remaining fix needed before building is for the opkg lock issue.
*Patches should soon start flowing into master for 4.3
*The opkg lock issue is now understood but the best fix is still under discussion/ development.
*The project is looking at a funding opportunity where projects with a specific development focus may be able to be funded. Ideas coming to mind might include bringing back patchtest or toaster’s automated testing. If anyone has ideas that we’d be able to find people to work on (contract based?) within a reasonable timeframe, we’d be interested to hear the things people feel would make the biggest difference to the project.
*One set of the problematic autobuilder failures was tracked down to a queued but  unmerged bitbake patch. There are other intermittent issues which still need to be root caused, at least one failure was also due to system load issues.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We continue to watch the NIST NVD (CVE database) issue and await further information about what the future holds there (https://nvd.nist.gov/  - “You will temporarily see delays in analysis efforts during this transition”)


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: patchtest, layerindex, devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*There are bugs that are currently unassigned for YP 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
*There are bugs that are currently unassigned for YP 5.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
*We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
*We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. 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.
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. 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.
*Help us resolve CVE issues: CVE metrics  
*Help us resolve CVE issues: CVE metrics  
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''YP 4.2 Milestone Dates:'''<br/>
'''YP 5.0 Milestone Dates:'''<br/>
*YP 4.2 M4 built and in QA
*YP 5.0 M3 is released.
*YP 4.2 M4 Release date 2023/04/28
*YP 5.0 M4 build date 2024/04/01
 
*YP 5.0 M4 Release date 2024/04/30
'''YP 4.3 Milestone Dates:'''<br/>
*YP 4.2 M4 build date 2023/04/03
*YP 4.2 M4 Release date 2023/04/28
*YP 4.3 M1 build date  2023/06/05
*YP 4.3 M1 Release date 2023/06/16
*YP 4.3 M2 build date  2023/07/17
*YP 4.3 M2 Release date 2023/07/28
*YP 4.3 M3 build date  2023/08/28
*YP 4.3 M3 Release date 2023/09/08
*YP 4.3 M4 build date  2023/10/02
*YP 4.3 M4 Release date 2023/10/27


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.9 building
*YP 4.0.17 is out of QA.
*YP 4.0.9 Release date 2023/04/21
*YP 4.3.4 build date 2024/03/25
*YP 4.1.4 build date 2023/05/01
*YP 4.3.4 Release date 2024/04/05
*YP 4.1.4 Release date 2023/05/13
*YP 3.1.33 build date 2024/04/15
*YP 3.1.25 build date 2023/05/08
*YP 3.1.33 Release date 2024/04/26
*YP 3.1.25 Release date 2023/05/19
*YP 4.0.18 build date 2024/04/22
*YP 4.0.10 build date 2023/05/15
*YP 4.0.18 Release date 2024/05/03
*YP 4.0.10 Release date 2023/05/26
*YP 4.0.19 build date 2024/06/03
*YP 4.2.1 build date 2023/05/22
*YP 4.0.19 Release date 2024/06/14
*YP 4.2.1 Release date 2023/06/02
*YP 3.1.26 build date 2023/06/19
*YP 3.1.26 Release date 2023/06/30
*YP 4.0.11 build date 2023/06/26
*YP 4.0.11 Release date 2023/07/07
*YP 4.2.2 build date 2023/07/10
*YP 4.2.2 Release date 2023/07/21
*YP 3.1.27 build date 2023/07/31
*YP 3.1.27 Release date 2023/08/11
*YP 4.0.12 build date 2023/08/07
*YP 4.0.12 Release date 2023/08/18
*YP 4.2.3 build date 2023/08/28
*YP 4.2.3 Release date 2023/09/08
*YP 3.1.28 build date 2023/09/18
*YP 3.1.28 Release date 2023/09/29
*YP 4.0.13 build date 2023/09/25
*YP 4.0.13 Release date 2023/10/06
*YP 3.1.29 build date 2023/10/30
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.14 build date 2023/11/06
*YP 4.0.14 Release date 2023/11/17
*YP 4.2.4 build date 2023/11/13
*YP 4.2.4 Release date 2023/11/24
*YP 3.1.30 build date 2023/12/11
*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


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2531 (last week 2504) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2703 (last week 2706) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1200 (last week 1195)
**Total patches found: 1156 (last week 1148)
**Patches in the Pending State: 278 (23%) [last week 277 (23%)]
**Patches in the Pending State: 249 (22%) [last week 249 (22%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


Line 92: Line 55:


== Archives ==
== Archives ==
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]

Revision as of 14:43, 26 March 2024

Yocto Project Weekly Status March 26th, 2024

Current Dev Position: YP 5.0 M4 - Final Release
Next Deadline: 1st April 2024 YP 5.0 M4 build

Next Team Meetings:

Key Status/Updates:

  • YP 5.0 M3 has been released.
  • YP 4.0.17 is under review and due for release.
  • Steve is taking patches for Dunfell until around April 8 in preparation for an April 15 build. This will be the last release of dunfell.
  • There was a regression on beaglebone in 5.0 M3 where X11 wasn’t working but this has been fixed in master ready for the release.
  • A key worry now is the documentation for the release, especially given it is an LTS. There are emails on the docs list about this, help is much appreciated.
  • For M4, we are still hoping to transition to a different public hash equivalence server before release. We have stopped taking general point release upgrades to recipes unless there is a security or other key reason to take them. *The key remaining fix needed before building is for the opkg lock issue.
  • The opkg lock issue is now understood but the best fix is still under discussion/ development.
  • One set of the problematic autobuilder failures was tracked down to a queued but unmerged bitbake patch. There are other intermittent issues which still need to be root caused, at least one failure was also due to system load issues.
  • We continue to watch the NIST NVD (CVE database) issue and await further information about what the future holds there (https://nvd.nist.gov/ - “You will temporarily see delays in analysis efforts during this transition”)

Ways to contribute:

YP 5.0 Milestone Dates:

  • YP 5.0 M3 is released.
  • YP 5.0 M4 build date 2024/04/01
  • YP 5.0 M4 Release date 2024/04/30

Upcoming dot releases:

  • YP 4.0.17 is out of QA.
  • 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