From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-f172.google.com (mail-pl1-f172.google.com [209.85.214.172]) by mail.openembedded.org (Postfix) with ESMTP id 24148600E9 for ; Tue, 11 Feb 2020 15:51:26 +0000 (UTC) Received: by mail-pl1-f172.google.com with SMTP id ay11so4435513plb.0 for ; Tue, 11 Feb 2020 07:51:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version:content-language :thread-index; bh=jJP1bMovBIUu1p2gDP3mQ5E6FXmFdu0kWp/NLjvmHOo=; b=UAXsuGo4JcNXhHQYRAEipyWyc6U1lAIToLd49NAh0NHfys44W+P6PsmppdwzUyzgEc 5w4PpqD7RK9V4frTcD8ECbbBvpNTeELIDIoSQ16by08G3JzZal6I2po1Xt4meZUfEknY 15CTxmuoNiw9dteDGuhQvzmYMDaFMUvePrhoq5lSb+uPMfRKh75JVikDpVlBhk4EGWWk rqY0Lgtorlm7o8tX3o7fduuqDblTjmc773DNmQ31BKhKyvIebUGLcVYddPaIVCSySDgj PkgTg843iKvpeV0HdQFWw8CKRWwNSSh1O14e6IFWOrZR3z/D6iR2ta3S0nPR1jzdubSR buNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version :content-language:thread-index; bh=jJP1bMovBIUu1p2gDP3mQ5E6FXmFdu0kWp/NLjvmHOo=; b=ZeOCOvEEtRqJV7DJohodYTTyzhRGBqmP0+6gEMr63192MIeA9Szm5orEbInMy5/0F4 fGkgRF+jk/LNWaMY8sq0oqK/vDO+k4MtT/8Ll7EVUIFiLdLUn0hZnEY3lbhAwFuOd9Qi 3oavDGJG/oHyGtZj/1DPcrTWQ1dGijAVrlgzxNV1DWuO7E8vitwdu3XJTBwfhI0hi4Uk k4JHb/cOTRGSeJmXHFnHgzp4aS88EoTPQSH08Sthbkt7PZgv/wATj6bzSB5ujSy5nJ9+ JBpkaKSttDNPORqd7urSvoz5MhbToM0HxUdIM0u5gEVSmHEFtG7rcRBZz8JZTCxCz7aD zwsw== X-Gm-Message-State: APjAAAWWb/vToJJTUFxnkAZTrTKMXmjql6ErWe5P4Wy0C01xTNrgtSFf wrUS2hnM2HuFf/uggomkZtw= X-Google-Smtp-Source: APXvYqy3H3wuVHuNNMRbPcv6zLgA2CHDggT8XKLDbZmZHIxsgLj8mNBgDZBxNVB3cEokZIRp/PvZNA== X-Received: by 2002:a17:90a:8a0e:: with SMTP id w14mr4478589pjn.51.1581436287127; Tue, 11 Feb 2020 07:51:27 -0800 (PST) Received: from skjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id d2sm3694928pjv.18.2020.02.11.07.51.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Feb 2020 07:51:26 -0800 (PST) From: To: , Date: Tue, 11 Feb 2020 07:51:26 -0800 Message-ID: <02bb01d5e0f3$1e6f19d0$5b4d4d70$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdXg8xGEXPGD7LfMSzOUBhjFlLJndw== Subject: Yocto Project Status WW06'20 X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2020 15:51:26 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_02BC_01D5E0B0.104D1250" Content-Language: en-us ------=_NextPart_000_02BC_01D5E0B0.104D1250 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M3 Next Deadline: YP 3.1 M3 build date 2/24/2020 Next Team Meetings: * Bug Triage meeting Thursday Feb. 13th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Mar. 3rd at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Feb. 11th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Feb. 11th at 8am PDT ( https://www.twitch.tv/yocto_project) Key Status/Updates: * YP 3.1 M2 was released * We're now in a much better position with reproducibility issues after around 20 patches merged addressing various problems. Some issues still remain but the bulk of the issues appear to be under control now. * Due to the number and type of fixes found, the 3.0.2 rc1 build will be abandoned and rc2 built with the reproducibility fixes (as well as additional hashserv/multiconfig fixes). This delays 3.0.2 by a week but for a reasonable set of improvements. * YP 3.0.2 should therefore enter QA within the next day or so. * Review of newly queued warrior (2.7.3) patches will happen later this week once 3.0.2 is in QA. * With the new fixes and a small fix to the autobuilder code, we managed the first green "full" build in nearly three months. * The incoming patch queue is roughly under control again * We're collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add). * One worrying metric is that the WDD is now on level with the high of 2017 so our worst defect weighting in two years. This is sadly unsurprising and directly correlated to a lack of participation in the triage process and a lack of people working on general bug fixing. * The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated. YP 3.1 Milestone Dates: * YP 3.1 M3 build date 2/24/2020 * YP 3.1 M3 release date 3/6/2020 * YP 3.1 M4 build date 3/30/2020 * YP 3.1 M4 release date 4/24/2020 Planned upcoming dot releases: * YP 2.7.3 build date 2/10/2020 * YP 2.7.3 release date 2/21/2020 * YP 3.0.2 build date 2/3/2020 * YP 3.0.2 release date 2/14/2020 Tracking Metrics: * WDD 2728 (last week 2767) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1361 (last week 1368) * Patches in the Pending State: 547 (40%) [last week 544 (40%)] 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_02BC_01D5E0B0.104D1250 Content-Type: text/html; boundary="----=_NextPart_000_0951_01D5DB30.DAF1A3C0"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M3

Next Deadline: YP = 3.1 M3 build date 2/24/2020

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 3.1 M2 was = released
  • We’re now in a much = better position with reproducibility issues after around 20 patches = merged addressing various problems. Some issues still remain but the = bulk of the issues appear to be under control = now.
  • Due to the number and type of = fixes found, the 3.0.2 rc1 build will be abandoned and rc2 built with = the reproducibility fixes (as well as additional hashserv/multiconfig = fixes). This delays 3.0.2 by a week but for a reasonable set of = improvements.
  • YP 3.0.2 should therefore enter = QA within the next day or so.
  • Review of newly queued warrior = (2.7.3) patches will happen later this week once 3.0.2 is in = QA.
  • With the new fixes and a small = fix to the autobuilder code, we managed the first green = “full” build in nearly three = months.
  • The incoming patch queue is = roughly under control again
  • We’re collecting a list = of companies, products and projects which use the Yocto Project on the = wiki: https://wiki.yoctoproject.org/wiki/Project_Users<= /span> Please add any you know are missing (or email Richard/Stephen = who can add).
  • One worrying metric is that the = WDD is now on level with the high of 2017 so our worst defect weighting = in two years. This is sadly unsurprising and directly correlated to a = lack of participation in the triage process and a lack of people working = on general bug fixing.
  • The triage team is worried = about attendance at triage meetings and the project is finding it hard = to find people to help fix bugs. If anyone is willing to work on bugs, = assistance would be greatly appreciated.

 

YP 3.1 Milestone = Dates:

  • YP 3.1 M3 build date = 2/24/2020
  • YP 3.1 M3 release date = 3/6/2020
  • YP 3.1 M4 build date  = 3/30/2020
  • YP 3.1 M4 release date  = 4/24/2020

 

Planned upcoming = dot releases:

  • YP 2.7.3 build date  = 2/10/2020
  • YP 2.7.3 release date = 2/21/2020
  • YP 3.0.2 build date  = 2/3/2020
  • YP 3.0.2 release date = 2/14/2020

 

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_02BC_01D5E0B0.104D1250--