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 829107FED5 for ; Tue, 28 Jan 2020 16:01:23 +0000 (UTC) Received: by mail-pl1-f180.google.com with SMTP id p9so5245282plk.9 for ; Tue, 28 Jan 2020 08:01:24 -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=sYWeR3ezj3oL9wil8SEzplxfIicvA+XAB3wv0ShV1mY=; b=hv9WQWQdhxxhBQCOU99BdHYv1TfxcJ6GuVht4LnqVZ+3I1N6E84V5FD8LbIFbrSGoo 2NeqDcGyc40CGRbWwIv8FWtsY8EioEpcNEeeSWsCNc9XAKLweVvMUsJalQO+oAQFhTwD Es2x9OJ0j45Ym4oSJs/LK060MD8Od4iB/rWBnQm9yTDk+DSJe/QpQtL9xbnMEDeFHw5G xgo8qkzbXISCO2JraDsFukLXN83lcsOSPwmT7vlTWuxdZNpamMABwT/MERpkYVx8/zJJ EMbvxGDJG1nKwTD8YWMu6bbNaYURkwQJsgSO0Lykg3/ekpupSl/kiNCnZAakV9KEh6US e2ww== 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=sYWeR3ezj3oL9wil8SEzplxfIicvA+XAB3wv0ShV1mY=; b=uibmJnkSB0ZgtxSwp/biRM8fvn0NeWCw5oyuuDMIKkUaUto1XtTSYmpnYMCR9odW1k b0a6gu5DScuD0eNJRMo4gtNLIbbMapWBAKHLMjPk7fY2gXakNmVLkNcU3IXKvwzEl20h w6h4v9h80KEqrSKKBRxJbN7AaQwP0HLlXjkZ5lHHohqHw0t4t9wdiivxg9GnuH+kUcoK oUPTkFzLloKIlMq9wozR3xpn9nuV9J2oE5yRqqB6NBNfsJp07OcLrBbTR8PhZu3u4pJH shI2erJnYFcgRiq1hQBarnC/yej5fbWX5nHg9DtLtu2teC0JPAGjwDMpDFXu3g09FUXx 5d2g== X-Gm-Message-State: APjAAAV8E7QiSPeO+yIg82g+IFFmffaofkHnj9A5kyznpO9dQNtcQ7Uz nNVyw0IpWhS+92xwjw2xGxw= X-Google-Smtp-Source: APXvYqycosbTpY1Y+mrmsGBp0Uy8YGG37/SsdNoJpA/TRN7fxfbONIOHPJylkv/78+YFirflMf0+qA== X-Received: by 2002:a17:902:82c3:: with SMTP id u3mr22317578plz.73.1580227284206; Tue, 28 Jan 2020 08:01:24 -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 o11sm3325251pjs.6.2020.01.28.08.01.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Jan 2020 08:01:23 -0800 (PST) From: To: , Date: Tue, 28 Jan 2020 08:01:23 -0800 Message-ID: <086201d5d5f4$307b2150$917163f0$@gmail.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQLrhc3H6Rfbraq9lZI/TYNyHvpX+g== Subject: Yocto Project Status WW04'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, 28 Jan 2020 16:01:23 -0000 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0863_01D5D5B1.225AC780" Content-Language: en-us ------=_NextPart_000_0863_01D5D5B1.225AC780 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Current Dev Position: YP 3.1 M3 Next Deadline: YP 3.1 M2 in QA - release 1/31/20 Next Team Meetings: * Bug Triage meeting Thursday Jan. 30th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Feb. 4th at 8am PDT ( https://zoom.us/j/990892712) * Weekly Engineering Sync Tuesday Jan. 28th at 8am PDT ( https://zoom.us/j/990892712) * Twitch - Next event is Tuesday Feb. 11th at 8am PDT ( https://www.twitch.tv/yocto_project) Tip of the Week: * The scripts in ${WORKDIR}/temp/run.XXX for shell tasks can be quickly hacked and used for standalone debugging by replacing the function call at the end with "bash -i" which will then drop you into a shell environment matching the task being debugged (minus the fakeroot context). * Bonus marks for anyone sending a patch to add the fakeroot context as comments at the start of the scripts. * (send any tips you'd like to see here to Stephen or Richard) Key Status/Updates: * YP 3.1 M2 is in QA but has issues with build reproducibility * We're unlikely to rebuild M2 as master has the same issues and they look like they will take a while to resolve. * There are now serious problems with the build reproducibility test failures on the autobuilder. We're not sure why there is a sudden set of problems but they are real issues and causing most builds to fail. The tests will have to be disabled unless they can be resolved quickly. There are fixes merged for the CONFIG_SHELL issue and kbd and patches queued as a potential fix for makeinfo. There are more remaining issues, some have open bugs, others don't have bugs yet. Help with any of these would be appreciated (or help filing the bugs). * 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). * We have created a "documentation" list and a "licensing" list on the yocto project mailing list infrastructure. We believe these topics would benefit from dedicated discussions, the people involved usually aren't interested in bulk email as would be found on other lists. The new lists can be found at: https://lists.yoctoproject.org/g/licensing/join and https://lists.yoctoproject.org/g/docs/join * There is continued concern about the number of recurring/intermittent failures in the automated testing, mostly from selftest and testimage. * We continue to struggle to get clean 'full' builds due to the reproducibility issues in particular. * 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 M2 release date 1/31/2020 * 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 2765 (last week 2758) ( https://wiki.yoctoproject.org/charts/combo.html) * Poky Patch Metrics * Total patches found: 1368 (last week 1357) * Patches in the Pending State: 545 (40%) [last week 536 (39%)] 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_0863_01D5D5B1.225AC780 Content-Type: text/html; boundary="----=_NextPart_000_0C39_01D5D02F.61303FD0"; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Current Dev = Position: YP 3.1 M3

