Yocto Project Status WW16`22
Richard Purdie
Current Dev Position: YP 4.0 rc3
Next Deadline: 29th April 2022 YP 4.0 final release
Next Team Meetings:
- Bug Triage meeting Thursday Apr.21st 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
- Monthly Project Meeting Tuesday May 3rd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
- Weekly Engineering Sync Tuesday Apr. 19th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
- Twitch - See https://www.twitch.tv/theyoctojester
Key Status/Updates:
- The next release, kirkstone will be 4.0 (previously known as 3.5) and will be bitbake 2.0 based.
- The third release candidate build for YP 4.0 (3.5) is now in QA.
- rc1 had several issues such as edgerouter not booting, a uninative gcc 12 issue and broken icons in sato that made it inappropriate for release. rc2 triggered a number of autobuilder intermittent issues, there were tweaks to some of the rc1 fixes needed, several CVEs and a systemd/bluetooth issue that resulted in an rc3.
- YP 3.3.6, the final hardknott release will build after 4.0.
- YP 4.1 planning document is available for review at: https://docs.google.com/document/d/1-g7DatSdmIETwD3xFSCxV7MbWVVkpQvQ788mIr1MPTI/edit?usp=sharing
- If people see intermittent issues in their own builds, particularly if they’re the same as intermittent issues seen on the autobuilder, please do comment in the bugs mentioning when they happen as the frequency information does help us prioritize fixing the most common issues.
- Intermittent issues continue to be at high levels and help is very much welcome in trying to resolve them. 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
Ways to contribute:
- 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 3.5. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhancements.2FBugs
- 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.
YP 4.0 Milestone Dates:
- YP 4.0 is in QA
- YP 4.0 Release date 2022/04/29
YP 4.1 Milestone Dates:
- YP 4.1 M1 build date 2022/05/30
- YP 4.1 M1 Release date 2022/06/10
- YP 4.1 M2 build date 2022/07/11
- YP 4.1 M2 Release date 2022/07/22
- YP 4.1 M3 build date 2022/08/22
- YP 4.1 M3 Release date 2022/09/02
- YP 4.1 M4 build date 2022/10/03
- YP 4.1 M4 Release date 2022/10/28
Upcoming dot releases:
- YP 3.3.6 build date 2022/03/28
- YP 3.3.6 Release date 2022/04/08
- YP 3.1.16 build date 2022/04/25
- YP 3.1.16 Release date 2022/05/06
- YP 3.4.4 build date 2022/05/02
- YP 3.4.4 Release date 2022/05/13
- YP 4.0.1 build date 2022/05/16
- YP 4.0.1 Release date 2022/05/27
- YP 3.1.17 build date 2022/06/06
- YP 3.1.17 Release date 2022/06/17
- YP 4.0.2 build date 2022/06/27
- YP 4.0.2 Release date 2022/07/08
- YP 3.1.18 build date 2022/07/18
- YP 3.1.18 Release date 2022/07/29
- YP 4.0.3 build date 2022/08/08
- YP 4.0.3 Release date 2022/08/19
- YP 3.1.19 build date 2022/08/29
- YP 3.1.19 Release date 2022/09/09
- YP 4.0.4 build date 2022/09/19
- YP 4.0.4 Release date 2022/09/30
- YP 3.1.20 build date 2022/10/10
- YP 3.1.20 Release date 2022/10/21
- YP 4.0.5 build date 2022/10/31
- YP 4.0.5 Release date 2022/11/11
Tracking Metrics:
- OE-Core/Poky Patch Metrics
- Total patches found: 1215 (last week 1203)
- Patches in the Pending State: 343 (28%) [last week 343 (29%)]
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Archived content:
Tip of the Week:
- The scripts in ${WORKDIR}/temp/run.XXX for shell tasks can be quickly hacked and used for standalone debugging by replacing the function call at the end with “bash -i” which will then drop you into a shell environment matching the task being debugged (minus the fakeroot context).
- Bonus marks for anyone sending a patch to add the fakeroot context as comments at the start of the scripts.
- (send any tips you’d like to see here to Stephen or Richard)