All,

YP M+ or high bugs which moved to a new milestone in WW19 are listed below:

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

All,

The below were the owners of enhancements or bugs closed during the last week!

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

All,

Below is the list as of top 50 bug owners as of the end of WW19 of who have open medium or higher bugs and enhancements against YP 3.2.   There are 120 possible work days left until the final release candidates for YP 3.2 needs to be released.

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

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 May 14th at 7:30am PDT (https://zoom.us/j/454367603)
• Monthly Project Meeting Tuesday june 2nd at 8am PDT (https://zoom.us/j/990892712)
• Weekly Engineering Sync Tuesday May 12th  at 8am PDT (https://zoom.us/j/990892712)
• Twitch -  See http://www.twitch.tv/letoatreidesthe2nd

Key Status/Updates:

• Patches continue to merge into master, there have been a number of infrastructure issues and build failures which have delayed some patches until we could get clean builds
• We’re nearly ready to merge gcc 10 to master with some mingw issues being the currently known remaining blocker.
• A number of other slightly more invasive changes are merging such as the changing of QA warnings to become errors and changes to the way libva is built. Some further, more invasive changes are in the queue (e.g. image sstate structure) so review of the patch queue by people with interests in these things is appreciated.
• We believe autoconf may release a new version soon (the first in a few years) so have worked with autoconf upstream to ensure it should work for us, reporting test results back.
• YP 3.0.3 will build this week.

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 3.0.3 build date 2020/5/4
• YP 3.0.3 release date 2020/5/15
• YP 2.7.4 build date 2020/5/18
• YP 2.7.4 release date 2020/5/29
• YP 3.1.1 build date 2020/6/29
• YP 3.1.1 release date 2020/7/10
• 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)
• Poky Patch Metrics  
• Total patches found: 1345 (last week 1353)
• Patches in the Pending State: 536 (40%) [last week 536 (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@...

I can’t reach http://downloads.yoctoproject.org/ to download http://downloads.yoctoproject.org/releases/uninative/2.7/x86_64-nativesdk-libc.tar.xz .

Did somebody know anything?

All,

The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 334 unassigned or newcomer bugs.

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.1”, “3.2, "3.99" and "Future", the more pressing/urgent issues being in "3.1" and then “3.2”.

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...