From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8720CC433FE for ; Tue, 1 Feb 2022 16:07:25 +0000 (UTC) Received: from mail-pj1-f54.google.com (mail-pj1-f54.google.com [209.85.216.54]) by mx.groups.io with SMTP id smtpd.web12.50217.1643731642315848798 for ; Tue, 01 Feb 2022 08:07:22 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=p+3C5/TT; spf=pass (domain: gmail.com, ip: 209.85.216.54, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pj1-f54.google.com with SMTP id r59so17530303pjg.4 for ; Tue, 01 Feb 2022 08:07:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:subject:date:message-id:mime-version:content-language :thread-index; bh=6RrT6MP4OB5zDKCfdY3t7P6F1OzBlkuxX+dEQ/EJXbQ=; b=p+3C5/TT/S4iRbOl1Zh4rBw4N1UETK4WyyXJoDEldkCMmJ2abzjv5IusrbN9imAk49 7I+Pbet34cSoodFnv2yek8s5MeOYEhY45D+vxqMbdCfox6OoFvRk8FIK1WWCSLMrR4gg gv7i8JB23HjhrQWatv4lfz54mP6NaibuC4TVOzPMfQoxbuU33hgclW8Smc5zsgNnlf3T gheqDDxeEoxAS88IOjITL9bJ8n0kKl1EOVXB4y7FXcOl0zx9w2Pk9pBXetl9lTKD4J3v ZidIeeaeGixdw2cndmu9l41g2IIJf9Y23K+uH7w23bIIPx+PGIbGHQ5RfXKBDG2T9kGa T6ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-language:thread-index; bh=6RrT6MP4OB5zDKCfdY3t7P6F1OzBlkuxX+dEQ/EJXbQ=; b=4yA1dkT2zjXy+cP6pdGxJfmmKTRW3R2SHS5NmmULDPKzu4CXCXxT2IiIJowxeBYcJ0 NUp5bYRV/nGut3OsWzBm+HNjT2MKXurWW4WOZlMoWfDI5j11852ohg2MMrExR+okK+HR C9rKXZZ6vyLQY1M4wAy7TiD+e41uLGt3ydlJ2EiWBNUJYyjX953wsvVyARL4YuCNGuWl X9JUZ7X13BJ91R0/kurZG3HCuY9V/EONdSrfLSd4hOx+52um7OJo60O2YjKXLArp2RVV HQDabwveSYyrqdqqKQJI4sbr9OFxKPKAPj2O80Cxu5M3qkmJM7elaaAMvbshgBrkMkQy lQxg== X-Gm-Message-State: AOAM532nKLXxVkW+FN9IxgPXc3DHq4n5+9Q0QuroO8HayINvVeJRmORb mhDcnM223ogghEXY6gOOXjGyU5lyd58= X-Google-Smtp-Source: ABdhPJyUu9nmaALvV+/+0qnueCeKQoHWrPXuvkFXpS2TpocMx3+O+5ge8QeIgCEKC0jqpL8VpiIBRA== X-Received: by 2002:a17:90a:7f81:: with SMTP id m1mr3044789pjl.157.1643731641459; Tue, 01 Feb 2022 08:07:21 -0800 (PST) Received: from skjolley (125.sub-72-111-56.myvzw.com. [72.111.56.125]) by smtp.gmail.com with ESMTPSA id g12sm21701562pfm.119.2022.02.01.08.07.19 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Feb 2022 08:07:20 -0800 (PST) From: To: , Subject: Yocto Project Status WW05`22 Date: Tue, 1 Feb 2022 09:07:18 -0700 Message-ID: <0e2101d81785$caab1ad0$60015070$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0E22_01D8174B.1E4F9E30" X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AQI/fI4PyJDVq07QDllh7nzMM3sVnA== List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Tue, 01 Feb 2022 16:07:25 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/161158 This is a multipart message in MIME format. ------=_NextPart_000_0E22_01D8174B.1E4F9E30 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit 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. 3rd 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) * Monthly Project Meeting Tuesday Feb. 1st at 8 am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 ) * Weekly Engineering Sync Tuesday Feb. 8th at 8 am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 ) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * YP 3.5 M2 has passed QA with one bug highlighted (14708). Due to vacations in Asia the release, if approved, will be made next week. * YP 3.1.14 is ready for QA but the release will also be delayed until next week. * A new Patchwork is available at https://patchwork.yoctoproject.org/. This new system is running the up to date mainline code and will receive regular updates. The previous unmaintained fork remains up at https://patchwork.openembedded.org/ to preserve history. We are seeking help updating PatchTest to run with the new version. Everyone can now sign up for an account on the new system. Patchwork project maintainers please email mhalstead@linuxfoundation.org to have your access restored. * Upstream glibc are now planning to remove prelink support in 2.36. I think we will still want to remove prelink from OE-Core before our next release though, particularly as it is an LTS. * An email proposing inclusive language changes for bitbake and OE-Core has been sent to the community for review. The aim is to implement this before M3. * We are seeing networking issues during image testing on the centos8/stream8 workers, possibly due to recent changes in the distro. Help with debugging this welcome. * We have also realized there is an issue with hash equivalence where the current mechanism will not account for different headers inside the sysroot added through indirect dependencies (e.g. linux-libc-headers via glibc). This means something like rtcwake in util-linux which uses rtc.h can have differing debug symbols due to differing line numbers yet otherwise be identical. There is a potential fix with downsides in master-next. * CVE metrics are still under control for master with pending patches accounted for (thanks Ross!) but work still remains on the various stable branches which have high counts. * 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_Enhan cements.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/main tainers.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.5 Milestone Dates: * YP 3.5 M2 is out of QA * 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 built * YP 3.1.14 Release date 2022/02/04 * YP 3.4.2 build date 2022/02/07 * 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 2705 (last week 2700) ( https://wiki.yoctoproject.org/charts/combo.html) * OE-Core/Poky Patch Metrics * Total patches found: 1236 (last week 123.) * Patches in the Pending State: 342 (28%) [last week 340 (28%)] The Yocto Project's technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC 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!] Thanks, Stephen K. Jolley Yocto Project Program Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_0E22_01D8174B.1E4F9E30 Content-Type: text/html; boundary="----=_NextPart_000_0C88_01D816DA.07B45510"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.5 M3

Next Deadline: 21th = Feb. 2022 YP 3.5 M3 build

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 3.5 M2 has passed QA with = one bug highlighted (14708). Due to vacations in Asia the release, if = approved, will be made next week.
  • YP 3.1.14 is ready for QA but = the release will also be delayed until next = week.
  • A new Patchwork is available at = https://patchwork.yoctoproject.org/. = This new system is running the up to date mainline code and will receive = regular updates. The previous unmaintained fork remains up at https://patchwork.openembedded.org/ = to preserve history. We are seeking help updating PatchTest to run with = the new version.

Everyone can now = sign up for an account on the new system. Patchwork project maintainers = please email mhalstead@linuxfou= ndation.org to have your = access restored.

  • Upstream glibc are now planning = to remove prelink support in 2.36. I think we will still want to remove = prelink from OE-Core before our next release though, particularly as it = is an LTS.
  • An email proposing inclusive language = changes for bitbake and OE-Core has been sent to the = community for review. The aim is to implement this before = M3.
  • We are seeing networking issues = during image testing on the centos8/stream8 workers, possibly due to = recent changes in the distro. Help with debugging this = welcome.
  • We have also realized there is = an issue with hash equivalence where the current mechanism will not = account for different headers inside the sysroot added through indirect = dependencies (e.g. linux-libc-headers via glibc). This means something = like rtcwake in util-linux which uses rtc.h can have differing debug = symbols due to differing line numbers yet otherwise be identical. There = is a potential fix with downsides in = master-next.
  • CVE metrics are still under control = for master with pending patches accounted for (thanks Ross!) but work = still remains on the various stable branches which have high = counts.
  • 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?qui= cksearch=3DAB-INT

In particular, = we’re struggling to understand the intermittent network issue with = external hosts we’re seeing very = occasionally.

 

Ways to = contribute:

 

YP 3.5 Milestone = Dates:

  • YP 3.5 M2 is out of = QA
  • 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 = built
  • YP 3.1.14 Release date = 2022/02/04
  • YP 3.4.2 build date = 2022/02/07
  • 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:

 

The Yocto = Project’s technical governance is through its Technical Steering = Committee, more information is available at:

https://wiki.yocto= project.org/wiki/TSC

 

The Status reports = are now stored on the wiki at: https://wiki.yocto= project.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<= o:p>

Yocto = Project Program Manager

(    Cell:         = ;       (208) = 244-4460

* Email:           = ;   sjolley.yp.pm@gmail.com

 

------=_NextPart_000_0E22_01D8174B.1E4F9E30--