Weekly Status
From Yocto Project
Jump to navigationJump to search
Yocto Project Weekly Status Nov. 24, 2020
Current Dev Position: YP 3.3 M1 development
Next Deadline: 7th December 2020 YP 3.3 M1 build
Next Team Meetings:
- Bug Triage meeting Thursday Nov. 26th at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
- Monthly Project Meeting Tuesday Dec. 1st at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
- Weekly Engineering Sync Tuesday Nov. 24th at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
- Twitch - See https://www.twitch.tv/theyoctojester
Key Status/Updates:
- YP 3.1.4 will build later this week.
- YP 3.3 development in master is continuing as patches are reviewed, tested and merged.
- We plan to backport the sphinx documentation transition back to our LTS after 3.1.4 is built.
- A small but important issue was identified related to build reproducibility where the host umask was influencing the build output in relatively minor ways. We plan to run a mixture of umasks on the autobuilder infrastructure in future to avoid this source of reproducibility issues. There are patches for the issues queued for master and will be backported in due course.
- Support for fedora33 has been resolved but required making pseudo-native host specific and not ‘uninative’ due to differences in the way pseudo builds depending on the presence of headers.
- Hashserve “passthrough” support has merged allowing hashservers to be chained together, thanks Joshua.
- Intermittent autobuilder issues continue to occur. 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
- Further autobuilder improvements have been submitted and accepted into upstream buildbot (field history, triggered build summary stats and work name display in build summary). As these are released and deployed, they will make small but important improvements to the autobuilder usability.
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.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_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 3.3 Milestone Dates:
- YP 3.3 M1 build date 2020/12/07
- YP 3.3 M1 Release date 2020/12/18
- YP 3.3 M2 build date 2021/01/18
- YP 3.3 M2 Release date 2021/01/29
- YP 3.3 M3 build date 2021/03/01
- YP 3.3 M3 Release date 2021/03/12
- YP 3.3 M4 build date 2021/04/05
- YP 3.3 M4 Release date 2021/04/30
Planned upcoming dot releases:
- YP 3.1.4 build date 2020/11/2
- YP 3.1.4 release date 2020/11/13
- YP 3.2.1 build date 2020/11/16
- YP 3.2.1 release date 2020/12/4
- YP 3.1.5 build date 2021/01/11
- YP 3.1.5 release date 2021/01/22
- YP 3.2.2 build date 2021/02/08
- YP 3.2.2 release date 2021/02/19
- YP 3.1.6 build date 2021/02/22
- YP 3.1.6 release date 2021/03/05
- YP 3.1.7 build date 2021/03/22
- YP 3.1.7 release date 2021/04/02
Tracking Metrics:
- WDD 2532 (last week 2534) (https://wiki.yoctoproject.org/charts/combo.html)
- Poky Patch Metrics
- Total patches found: 1279 (last week 1275)
- Patches in the Pending State: 497 (39%) [last week 497 (39%)]
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC
