From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-f50.google.com (mail-pj1-f50.google.com [209.85.216.50]) by mail.openembedded.org (Postfix) with ESMTP id 73BBC616C9 for ; Tue, 25 Feb 2020 15:54:59 +0000 (UTC) Received: by mail-pj1-f50.google.com with SMTP id ep11so1424640pjb.2 for ; Tue, 25 Feb 2020 07:55:00 -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=Y0qEzp0+Yr4LW4Sa4hbVpaqji/X1jcCV777iTXwMIRo=; b=pPmfwIChdbxXi1HMxG7l9eIMUHTx6pS4T7eYNxYX0PyXh3Vgt4KnQFzWetbp5+1x33 r5PDzyJphR95Pe9ZgkzasF9dTtimcEEk309GxjwAGdNIqrNxrOoV9bgM9VziaGMM6Qyh NrKnj+AXtbP3ZAzOnniVJ8LMpVmSxMPhbqNs70zx7Ft95it57PXqbytYEkXD6Bt6OZX9 iONagbB91xVK+P0tgqjsDQyVd20WepzQdEzIE4/o9NwVLJn8Q7KzFEym+nIiI7bLQzcI G/qDU2mwpawdbU1TyCFzvR48ZuR0rAmIs4ZPQgsVC4A7QPSGZ2Mi+7g2pX8Mcq5jV/py X/8Q== 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=Y0qEzp0+Yr4LW4Sa4hbVpaqji/X1jcCV777iTXwMIRo=; b=dbuSqwocqbKp8u2yzwcWrKvI9w87XsQagAuFDNRZ85sta085PHfOfPQSyX29Y94ieF GRFcqtQSanomhT6MsSfrlcd6swVrAVLNDm+bwqzpX4OGG3RzA83MGh7VBtRxx4t8AKqN I1Eay46L5nJacP7TQLXzPEkuo0U7bGEg0zxnB6DemTn1fEMx7z6JLoz4Hj1d4vYJnW6d 9hPwnIy9jtidPXU8lov2oEwpZxzfX8F4HxeI11ICc9bxcrYPsIgRipqY/DZ4m1jf1aMc yCBKduyexLSI4eMnHFgtOhhMSw+45VNIaLhsV0eytZxqGHNSVAR7xfx2/Le5j0DvwGXH vV5A== X-Gm-Message-State: APjAAAUChaVROHVQ8XBAmJZMNfZjZlgYrRkrxjQ9rMDniaNZnQCNf+Fn /k7AoX9B8VsXUnPajrsgEm+NemSO X-Google-Smtp-Source: APXvYqwtsUH4aINvFFTAwdIAgzWY6Q6DDUriQ+46ijMWxcsodG3MeS/HSstreb9pb8hFUrUEfQY+VA== X-Received: by 2002:a17:902:82c5:: with SMTP id u5mr54571906plz.219.1582646100441; Tue, 25 Feb 2020 07:55:00 -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 136sm2991356pgh.26.2020.02.25.07.54.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Feb 2020 07:55:00 -0800 (PST) From: To: , Date: Tue, 25 Feb 2020 07:54:59 -0800 Message-ID: <040e01d5ebf3$ef621320$ce263960$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdXr8+OBSREt9hH/Qf2heekAWZ0NRg== Subject: Yocto Project Status WW08'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, 25 Feb 2020 15:54:59 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_040F_01D5EBB0.E143B520" Content-Language: en-us ------=_NextPart_000_040F_01D5EBB0.E143B520 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M3 - At Feature Freeze Next Deadline: YP 3.1 M3 build date 2/24/2020 Next Team Meetings: * Bug Triage meeting Thursday Feb. 27th 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. 25th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - See http://www.twitch.tv/letoatreidesthe2nd Key Status/Updates: * YP 2.7.3 rc1 is in QA with the report due next week. * YP 3.0.2 rc2 was rebuilt to remove a broken bash CVE patch, rc3 had automated QA only and is now due for release. * We are now at the date for M3 which is feature freeze. We are not yet in a position where we can build M3 as there are a number of open high blocking bugs but patches will need to start tapering down to bug fix only. More invasive or unplanned features will no longer be accepted. * We have a serious issue with hashequiv but a patch in progress for that. There is also a usability issue raised with hashequiv and this can only realistically be fixed in M4, it means changing the UI message handling within bitbake. * We continue to see automated test failures with master, most are long standing issues which we're struggling to resolve. A minority now have had their causes narrowed down or are now reproducible at will which should help but there is concern about the others. * Some recent changes like psplash systemd support have introduced a race causing intermittent build failures. We had thought those resolved but they reappeared after merging. * Alex Kanavin has quietly but very effectively been fixing ptest failures and we now have only a very small number of non-toolchain tests failing, thanks Alex! * 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). * 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 built and in QA * YP 2.7.3 release date 2/21/2020 * YP 3.0.2 release soon * YP 3.0.3 build date 5/4/2020 * YP 3.0.3 release date 5/15/2020 * YP 2.7.4 build date 5/18/2020 * YP 2.7.4 release date 5/29/2020 Tracking Metrics: * WDD 2665 (last week 2710) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1356 (last week 1360) * Patches in the Pending State: 543 (40%) [last week 546 (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_040F_01D5EBB0.E143B520 Content-Type: text/html; boundary="----=_NextPart_000_02BC_01D5E0B0.104D1250"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M3 - At Feature Freeze

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

 

Next Team = Meetings:

 

Key = Status/Updates:

  • YP 2.7.3 rc1 is in QA with the = report due next week.
  • YP 3.0.2 rc2 was rebuilt to = remove a broken bash CVE patch, rc3 had automated QA only and is now due = for release.
  • We are now at the date for M3 = which is feature freeze. We are not yet in a position where we can build = M3 as there are a number of open high blocking bugs but patches will = need to start tapering down to bug fix only. More invasive or unplanned = features will no longer be accepted.
  • We have a serious issue with = hashequiv but a patch in progress for that. There is also a usability = issue raised with hashequiv and this can only realistically be fixed in = M4, it means changing the UI message handling within = bitbake.
  • We continue to see automated = test failures with master, most are long standing issues which = we’re struggling to resolve. A minority now have had their causes = narrowed down or are now reproducible at will which should help but = there is concern about the others.
  • Some recent changes like = psplash systemd support have introduced a race causing intermittent = build failures. We had thought those resolved but they reappeared after = merging.
  • Alex Kanavin has quietly but = very effectively been fixing ptest failures and we now have only a very = small number of non-toolchain tests failing, thanks = Alex!
  • 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).
  • 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 built and in = QA
  • YP 2.7.3 release date = 2/21/2020
  • YP 3.0.2 release = soon
  • YP 3.0.3 build date  = 5/4/2020
  • YP 3.0.3 release date = 5/15/2020
  • YP 2.7.4 build date  = 5/18/2020
  • YP 2.7.4 release date = 5/29/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_040F_01D5EBB0.E143B520--