Next Deadline: YP = 3.1 M2 in QA - release 1/31/20

 

Next Team = Meetings:

 

Tip of the = Week:

  • The scripts in = ${WORKDIR}/temp/run.XXX for shell tasks can be quickly hacked and used = for standalone debugging by replacing the function call at the end with = “bash -i” which will then drop you into a shell environment = matching the task being debugged (minus the fakeroot = context). 
  • Bonus marks for anyone sending = a patch to add the fakeroot context as comments at the start of the = scripts.
  • (send any tips you’d like = to see here to Stephen or Richard)

 

Key = Status/Updates:

  • YP 3.1 M2 is in QA but has = issues with build reproducibility
  • We’re unlikely to rebuild = M2 as master has the same issues and they look like they will take a = while to resolve.
  • There are now serious problems = with the build reproducibility test failures on the autobuilder. = We’re not sure why there is a sudden set of problems but they are = real issues and causing most builds to fail. The tests will have to be = disabled unless they can be resolved quickly. There are fixes merged for = the CONFIG_SHELL issue and kbd and patches queued as a potential fix for = makeinfo. There are more remaining issues, some have open bugs, others = don’t have bugs yet. Help with any of these would be appreciated = (or help filing the bugs).
  • 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).
  • We have created a = “documentation” list and a “licensing” list on = the yocto project mailing list infrastructure. We believe these topics = would benefit from dedicated discussions, the people involved usually = aren’t interested in bulk email as would be found on other lists. = The new lists can be found at: https://lists.yoctoproject.org/g/licensing/join and https://lists.yoctoproject.org/g/docs/join=  
  • There is continued concern = about the number of recurring/intermittent failures in the automated = testing, mostly from selftest and testimage.
  • We continue to struggle to get = clean ‘full’ builds due to the reproducibility issues in = particular.
  • 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 M2 release date = 1/31/2020
  • 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_0863_01D5D5B1.225AC780--