From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-f180.google.com (mail-pl1-f180.google.com [209.85.214.180]) by mail.openembedded.org (Postfix) with ESMTP id A37B97D97D for ; Tue, 13 Aug 2019 14:52:19 +0000 (UTC) Received: by mail-pl1-f180.google.com with SMTP id z3so2562809pln.6 for ; Tue, 13 Aug 2019 07:52:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version:thread-index :content-language; bh=fZ08hXcD2jcjQxMS02sLLO9nybMEmRxhFfZ2ssjCJCs=; b=dcqKiIWJTC2Dh9xBueGCOWdjM/n6TbMlvC9pzzsqygsJS5KDJR+rSsoSQZlwrfvMG0 PZPg52ssHgkqtHHPSpn4ViLNvjqpEDf93g2ZzqPGt+oANXcLdgP123CZnj94kXhWjOy9 VMIVVY9w8EIN2ddXlcIxFEIw9IDEb1eKAIQ3HBfk35LRHYvEfQMUn4Z9Q15dcpPWRuzp QWtWeJeG3zp2TqsPHgakpQBKKxDRDrDFIdMmx9ltQlfSlKtNs24P+jczv1PytB8LtK2/ c/ysYyJ14ATQ8jmrXEpjR4W5LJk/gGt8H5i8DSjtDkX9GkLtMfG/tLVsphudAH6n2val CPnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :thread-index:content-language; bh=fZ08hXcD2jcjQxMS02sLLO9nybMEmRxhFfZ2ssjCJCs=; b=EX3HXjkvYtmmuDdVbye1mHlREShIdKqX/4hx/49zTVOk7smP+mOsv/VPK3pv7Gzxwm d892uggCLZY2yWEFlL5f4vCsLuZGsgIuchqOEWeZ2e+1C6sZQV8YP3mrjM2X/kSLe+Wh L6sgYrkzj8SHfGwsJ7OrZWiEk3TDtYcfCHAO/FkpMoBZvJPSYISfAwVkp4VLoXGTJOUL ej7LhJWmnkhDgmmG8vxIuJQ3YK+HCW0B8sJFTA6n7PgT31h9cfXl5mDTyEhm1Lk6cxK6 dz0RybXTuGUJvDj9+mB5CxrAj07wsnKS8taOh9W29YTaF8aUHL6ISweUBQO/0QnpAiGw ThQw== X-Gm-Message-State: APjAAAXb29q8Cvw1j513NeaJVqG82sxn7H3XY8oaKOVbKGuI0FeevvxG 251VYjet88WPV+mphe8n7NE= X-Google-Smtp-Source: APXvYqxWfH8sbFs30HVHuQyw1oOY0MQW+ewth2eDjHtzicggpLLOJchVZ4KFqcC87NLVFn4VIgmSkQ== X-Received: by 2002:a17:902:b582:: with SMTP id a2mr12459478pls.199.1565707940671; Tue, 13 Aug 2019 07:52:20 -0700 (PDT) Received: from sjolley (c-71-59-136-149.hsd1.or.comcast.net. [71.59.136.149]) by smtp.gmail.com with ESMTPSA id n10sm36368367pgv.67.2019.08.13.07.52.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Aug 2019 07:52:20 -0700 (PDT) From: To: , Date: Tue, 13 Aug 2019 07:52:19 -0700 Message-ID: <011401d551e6$b5266d20$1f734760$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdVR5p3kJUkqv8BrQoqrIVSkEKcsDA== Cc: Lieu.Ta@windriver.com Subject: Yocto Project Status WW33'19 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, 13 Aug 2019 14:52:21 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0115_01D551AC.08CBDAE0" Content-Language: en-us ------=_NextPart_000_0115_01D551AC.08CBDAE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 2.8 M3 Next Deadline: YP 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, 2019 SWAT Team Rotation: * SWAT lead is currently: Amanda * SWAT team rotation: Amanda -> Chen on Aug. 16, 2019 * SWAT team rotation: Chen -> Armin on Aug. 23, 2019 * https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Next Team Meetings: * Bug Triage meeting Thursday August 15th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Sept. 3rd at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Sept. 3rd at 8am PDT ( https://www.twitch.tv/yocto_project) Key Status/Updates: * YP 2.6.3 is out of QA and being readied for release. * This release which was 2.8 will now become 3.0. * The sstate has equivalency work has run into some challenges: * performance of the hash server is not able to scale to the autibuilder's load * performance of runqueue has regressed even when not using the hash equivalency code * bugfixes in master-next regress performance even further * there are bugs being triggered by the has equivalency code that need investigation and resolution (along with test cases creating). These issues are being worked on but we need to ensure correctness of the new code first before the performance can be fixed * There were updates so some key components for bug fixes this week, in particular pseudo. * General patch merging is happening and the queue is mostly clear and flowing but it isn't happening as frequently as usual due to the hash equivalency work. Planned Releases for YP 3.0 {2.8}: * M2 is released. * M3 Cutoff (Feature Freeze) 25th Aug * M3 Release 6th Sept * M4 Cutoff 30th Sept - this will be YP 3.0. * YP 3.0 {2.8 (M4)} Final Release 25th Oct Planned upcoming dot releases: * YP 2.7.2 (Warrior) is planned for after YP 3.0 release. * YP 2.6.3 (Thud) is out of QA and being readied for release. * YP 2.6.4 (Thud) is planned for after YP 2.7.2 release. Tracking Metrics: * WDD 2482 (last week 2481) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1489 (last week 1496) * Patches in the Pending State: 617 (41%) [last week 615 (41%)] Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features 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 Project Manager * Cell: (208) 244-4460 * Email: sjolley.yp.pm@gmail.com ------=_NextPart_000_0115_01D551AC.08CBDAE0 Content-Type: text/html; boundary="----=_NextPart_000_07D0_01D54C30.E0CBC710"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 2.8 M3

