From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f194.google.com (mail-pf1-f194.google.com [209.85.210.194]) by mail.openembedded.org (Postfix) with ESMTP id AF96D6C104 for ; Tue, 12 Mar 2019 16:05:01 +0000 (UTC) Received: by mail-pf1-f194.google.com with SMTP id i19so2173323pfd.0 for ; Tue, 12 Mar 2019 09:05:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:date:message-id:mime-version:thread-index :content-language; bh=6rsNctFLbK9Fn5j/v/Q+r3+hBm3FOLp99kZs06Q975s=; b=hiT+3769+lwyT7VhLi1sHT2kao6jWTydu0NZ5RNoRaLXm5oB1D6U7WNato8Mc21xA3 kT9bNdaMzisuyPujs+Cm0R9PVH/+EnODe3G/zIHbYIfcAuGhhiRTY7D8HfkAEDrSeJyK lma61lSX1W5Mferhyd8bQg8FKwvd6nkzudItIvjTttV7s6cLGODHIjdxw7JCqicCCKaG evJ4qhCiMAC9efgpdSjSWBn0hBb7J9wNy/fgfCDyfE2Vtl94eFZ9YNX6aXjHHL0qHvxA oPyyU+JR6fdnnZfeA+6nfibm5Au9htFYGOYzbcuxV+UW6nQlUFXonLt9e4XnQhRBrIAM lBCA== 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 :thread-index:content-language; bh=6rsNctFLbK9Fn5j/v/Q+r3+hBm3FOLp99kZs06Q975s=; b=ujWhsIXuaAgT06DgRqArGIGog6TytjAlzdQoY0x6xHe0CwHsZbX/Lg1pg82XQ/EGtw F+YOErig2aS0o+zCouqfyMKmfISoFC/nZylcVHkmZ/cirNmeuWpmLN5pdUe/7bJ4Iv4t bs2xMbHR39ULDiTW0XdEdqADDIW05oUN+z3C1TyucZwXUCECo/Uq3I14DX8x1W2Zz9NT yvcSE8xuiAMMbWA9/khAP5+8ONIoyihnxCHTnX8nwzxtI2vFyDFgIvjtBkUhod2zGRoV imm81zU9uwInIJtT3Z0sEAfRsOEP1cc0NwOtpNTrS28Lfh2Sj7Qomcv3Xi56JFVXQdwS Anyw== X-Gm-Message-State: APjAAAWAh59iam+O+OIx5eDgEzANCw8t5f/g1otjYx2japDtCGcmxPqd 55qHQvT8GKo7/OwyFi9qtyEFSqPC X-Google-Smtp-Source: APXvYqzjTknnVR3Hy/m9orcMFSr1pTGlPxpmHwsIFr0qwRuM+HqJXzQi0p8+8syxFzUL7JNmCcAcQQ== X-Received: by 2002:a65:4203:: with SMTP id c3mr35981038pgq.271.1552406702310; Tue, 12 Mar 2019 09:05:02 -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 u18sm12788451pfn.22.2019.03.12.09.05.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Mar 2019 09:05:01 -0700 (PDT) From: To: , Date: Tue, 12 Mar 2019 09:05:01 -0700 Message-ID: <01b601d4d8ed$593ebe80$0bbc3b80$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdTY7U6zuNIRex36SLmKgB9UVdzHQg== Subject: Yocto Project Status WW11'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, 12 Mar 2019 16:05:01 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01B7_01D4D8B2.ACE42C40" Content-Language: en-us ------=_NextPart_000_01B7_01D4D8B2.ACE42C40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 2.7 M3 (New feature Freeze has begun.) Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019 SWAT Team Rotation: * SWAT lead is currently: Anuj * SWAT team rotation: Anuj -> Armin on Mar. 15, 2019 * SWAT team rotation: Armin -> Paul on Mar. 23, 2019 * https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team Key Status/Updates: * YP 2.7 M2 rc2 was released on May 5, 2019. * We believe we now have all the key components for 2.7M3 in master-next but have not completed a successful test run with this. In addition to the list last week, this means M3 will include: * 5.0 kernel * qemuarm transition to armv7 * Busybox full replacement utils * Some invalid source revisions tested in master-next have broken the autobuilder causing build hangs and failures. With travel and other distractions, nobody is available to dive in and debug this immediately so it will block M3. * We also want to complete the transition to the new QA process and test this for M3. Aproov is going to send out details of this imminently, we believe the main code work is complete and its process/documentation that remains. We will block on this as we want to use the new QA process for M3 and the final 2.7 release. * YP 2.5.3 continues to be blocked on autobuilder-helper changes for the stable branches and the resulttool changes in master to move to the new QA process. Planned Releases for YP 2.7: * YP 2.7 M3 Cutoff is Feb. 25, 2019 * YP 2.7 M3 Release Target is Mar. 8, 2019 * YP 2.7 M4 Cutoff is Apr. 1, 2019 * YP 2.7 M4 Release Target is Apr. 26, 2019 Planned upcoming dot releases: * YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done. * YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done. * YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done. Tracking Metrics: * WDD 2439 (last week 2436) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1523 (last week 1502) * Patches in the Pending State: 657 (43%) [last week 658 (44%)] Key Status Links for YP: https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features 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_01B7_01D4D8B2.ACE42C40 Content-Type: text/html; boundary="----=_NextPart_000_01A6_01D4D327.CE2A4910"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 2.7 M3 (New feature Freeze has = begun.)

Next Deadline: YP = 2.7 M3 Cutoff was Feb. 25, 2019

 

SWAT Team = Rotation:

 

Key = Status/Updates:

  • YP 2.7 M2 rc2 was released on = May 5, 2019.
  • We believe we now have all the = key components for 2.7M3 in master-next but have not completed a = successful test run with this. In addition to the list last week, this = means M3 will include:
    • 5.0 = kernel
    • qemuarm transition to = armv7
    • Busybox full replacement = utils
  • Some invalid source revisions = tested in master-next have broken the autobuilder causing build hangs = and failures. With travel and other distractions, nobody is available to = dive in and debug this immediately so it will block = M3.
  • We also want to complete the = transition to the new QA process and test this for M3. Aproov is going = to send out details of this imminently, we believe the main code work is = complete and its process/documentation that remains. We will block on = this as we want to use the new QA process for M3 and the final 2.7 = release.
  • YP 2.5.3 continues to be = blocked on autobuilder-helper changes for the stable branches and the = resulttool changes in master to move to the new QA = process.

 

Planned Releases = for YP 2.7:

  • YP 2.7 M3 Cutoff is Feb. 25, = 2019
  • YP 2.7 M3 Release Target is = Mar. 8, 2019
  • YP 2.7 M4 Cutoff is Apr. 1, = 2019
  • YP 2.7 M4 Release Target is = Apr. 26, 2019

 

Planned upcoming = dot releases:

  • YP 2.5.3 (Sumo) will be = targeted after YP 2.7 M2 is done.
  • YP 2.5.4 (Sumo) will be = targeted after YP 2.7 M4 is done.
  • YP 2.6.2 (Thud) will be = targeted after YP 2.5.4 is done.

 

Tracking = Metrics:

 

Key Status Links = for YP:

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

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

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

 

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_01B7_01D4D8B2.ACE42C40--