Yocto Project Status WW07'19

Yocto Project Status WW07'19

[sjolley.yp.pm]

[-- Attachment #1: Type: text/plain, Size: 4419 bytes --]

Current Dev Position: YP 2.7 M3

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

 

SWAT Team Rotation:

*	SWAT lead is currently: Paul 
*	SWAT team rotation: Paul -> Ross on Feb. 15, 2019
*	SWAT team rotation: Ross -> Amanda on Feb. 22, 2019
*	 <https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team>
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Key Status/Updates:

*	YP M2 rc1 had major problems in perl as fallout from the perl
upgrade and switch to perl-cross. We've therefore built an rc2 based on a
more recent master.
*	The python upgrade to 3.7 merged, thanks to AlexK for his hard work
on this. It means all of the major components in OE-Core are finally up to
date (many minor versions are still adrift).
*	Major util-linux changes have just merged which should hopefully
allow easier long term maintenance of this recipe (all binaries now have
their own package, this recipe kept being split up)
*	Build performance tests on the autobuilder have been improved and
builds now have automated result comparisons, e.g.:
<https://autobuilder.yocto.io/pub/non-release/20190212-7/testresults/buildpe
rf-ubuntu1604/perf-ubuntu1604_master_20190212045844_be52da1.html>
https://autobuilder.yocto.io/pub/non-release/20190212-7/testresults/buildper
f-ubuntu1604/perf-ubuntu1604_master_20190212045844_be52da1.html (from
<https://autobuilder.yoctoproject.org/typhoon/#/builders/92/builds/101>
https://autobuilder.yoctoproject.org/typhoon/#/builders/92/builds/101)
(Thanks to Markus for a lot of the underlying code/work)
*	Build performance can now compare master to master-next test builds
*	We continue to need help with ptest, both on the tests themselves
and on the results reporting. The intent is to have something similar to the
build performance pieces above.
*	The recipe reporting system integration with the layer index is
available at:  <https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/>
https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the
historical data has now been imported.
*	The project is considering moving its mailing list hosting to
groups.io, if anyone has any experience of that, positive or negative please
let Michael, Nico and Richard know. Note that google has made further
significant changes to its mail processing at the detriment to mailing
lists:
<https://lists.freedesktop.org/archives/freedesktop/2019-February/000396.htm
l>
https://lists.freedesktop.org/archives/freedesktop/2019-February/000396.html
*	If anyone has feedback about the maintainers/recipe upgrade
processes or how to attract new recipe maintainers, please talk to Richard
Purdie / Ross Burton

 

Planned Releases for YP 2.7:

*	YP 2.7 M2 is being rebuilt and will go back to QA for rc2.
*	YP 2.7 M2 Release Target is Feb. 1, 2019
*	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 2353 (last week 2356) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
*	Poky Patch Metrics  

*	Total patches found: 1527 (last week 1572
*	Patches in the Pending State: 663 (43%) [last week 678 (43%)]

 

Key Status Links for YP:

 <https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status>
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_Schedule

 <https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features>
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>
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
<mailto:sjolley.yp.pm@gmail.com> 

 


[-- Attachment #2: Type: text/html, Size: 36388 bytes --]

Re: Yocto Project Status WW07'19

[Alexander Kanavin]

On Tue, 12 Feb 2019 at 17:10, <sjolley.yp.pm@gmail.com> wrote:
> The recipe reporting system integration with the layer index is available at: https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the historical data has now been imported.

Sadly the new RRS still seems to be suffering from the 'outdated info'
problem. For example glibc, or python3 recipes have been updated to
latest versions, yet RRS still shows that they haven't been.

Alex

Re: Yocto Project Status WW07'19

[Paul Eggleton]

Hi Alex

On Wednesday, 13 February 2019 6:22:23 AM NZDT Alexander Kanavin wrote:
> On Tue, 12 Feb 2019 at 17:10, <sjolley.yp.pm@gmail.com> wrote:
> > The recipe reporting system integration with the layer index is available
> > at: https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the
> > historical data has now been imported.
> 
> Sadly the new RRS still seems to be suffering from the 'outdated info'
> problem. For example glibc, or python3 recipes have been updated to
> latest versions, yet RRS still shows that they haven't been.

We're reliant upon the layer index updating and it appears that's not working 
at the moment. I have asked Michael to look into it. Thanks for the report, 
I'll reply back here when things are sorted out.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Yocto Project Status WW07'19

[Michael Halstead]

The regular 3 hour update wasn't installed on the new server. I have 
repaired that and added the RRS updates as well..

The update has been run several times in testing and I'm curious if RRS 
has caught up as expected.

On 2/12/19 5:57 PM, Paul Eggleton wrote:
> Hi Alex
>
> On Wednesday, 13 February 2019 6:22:23 AM NZDT Alexander Kanavin wrote:
>> On Tue, 12 Feb 2019 at 17:10, <sjolley.yp.pm@gmail.com> wrote:
>>> The recipe reporting system integration with the layer index is available
>>> at: https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the
>>> historical data has now been imported.
>> Sadly the new RRS still seems to be suffering from the 'outdated info'
>> problem. For example glibc, or python3 recipes have been updated to
>> latest versions, yet RRS still shows that they haven't been.
> We're reliant upon the layer index updating and it appears that's not working
> at the moment. I have asked Michael to look into it. Thanks for the report,
> I'll reply back here when things are sorted out.
>
> Cheers,
> Paul
>
-- 
Michael Halstead
Linux Foundation / SysAdmin

Re: Yocto Project Status WW07'19

[Alexander Kanavin]

I think it looks right now, thanks :)

Alex

On Thu, 14 Feb 2019 at 10:13, Michael Halstead
<mhalstead@linuxfoundation.org> wrote:
>
> The regular 3 hour update wasn't installed on the new server. I have
> repaired that and added the RRS updates as well..
>
> The update has been run several times in testing and I'm curious if RRS
> has caught up as expected.
>
> On 2/12/19 5:57 PM, Paul Eggleton wrote:
> > Hi Alex
> >
> > On Wednesday, 13 February 2019 6:22:23 AM NZDT Alexander Kanavin wrote:
> >> On Tue, 12 Feb 2019 at 17:10, <sjolley.yp.pm@gmail.com> wrote:
> >>> The recipe reporting system integration with the layer index is available
> >>> at: https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the
> >>> historical data has now been imported.
> >> Sadly the new RRS still seems to be suffering from the 'outdated info'
> >> problem. For example glibc, or python3 recipes have been updated to
> >> latest versions, yet RRS still shows that they haven't been.
> > We're reliant upon the layer index updating and it appears that's not working
> > at the moment. I have asked Michael to look into it. Thanks for the report,
> > I'll reply back here when things are sorted out.
> >
> > Cheers,
> > Paul
> >
> --
> Michael Halstead
> Linux Foundation / SysAdmin
>