Next Deadline: YP = 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, = 2019

 

SWAT Team = Rotation:

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 2.6.3 is out of QA and being = readied for release.
  • This release which was 2.8 will = now become 3.0.
  • The sstate has equivalency work = has run into some challenges:
    • performance of the hash server = is not able to scale to the autibuilder’s = load
    • performance of runqueue has = regressed even when not using the hash equivalency = code
    • bugfixes in master-next regress = performance even further
    • there are bugs being triggered = by the has equivalency code that need investigation and resolution = (along with test cases creating).

These issues are = being worked on but we need to ensure correctness of the new code first = before the performance can be fixed

  • There were updates so some key = components for bug fixes this week, in particular = pseudo.
  • General patch merging is = happening and the queue is mostly clear and flowing but it isn’t = happening as frequently as usual due to the hash equivalency = work.

 

Planned Releases = for YP 3.0 {2.8}:

  • M2 is = released.
  • M3 Cutoff (Feature Freeze) 25th = Aug
  • M3 Release 6th = Sept
  • M4 Cutoff 30th Sept - this will = be YP 3.0.
  • YP 3.0 {2.8 (M4)} Final Release = 25th Oct

 

Planned upcoming = dot releases:

  • YP 2.7.2 (Warrior) is planned = for after YP 3.0 release.
  • YP 2.6.3 (Thud) is out of QA = and being readied for release.
  • YP 2.6.4 (Thud) is planned for = after YP 2.7.2  release.

 

Tracking = Metrics:

 

Key Status Links = for YP:

https://wiki.yoctoproject.or= g/wiki/Yocto_Project_v2.8_Status

https://wiki.yoctoproject.or= g/wiki/Yocto_2.8_Schedule

https://wiki.yoctoproject.or= g/wiki/Yocto_2.8_Features

 

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 Project Manager

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

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

 

------=_NextPart_000_0115_01D551AC.08CBDAE0--