Current Dev Position: YP 3.2 M1 Next Deadline: YP 3.2 M1 build date 2020/6/16
Next Team Meetings: * Bug Triage meeting Thursday June 18th at 7:30am PDT ( <https://zoom.us/j/454367603> https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday July 7th at 8am PDT ( <https://zoom.us/j/990892712> https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday June 16th at 8am PDT ( <https://zoom.us/j/990892712> https://zoom.us/j/990892712) * Twitch - See http://www.twitch.tv/letoatreidesthe2nd Key Status/Updates: * YP 3.1.1 is out from QA and had no defects raised so is likely to be released after review * YP 3.2 M1 will be built as soon as we have a clean build run of the currently queued patches. We've not seen anything else pending critical to M1. * We are struggling with maintainers for some key components of the system/infrastructure such as devtool, wic, buildhistory and patchwork/patchtest. If anyone can help in these areas please contact Richard. * There was a key fix to the gitsm fetcher which resolved autobuilder regressions, thanks Paul Barker for helping resolve that at short notice. * There were some important improvements to multiconfig this week so that multiconfig task hashes are correctly accounted for and rebuilt as well as BBMASK being handled correctly in individual multiconfigs, thanks Joshua Watt for those improvements. * The biggest concern for both LTS and master right now are the intermittent test failures that keep occurring on the infrastructure, we're struggling to get clean builds of either branch due to these issues. Instability in the upstream distros we run on (which we regularly pull for security updates) are sadly contributing to the issues, seemingly more significantly than usual. * If anyone has thoughts on attracting and recognizing project contributors and contributions, we would be interested in ideas and assistance in that area. * There remain a large number of bugs that we'd ideally like to fix in 3.2 M2 but they are "unassigned", there is nobody to work on them. If anyone has time, looking at these bugs would be a great way to help us. See: <https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enha ncements.2FBugs> https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhan cements.2FBugs YP 3.2 Milestone Dates: * YP 3.2 M1 build date 2020/6/16 * YP 3.2 M1 Release date 2020/6/26 * YP 3.2 M2 build date 2020/7/27 * YP 3.2 M2 Release date 2020/8/7 * YP 3.2 M3 build date 2020/8/31 * YP 3.2 M3 Release date 2020/9/11 * YP 3.2 M4 build date 2020/10/5 * YP 3.2 M4 Release date 2020/10/30 Planned upcoming dot releases: * YP 3.1.1 should be released shortly. * YP 3.0.4 build date 2020/8/10 * YP 3.0.4 release date 2020/8/21 * YP 3.1.2 build date 2020/9/14 * YP 3.1.2 release date 2020/9/25 Tracking Metrics: * WDD 2545 (last week 2515) ( <https://wiki.yoctoproject.org/charts/combo.html> https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1306 (last week 1301) * Patches in the Pending State: 518 (40%) [last week 517 (40%)] The Yocto Project's technical governance is through its Technical Steering Committee, more information is available at: <https://wiki.yoctoproject.org/wiki/TSC> https://wiki.yoctoproject.org/wiki/TSC The Status reports are now stored on the wiki at: <https://wiki.yoctoproject.org/wiki/Weekly_Status> 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!] Thanks, Stephen K. Jolley Yocto Project Program Manager * Cell: (208) 244-4460 * Email: sjolley.yp...@gmail.com <mailto:sjolley.yp...@gmail.com>
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#49651): https://lists.yoctoproject.org/g/yocto/message/49651 Mute This Topic: https://lists.yoctoproject.org/mt/74917455/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
