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 2C0BAC4167B for ; Tue, 20 Dec 2022 15:51:34 +0000 (UTC) Received: from mail-pj1-f44.google.com (mail-pj1-f44.google.com [209.85.216.44]) by mx.groups.io with SMTP id smtpd.web11.53611.1671551484266382192 for ; Tue, 20 Dec 2022 07:51:24 -0800 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20210112 header.b=IReT28pP; spf=pass (domain: gmail.com, ip: 209.85.216.44, mailfrom: sjolley.yp.pm@gmail.com) Received: by mail-pj1-f44.google.com with SMTP id u15-20020a17090a3fcf00b002191825cf02so12550349pjm.2 for ; Tue, 20 Dec 2022 07:51:24 -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=frU4Y1HURyaAh1twpEcLqlwX+vviCZ7Uu+cseIFDQcQ=; b=IReT28pP1jdcSvLVfBCdm7MWMV/bxmNPgFkTkTT+feiElubmhQIXJ46hytXtcLdADJ mYugLngUnXR1CCVV2nieXb13SeHHAyDuOL6RArJVPC8y7nRFyzON8t0xkb3rYu3LHkst zr1iF6cWp/o/OBywRdB0V4t1qGbw/iA5WNRI9V82xG0fOFWvlYTs0aLWe+oV3VL4tDue YQ3T60JUxndk8MGXMPy8p76oD47VBdSjUwEnq4h3OzXRhmBszLxwvwvY1UiIpNfmB5mF V2eC4zgSkzr/1WNtCKEjfR0PJkXVjRkjINN7Ux1WD3xHLw8wrgDpgzxNtDjjqDYPCNOc JC1w== 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=frU4Y1HURyaAh1twpEcLqlwX+vviCZ7Uu+cseIFDQcQ=; b=z+4svDql6ynY6xoqg6LHq0Sro9IMVGOOVTLK1Ij29Thhl6+M2kfI/fwq1gw1kCAbsO ke/n54+9hNVivmrGuXA/xe3pQ9oMlEv/5IuZ40FdTVpavMRm5TFydR8uJ/XnFrIiIDru 8bnG6Dwo5KLSCPeZN61oYrbpggs+QIBx8Z7FPrJhpQ6YA81x4MGEKTtNEzi6s2N1YSLg KMNF191vj1Lbizzi6fZOw37r/Ip1FhVfTaEeyYXdN22K+pk38Ojd5tMcSL0k5GeYtvPE uPWvYHVoaq5ycmY7c04p7A9+frxkm8EMxF+W0VRER9pnl5t+GFXVWaEpoOaDh85aDBzP O6dA== X-Gm-Message-State: AFqh2kpaY48TQjjPAO7b/qLZbqFPsvj/QYSjmnVCqoW4tnz1VRxFMco9 2tsKZo6niXULiNpQJw7yYcB/Al+BiQWUNQ== X-Google-Smtp-Source: AMrXdXtkMu+roXGd+GFvFztOgEftza81eMEGm3btfQ6IJkuNv11SLXBGgFNgsvfsBWXxujW4brg0CQ== X-Received: by 2002:a17:902:ab1b:b0:191:3f73:bf4e with SMTP id ik27-20020a170902ab1b00b001913f73bf4emr1645838plb.62.1671551483083; Tue, 20 Dec 2022 07:51:23 -0800 (PST) Received: from skjolley ([2600:1011:a11e:7926:3670:229e:6a7c:c6b1]) by smtp.gmail.com with ESMTPSA id x5-20020a170902ec8500b00189371b5971sm9539376plg.220.2022.12.20.07.51.21 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Dec 2022 07:51:22 -0800 (PST) From: To: , Subject: Yocto Project Status 20 December 2022 (WW51) Date: Tue, 20 Dec 2022 08:51:22 -0700 Message-ID: <1a5b01d9148a$e91aa460$bb4fed20$@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_1A5C_01D91450.3CBE3D60" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdkUitXwyWQ2+KZ8SKKdkcCxzRpZWw== 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, 20 Dec 2022 15:51:34 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/174859 This is a multipart message in MIME format. ------=_NextPart_000_1A5C_01D91450.3CBE3D60 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 4.2 M2 Next Deadline: 23th January 2023 YP 4.2 M2 Build Next Team Meetings: * Bug Triage meeting Thursday December 22nd 7:30 am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) * Weekly Project Engineering Sync Tuesday December 20th at 8 am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09 ) * Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: * YP 4.2 M1 and YP 4.0.6 passed QA and are due for release. * Builds on the autobuilder are problematic at present due to connection losses with the controller machine. We understand the cause and will be migrating the controller to a new server/location to address this. * That, combined with OOM issues from recent bitbake cache changes meant patches are merging more slowly this week. * There are a number of bitbake patches pending which are a bit more invasive than usual. These are aiming to address: * memory issues seen with the recent cache changes and bitbake -S * UI hangs where the bitbake server has crashed/hung or otherwise failed * issues where bitbake may have removed another server instances bitbake.sock network socket file * console interaction issues where bitbake may not respond to Ctrl+C * event handler race issues around datastore accesses * The OE TSC decided in favour of adding export flag expansion despite the performance impact so that patch will be queued. * CVE levels in master are concerning again * With some debugging, the bitbake.sock disappearance was potentially identified and also issues with OOM process killing locking up bitbake's server and UI were studied. * We have a growing number of bugs in bugzilla, any help with them is appreciated. * There will be no status report next week, the next will be 3rd January 2023. 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 M1 is ready for released * 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.0.6 is out of QA * YP 4.1.2 build date 2023/01/09 * YP 4.1.2 Release date 2023/01/20 * YP 3.1.22 build date 2023/01/16 * YP 3.1.22 Release date 2023/01/27 * 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 2462 (last week 2437) ( https://wiki.yoctoproject.org/charts/combo.html) * OE-Core/Poky Patch Metrics * Total patches found: 1161 (last week 1162) * Patches in the Pending State: 282 (24%) [last week 285 (25%)] * 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_1A5C_01D91450.3CBE3D60 Content-Type: text/html; boundary="----=_NextPart_000_0CA4_01D90ECE.FEE20F20"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 4.2 M2

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

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 4.2 M1 and YP 4.0.6 passed = QA and are due for release.
  • Builds on the autobuilder are = problematic at present due to connection losses with the controller = machine. We understand the cause and will be migrating the controller to = a new server/location to address this.
  • That, combined with OOM issues = from recent bitbake cache changes meant patches are merging more slowly = this week.
  • There are a number of bitbake = patches pending which are a bit more invasive than usual. These are = aiming to address:
    • memory issues seen with the = recent cache changes and bitbake -S
    • UI hangs where the bitbake = server has crashed/hung or otherwise failed
    • issues where bitbake may have = removed another server instances bitbake.sock network socket = file
    • console interaction issues = where bitbake may not respond to Ctrl+C
    • event handler race issues = around datastore accesses
  • The OE TSC decided in favour of = adding export flag expansion despite the performance impact so that = patch will be queued.
  • CVE levels in master are = concerning again
  • With some debugging, the = bitbake.sock disappearance was potentially identified and also issues = with OOM process killing locking up bitbake’s server and UI were = studied.
  • We have a growing number of = bugs in bugzilla, any help with them is = appreciated.
  • There will be no status report = next week, the next will be 3rd January = 2023.

 

Ways to = contribute:

 

YP 4.2 Milestone = Dates:

  • YP 4.2 M1 is ready for = released
  • 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.0.6 is out of = QA
  • YP 4.1.2 build date = 2023/01/09
  • YP 4.1.2 Release date = 2023/01/20
  • YP 3.1.22 build date = 2023/01/16
  • YP 3.1.22 Release date = 2023/01/27
  • 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_1A5C_01D91450.3CBE3D60--