Yocto Project Status WW23'20

Yocto Project Status WW23'20

[Stephen Jolley]

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

Current Dev Position: YP 3.2 M1

Next Deadline: YP 3.2 M1 build date 2020/6/16

 

Next Team Meetings:

*	Bug Triage meeting Thursday June 11th at 7:30am PDT (
<https://zoom.us/j/454367603> https://zoom.us/j/454367603)
*	Monthly Project Meeting Tuesday July 7th at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Weekly Engineering Sync Tuesday June 9th  at 8am PDT (
<https://zoom.us/j/990892712> https://zoom.us/j/990892712)
*	Twitch -  See http://www.twitch.tv/letoatreidesthe2nd

 

Key Status/Updates:

*	YP 2.7.4 was released
*	YP 3.1.1 has been built with two issues being investigated before it
enters QA
*	A significant number of upgrades have merged into master and we are
up to date with a majority of recipes, particularly due work from Alex,
thanks! One which isn't and is looking slightly more problematic is the qemu
upgrade to 5.0.0, help would be welcome there.
*	YP 3.2 M1 is due to build next week so patches for M1 need to be
sent for review now in order to make it in.
*	We are struggling with maintainers for some key components of the
system/infrastructure such as devtool, wic, buildhistory and
patchwork/patchtest. If anyone can help in these areas please contact
Richard.
*	There remain a large number of bugs that we'd ideally like to fix in
3.2 M1 (or M2) but they are "unassigned", there is nobody to work on them.
If anyone has time, looking at these bugs would be a great way to help us.
See:
<https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enha
ncements.2FBugs>
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhan
cements.2FBugs

 

YP 3.2 Milestone Dates:

*	YP 3.2 M1 build date 2020/6/16
*	YP 3.2 M1 Release date 2020/6/26
*	YP 3.2 M2 build date 2020/7/27
*	YP 3.2 M2 Release date 2020/8/7
*	YP 3.2 M3 build date 2020/8/31
*	YP 3.2 M3 Release date 2020/9/11
*	YP 3.2 M4 build date 2020/10/5
*	YP 3.2 M4 Release date 2020/10/30

 

Planned upcoming dot releases:

*	YP 2.7.4 has been released
*	YP 3.1.1 build date 2020/6/09
*	YP 3.1.1 release date 2020/6/20
*	YP 3.0.4 build date 2020/8/10
*	YP 3.0.4 release date 2020/8/21
*	YP 3.1.2 build date 2020/9/14
*	YP 3.1.2 release date 2020/9/25

 

Tracking Metrics:

*	WDD 2577 (last week 2577) (
<https://wiki.yoctoproject.org/charts/combo.html>
https://wiki.yoctoproject.org/charts/combo.html)
*	Poky Patch Metrics  

*	Total patches found: 1301 (last week 1343)
*	Patches in the Pending State: 517 (40%) [last week 535 (40%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 <https://wiki.yoctoproject.org/wiki/TSC>
https://wiki.yoctoproject.org/wiki/TSC

 

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 Program Manager

*    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@gmail.com
<mailto:sjolley.yp.pm@gmail.com> 

 


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

Re: [OE-core] Yocto Project Status WW23'20

[Randy MacLeod]

On 2020-06-09 10:43 a.m., Stephen Jolley wrote:
> One which isn’t and is looking slightly more problematic is the qemu 
> upgrade to 5.0.0, help would be welcome there.

Sakib and Joe have worked on upreving qemu.
If things go well they'll send the uprev this week.

I wouldn't hold M1 for it.

-- 
# Randy MacLeod
# Wind River Linux

Re: [OE-core] Yocto Project Status WW23'20

[Randy MacLeod]

On 2020-06-14 8:32 p.m., Randy MacLeod wrote:
> On 2020-06-09 10:43 a.m., Stephen Jolley wrote:
>> One which isn’t and is looking slightly more problematic is the qemu 
>> upgrade to 5.0.0, help would be welcome there.
> 
> Sakib and Joe have worked on upreving qemu.
> If things go well they'll send the uprev this week.
> 
> I wouldn't hold M1 for it.
> 

We could send the update now since all the oe-core workflows
that we have run work fine but we did find a WR specific
test that is failing so we're going to resolve that first.

Richard,
Let us know if the YP AB is bored and you really want to
test the qemu update today rather than later this week
or early next week.

-- 
# Randy MacLeod
# Wind River Linux