Re: [yocto] Yocto Project Status WW03'20

["akuster" <akuster808@gmail.com>]

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



On 1/14/20 7:52 AM, Stephen Jolley wrote:
>
> Current Dev Position: YP 3.1 M2
>
> Next Deadline: YP 3.1 M2 build date 1/20/2020
>
>  
>
> Next Team Meetings:
>
>   * Bug Triage meeting Thursday Jan. 16th  at 7:30am PDT
>     (https://zoom.us/j/454367603)
>   * Monthly Project Meeting Tuesday Feb. 4th  at 8am PDT
>     (https://zoom.us/j/990892712) <https://zoom.us/j/990892712>
>   * Weekly Engineering Sync Tuesday Jan. 14th at 8am PDT
>     (https://zoom.us/j/990892712) <https://zoom.us/j/990892712>
>   * Twitch - Next event is Tuesday Jan. 14th at 8am PDT
>     (https://www.twitch.tv/yocto_project)
>
>  
>
> Tip of the Week:
>
>   * ‘oe-pkgdata-browser’ is a new handy small helper UI added by Ross
>     to visualise the pkgdata held within a build.
>   * (anyone with tips they’d like to see here, please send to Stephen
>     or Richard)
>
>  
>
> Key Status/Updates:
>
>   * YP 3.1 M2 is due to be built next week.
>   * Patch merging is roughly on track however there are a number of
>     failures identified with key patches (glibc has a prelink issue on
>     mips, python 3.8 upgrade blocked on uid issue, gstreamer meson
>     transition blocked on nodistro failure). Most of these issues are
>     making progress over time.
>   * The more worrying aspect is that there are a number of
>     recurring/intermittent failures in the automated testing, mostly
>     from selftest and testimage.
>   * Looking at the build history, “full” images have built cleanly
>     only once in the past month (3 times in the last two months),
>     which is a pretty shocking statistic which summarises the
>     challenges we face there. Most of these are being procrastinated
>     on by the bug owners since we can’t reproduce them at will. We
>     really need help working on these kinds of issues.
>   * We have changed the sstate mirrors to be per release, simply to
>     lower the numbers of files in any given sstate directory.
>   * 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 build date 1/20/2020
>   * 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
>
New set of warrior patches sent out for review.


>  *
>
>
>
>   * YP 3.0.2 build date  2/3/2020
>   * YP 3.0.2 release date 2/14/2020
>
Back porting the remaining hash equivalence patches.

Do have some build failures that also affecting Master.

Will send out a call for patches sometime the end of next week.

Do we hold up the dot release if we add a new host?

- armin
>
>  *
>
>  
>
> Tracking Metrics:
>
>   * WDD 2772 (last week
>     2773)(https://wiki.yoctoproject.org/charts/combo.html)
>   * Poky Patch Metrics  
>       o Total patches found: 1411 (last week 1400)
>       o Patches in the Pending State: 562 (40%) [last week 562 (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 Project Manager*
>
> (    *Cell*:                (208) 244-4460
>
> * *Email*:              _sjolley.yp.pm@gmail.com
> <mailto:sjolley.yp.pm@gmail.com>_
>
>  
>
>
> 


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