Weekly Status
From Yocto Project
Jump to navigationJump to search
Yocto Project Weekly Status Feb. 15th, 2022
Current Dev Position: YP 3.5 M3
Next Deadline: 21th Feb. 2022 YP 3.5 M3 build
Next Team Meetings:
- Bug Triage meeting Thursday Feb. 17th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
- Monthly Project Meeting Tuesday Mar. 1st at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
- Weekly Engineering Sync Tuesday Feb. 15th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
- Twitch - See https://www.twitch.tv/theyoctojester
Key Status/Updates:
- Next week is feature freeze for 3.5, our next LTS release
- YP 3.1.14 passed QA and is due to be released
- YP 3.2.4 rc2 is in QA (rc1 had sstate networking issues)
- We’re extremely worried about the inclusive language changes since these are not anywhere near ready and the freeze deadline is in days. This is an important topic but sadly we’re simply starved of people with the right time and skills to spend on it. There is an email on the openembedded-architecture list about this.
- The autobuilder infrastructure is planned to be offline 26-28th February for a data center move. Public services like the website, wiki and git servers will remain live but the git backend (push.yoctoproject.org) will be offline, as will the downloads and sstate services and the autobuilder/NAS.
- We’ve upgraded to the new glibc version and have patches in testing for the new binutils release assuming some minor issues there are resolved.
- There are changes proposed to the bitbake git fetcher handling of tags. We resolve these against the upstream repositories and the caching of the values was showing issues such as network accesses in the unpack task. We advice against using tags due to the potential for them to change, any layers using them may seen error messages depending on whether their usage is problematic.
- Intermittent issues continue to be at record 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 In particular, we’re struggling to understand the intermittent network issue with external hosts we’re seeing very occasionally.
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.
- Help us resolve CVE issues: CVE metrics https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive
YP 3.5 Milestone Dates:
- YP 3.5 M3 build date 2022/02/21
- YP 3.5 M3 Release date 2022/03/04
- YP 3.5 M4 build date 2022/04/04
- YP 3.5 M4 Release date 2022/04/29
Upcoming dot releases:
- YP 3.1.14 is out of QA
- YP 3.4.2 is in QA
- YP 3.4.2 Release date 2022/02/18
- YP 3.3.5 build date 2022/02/14
- YP 3.3.5 Release date 2022/02/25
- YP 3.1.15 build date 2022/03/14
- YP 3.1.15 Release date 2022/03/25
- YP 3.4.3 build date 2022/03/21
- YP 3.4.3 Release date 2022/04/01
- 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
Tracking Metrics:
- WDD 2662 (last week 2665) (https://wiki.yoctoproject.org/charts/combo.html)
- Poky Patch Metrics
- Total patches found: 1208 (last week 1213)
- Patches in the Pending State: 334 (28%) [last week 338 (28%)]
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC
