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 917B5C636D3 for ; Tue, 31 Jan 2023 14:14:54 +0000 (UTC) Received: from mail-pl1-f178.google.com (mail-pl1-f178.google.com [209.85.214.178]) by mx.groups.io with SMTP id smtpd.web10.13026.1675174487036388982 for ; Tue, 31 Jan 2023 06:14:47 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=fudjoi2a; spf=pass (domain: gmail.com, ip: 209.85.214.178, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pl1-f178.google.com with SMTP id k13so15254205plg.0 for ; Tue, 31 Jan 2023 06:14:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-language:thread-index:mime-version:message-id:date:subject :to:from:from:to:cc:subject:date:message-id:reply-to; bh=86Q2CLZgCoWBEKMYwtmEc/enZha2PC5fH6ZP5Xr5FbQ=; b=fudjoi2a+yr//SXXhwAXvszIGgdxcVlFdG3u7OvEVKKu8lPaMr1crPTg/hWUA5v1Jl IeNmbDL1iJ+/5yauG5/38LnquRHP1gtcemGOvOXji5j2SSU2hBi+lsp74EE/xWwFmUS+ cs5OiI3sC/7H35l5enWSU4Ey3ts0jz5aL+3SCqaUiAnlB6kd3qkIoEh/z48CXl12PLvm nm3g/9q4T4gPt21AWbbJYt/4Zo71syQE50hmfIPSoH0W4JOLitiPGgZctmMe94k1XtW/ 8EAFVJlS54zvwp8LwJasp/ZSHJtP1KOyRfor6LyAlfilIF+8SP7j+MlbjQyLy7KsYqUr /V4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-language:thread-index:mime-version:message-id:date:subject :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=86Q2CLZgCoWBEKMYwtmEc/enZha2PC5fH6ZP5Xr5FbQ=; b=nZCheW554PPztdWin61+tmWDgFZFI73Mt/q61jO38w2vDJpPKzISWj9R7WkH01ZgM7 +QOK3Y8+msn6nSvaqAok781EC7cZsfIIWE7SGILhc/H6CkeF6Vt5l/uJZhS3CTnItAnR xACss3gF0efiXJcAJSPHsRRbd/06Ek4XSD/RuQUJyQCSr9GpKhGLuzNlDBgIDHLT38vI ZONivQ20ro2J8IFKhVID+rYxq+A9gm5tT77J1W6/miwwtAXS1PpXej6QHymPgB46+tD3 SCafHcNXl/xdSM5mpkNmv1Rwoukvm5BNgCeHSDHWMlDAGcUbrIJUliXFzvmERhx+qLBF Dm3g== X-Gm-Message-State: AO0yUKXxd9iz2oLTf6aURFF5kJ5q6f0gw8bTGsshr+BV4h0ImTEGAHiM OUCD/WB1FY8NqgWs5/I/ZdbXDuk7UzY= X-Google-Smtp-Source: AK7set9DkgY2znAbwJaWFjlbw2HBvwqcR9m1M50dEiUXygbRp8E606ZiGRyENTfGa+R5H71bjg/C0w== X-Received: by 2002:a17:903:24d:b0:193:38ce:7bb8 with SMTP id j13-20020a170903024d00b0019338ce7bb8mr12407562plh.37.1675174485902; Tue, 31 Jan 2023 06:14:45 -0800 (PST) Received: from skjolley ([2600:1011:a124:5236:60f7:d443:a417:be4a]) by smtp.gmail.com with ESMTPSA id d18-20020a170903231200b0019339f3368asm9955922plh.3.2023.01.31.06.14.44 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 31 Jan 2023 06:14:45 -0800 (PST) From: To: , Subject: Yocto Project Status 31 January 2023 (WW05) Date: Tue, 31 Jan 2023 07:14:43 -0700 Message-ID: <0dbb01d9357e$5e847230$1b8d5690$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0DBC_01D93543.B2280B30" X-Mailer: Microsoft Outlook 16.0 Thread-Index: Adk1fk9pT6wWjU7STm6x/RMq5jalzQ== Content-Language: en-us 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, 31 Jan 2023 14:14:54 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/176519 This is a multipart message in MIME format. ------=_NextPart_000_0DBC_01D93543.B2280B30 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 4.2 M3 Next Deadline: 20th February 2023 YP 4.2 M3 Build Next Team Meetings: * Bug Triage meeting Thursday February 2nd 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) * Weekly Project Engineering Sync Tuesday January 31st at 8 am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 ) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * YP 4.0.7 and YP 4.2 M2 are in QA * We switched to the 6.1 kernel by default for M2. Unfortunately there are a couple of intermittent issues that seem to have crept in. One is a reproducibility issue in perf, likely with some host component causing it as it only occurs on second builds. The second appears to be an intermittent networking issue accessing a python http-server for testing dnf which appeared after the kernel version change. * We are continuing to see other intermittent failures which are limiting how quickly we can merge changes. A summary of some of the key issues was sent to the mailing list: https://lists.openembedded.org/g/openembedded-core/message/176476 * There have been changes to the way the codeparser cache in bitbake stores data which should reduce cache size, reduce the times data needs to be written out and generally help performance. * CVE levels in master are still high but there are patches in progress for most issues as I understand it. * 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 built and in QA * 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.0.7 built and in QA * 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 2447 (last week 2442) ( https://wiki.yoctoproject.org/charts/combo.html) * OE-Core/Poky Patch Metrics * Total patches found: 1205 (last week 1190) * Patches in the Pending State: 280 (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_0DBC_01D93543.B2280B30 Content-Type: text/html; boundary="----=_NextPart_000_0E2D_01D92FD0.B258B000"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 4.2 M3

Next Deadline: 20th = February 2023 YP 4.2 M3 Build

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 4.0.7 and YP 4.2 M2 are in = QA
  • We switched to the 6.1 kernel = by default for M2. Unfortunately there are a couple of intermittent = issues that seem to have crept in. One is a reproducibility issue in = perf, likely with some host component causing it as it only occurs on = second builds. The second appears to be an intermittent networking issue = accessing a python http-server for testing dnf which appeared after the = kernel version change.
  • We are continuing to see other = intermittent failures which are limiting how quickly we can merge = changes. A summary of some of the key issues was sent to the mailing = list: https://lists.openembedded.org/g/openembedded-cor= e/message/176476
  • There have been changes to the = way the codeparser cache in bitbake stores data which should reduce = cache size, reduce the times data needs to be written out and generally = help performance.
  • CVE levels in master are still = high but there are patches in progress for most issues as I understand = it.
  • 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 built and in = QA
  • 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.0.7 built and in = QA
  • 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_0DBC_01D93543.B2280B30--