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 A9922C54E94 for ; Tue, 24 Jan 2023 15:49:00 +0000 (UTC) Received: from mail-pj1-f43.google.com (mail-pj1-f43.google.com [209.85.216.43]) by mx.groups.io with SMTP id smtpd.web10.18426.1674575339288144576 for ; Tue, 24 Jan 2023 07:48:59 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=FL7U8R5R; spf=pass (domain: gmail.com, ip: 209.85.216.43, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pj1-f43.google.com with SMTP id e10-20020a17090a630a00b0022bedd66e6dso2425589pjj.1 for ; Tue, 24 Jan 2023 07:48:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=thread-index:content-language:mime-version:message-id:date:subject :to:from:from:to:cc:subject:date:message-id:reply-to; bh=8RuTlZou5yWaR+YzkRg7lDYJPEYhDDShdowWh0rgX3o=; b=FL7U8R5R45AjB8j/w7SJXXmPI3pqxYT1vfnfLb/Gy6766dMlz/o7MMk7WXIPvkqQnU 00YGfDva5Bc5RATP/FNDuRqQqLEVIaEgG8imBrVVqt4+EXusWSa+YzdfNM25eqiOLiWB L4BgP2W4GPxcOtzCIMFT3Nvh6hbJH6yVrLfFCtzY4Eh9L5mps6vtV7X89cN5mekaOHtQ TVqyaO11MxCDEv4S/DgS4p82PAu9QtJXgrfOM1pzCE+eB6U7W4WgkzBNcz4IhnDefEU6 fr5sUflCI7j+6WGDrhJV/D6I27QiushHR842qk5z0tA7apntMQk/QfN4jG1Azk11k6J9 1fVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=thread-index:content-language:mime-version:message-id:date:subject :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8RuTlZou5yWaR+YzkRg7lDYJPEYhDDShdowWh0rgX3o=; b=CKvjLBybmE/2lKDhmA8mXyNXtDNlSouheH0iD4kAEZ6i6MdUm6842pjH/N+PogISag mKJoHRELe8Wb/zw3uhmfOEPbzUE4pd37TDfUBW5TQxYZUwZ7IHDtqarSevi41bLUeoBw 7goRc7Au1PuE5umbaQTImTqZmJXIiOhewTpqnCL0cQbPDBH2tRKr0Lr5FVg1nxxadhAE DwjGQHWmO4wkTncbEAX32bPhkaK1ggMxwwh1q78I71ZzzNuxkbr8VH8so589Fl01Ga7Z z1fEngSbS2Le4tjGQAE/hiSQ6vQegMCPQprfaH4rQcaW1d2+6mwvPfavij6q3mMvZNtj WJBw== X-Gm-Message-State: AFqh2krspuZnM2u6UFQELUSpaqMU8M6feipCoRp/y71clMd37gX4pet7 UyuUonmPMBWWUxfTjQSP3abvl+OM2cY= X-Google-Smtp-Source: AMrXdXvEhlrTtdnWjNVmuAHfcuAEpRudG98mo3nnpVOWa+4pltKwPfKx6lTXd3qAvNUS14QG8aoZ9A== X-Received: by 2002:a17:902:e5d2:b0:194:52ed:7a16 with SMTP id u18-20020a170902e5d200b0019452ed7a16mr36128149plf.24.1674575338094; Tue, 24 Jan 2023 07:48:58 -0800 (PST) Received: from skjolley ([2600:1011:a102:bdcb:7217:7162:14b2:5b0]) by smtp.gmail.com with ESMTPSA id y7-20020a1709029b8700b001929dff50a9sm1850644plp.87.2023.01.24.07.48.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Jan 2023 07:48:57 -0800 (PST) From: To: , Subject: Yocto Project Status 24 January 2023 (WW04) Date: Tue, 24 Jan 2023 08:48:56 -0700 Message-ID: <0e2c01d9300b$5eb53e10$1c1fba30$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0E2D_01D92FD0.B258B000" X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AdkwC0mcKEQOgWR+S8qXYOe6h8Q1vg== 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, 24 Jan 2023 15:49:00 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/176328 This is a multipart message in MIME format. ------=_NextPart_000_0E2D_01D92FD0.B258B000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 4.2 M2 Next Deadline: 23rd January 2023 YP 4.2 M2 Build Next Team Meetings: * Bug Triage meeting Thursday January 26th 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) * Weekly Project Engineering Sync Tuesday January 24th at 8 am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 ) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * YP 4.1.2 and YP 3.1.22 were released * YP 4.2 M2 is due to build this week. * Stable builds have been proving hard to obtain due to varying issues over many of the submitted patches. This has limited patch flow over the last week. * We were able to merge 6.1 kernel improvements and a number of good bug fixes in other areas too. * There has been an improvement to the configurability of patch warnings/errors and patch fuzz issues will now error and stop builds by default. * Warning/errors over missing Upstream-Status details in non-core layers appears too controversial to enable by default but the option is now available should users wish to. * CVE levels in master are becoming worrying again, Ross helpfully summarized the situation and submitted CPE changes for some of the issues being highlighted, thanks! * We have a growing number of bugs in bugzilla, any help with them is appreciated. Ways to contribute: * As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: patchtest, layerindex, devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components! * 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 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_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. * Help is very much welcome in trying to resolve our autobuilder intermittent issues. 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. * Help us resolve CVE issues: CVE metrics YP 4.2 Milestone Dates: * YP 4.2 M2 build date 2023/01/23 * YP 4.2 M2 Release date 2023/02/03 * YP 4.2 M3 build date 2023/02/20 * YP 4.2 M3 Release date 2023/03/03 * YP 4.2 M4 build date 2023/04/03 * YP 4.2 M4 Release date 2023/04/28 Upcoming dot releases: * YP 4.1.2 is released * YP 3.1.22 is released * YP 4.0.7 build date 2023/01/30 * YP 4.0.7 Release date 2023/02/10 * YP 3.1.23 build date 2023/02/13 * YP 3.1.23 Release date 2023/02/24 * YP 4.0.8 build date 2023/02/27 * YP 4.0.8 Release date 2023/03/10 * YP 4.1.3 build date 2023/03/06 * YP 4.1.3 Release date 2023/03/17 * YP 3.1.24 build date 2023/03/20 * YP 3.1.24 Release date 2023/03/31 * YP 4.0.9 build date 2023/04/10 * YP 4.0.9 Release date 2023/04/21 * YP 4.1.4 build date 2023/05/01 * YP 4.1.4 Release date 2023/05/13 * YP 3.1.25 build date 2023/05/08 * YP 3.1.25 Release date 2023/05/19 * YP 4.0.10 build date 2023/05/15 * YP 4.0.10 Release date 2023/05/26 Tracking Metrics: * WDD 2442 (last week 2457) ( https://wiki.yoctoproject.org/charts/combo.html) * OE-Core/Poky Patch Metrics * Total patches found: 1190 (last week 1181) * Patches in the Pending State: 279 (23%) [last week 279 (24%)] * https://autobuilder.yocto.io/pub/non-release/patchmetrics/ 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_0E2D_01D92FD0.B258B000 Content-Type: text/html; boundary="----=_NextPart_000_0EFE_01D92A4F.B6C53220"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 4.2 M2

Next Deadline: 23rd = January 2023 YP 4.2 M2 Build

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 4.1.2 and YP 3.1.22 were = released
  • YP 4.2 M2 is due to build this = week.
  • Stable builds have been proving = hard to obtain due to varying issues over many of the submitted patches. = This has limited patch flow over the last = week.
  • We were able to merge 6.1 = kernel improvements and a number of good bug fixes in other areas = too.
  • There has been an improvement = to the configurability of patch warnings/errors and patch fuzz issues = will now error and stop builds by default.
  • Warning/errors over missing = Upstream-Status details in non-core layers appears too controversial to = enable by default but the option is now available should users wish = to.
  • CVE levels in master are = becoming worrying again, Ross helpfully summarized the situation and = submitted CPE changes for some of the issues being highlighted, = thanks!
  • We have a growing number of = bugs in bugzilla, any help with them is = appreciated.

 

Ways to = contribute:

 

YP 4.2 Milestone = Dates:

  • YP 4.2 M2 build date = 2023/01/23
  • YP 4.2 M2 Release date = 2023/02/03
  • YP 4.2 M3 build date = 2023/02/20
  • YP 4.2 M3 Release date = 2023/03/03
  • YP 4.2 M4 build date = 2023/04/03
  • YP 4.2 M4 Release date = 2023/04/28

 

Upcoming dot = releases:

  • YP 4.1.2 is = released
  • YP 3.1.22 is = released
  • YP 4.0.7 build date = 2023/01/30
  • YP 4.0.7 Release date = 2023/02/10
  • YP 3.1.23 build date = 2023/02/13
  • YP 3.1.23 Release date = 2023/02/24
  • YP 4.0.8 build date = 2023/02/27
  • YP 4.0.8 Release date = 2023/03/10
  • YP 4.1.3 build date = 2023/03/06
  • YP 4.1.3 Release date = 2023/03/17
  • YP 3.1.24 build date = 2023/03/20
  • YP 3.1.24 Release date = 2023/03/31
  • YP 4.0.9 build date = 2023/04/10
  • YP 4.0.9 Release date = 2023/04/21
  • YP 4.1.4 build date = 2023/05/01
  • YP 4.1.4 Release date = 2023/05/13
  • YP 3.1.25 build date = 2023/05/08
  • YP 3.1.25 Release date = 2023/05/19
  • YP 4.0.10 build date = 2023/05/15
  • YP 4.0.10 Release date = 2023/05/26

 

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_0E2D_01D92FD0.B258B000--