[OE-core] Yocto Project Status WW31’18

[Jolley, Stephen K]

Current Dev Position: YP 2.6 M3.

Next Deadline: YP 2.6 M2 Release Target was July 27, 2018


SWAT Team Rotation:

·         SWAT lead is currently: Tracy

·         SWAT team rotation: Tracy -> Armin on Aug. 3, 2018

·         SWAT team rotation: Armin -> Maxin on Aug. 10, 2018

·         https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


Project Announcements:


There has been various changes in the project recently which have caused concern for some users and contributors. It is worth highlighting the recent news that:

·         The Yocto Project recently welcomed two new platinum members, Facebook and Arm to the advisory board

·         Richard Purdie is being funded by the project to continue in his role as the overall project architect, currently for a three month period whilst governance is discussed.

·         Nicolas Dechesne (Linaro) has taken over the community manager role from Jefro

·         Lieu Ta (WindRiver) has taken over the advisory board chairperson role from Jefro

·         Andreea Volosincu (WindRiver) has taken on the advocacy lead role from Tracey Erway

·         Discussions about the future governance of the project with a view to modernisation and clarification are now ongoing but are based upon the strong foundations above.

Key Status/Updates:

·         YP 2.6 M2 is in QA. See https://wiki.yoctoproject.org/wiki/2.6_QA_Status.  It is 98% complete and should complete this week.

·         YP 2.2.4 has been released.  This is the final release of the YP 2.2 (morty) series.

·         We are about to build 2.5.1 (sumo) after M2 completes QA.

·         The races in oe-selftest parallelisation are now mostly resolved and we will be able to use it by default with master. We had a record 30 minute oe-selftest run with hot sstate  (compared with 13 hours at its worst with cold sstate and no parallelism).

·         Multiconfig dependencies looks ready to merge (thanks Alejandro/Xlinx).

·         The layerindex library code from Mark/Windriver needs close review as it builds API any setup tool would rely upon.

·         The sstate equivalency server work from Joshua/Garmin needs review

·         The kernel-devsrc rework from Bruce/Windriver is hopefully ready to go in now multilib issues that were stopping it have been resolved.

·         Uninative 2.2 was released. There was a critical bug found in the first attempt and a patch was reverted to allow the release. This releases fixes build issues with newer distros.


Planned Releases for YP 2.6:

·         YP 2.6 M2 Build is in QA.

·         YP 2.6 M2 Release Target was July 27, 2018

·         YP 2.6 M3 Build Target is Aug. 27, 2018

·         YP 2.6 M3 Release Target is Sept. 7, 2018

·         YP 2.6 M4 Build Target is Oct. 1, 2018

·         YP 2.6 M4 Release Target is Oct. 26, 2018


Planned upcoming dot releases:

·         YP 2.5.1 (Sumo) will be targeted after YP 2.6 M2 is done.

·         YP 2.4.4 (Rocko) will be targeted after YP 2.6 M4 is done.

·         YP 2.5.2 (Sumo) will be targeted after YP 2.4.4 is done.


Tracking Metrics:

·         WDD 2620 (last week 2618) (https://wiki.yoctoproject.org/charts/combo.html)

·         Poky Patch Metrics

o    Total patches found: 1619 (last week 1619)

o    Percentage of patches in the Pending State: 740 (46%) [last week 762 (46%)]


Key Status Links for YP:

https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.6_Status

https://wiki.yoctoproject.org/wiki/Yocto_2.6_Schedule

https://wiki.yoctoproject.org/wiki/Yocto_2.6_Features


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
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
•    Cell:                (208) 244-4460
• Email:                             stephen.k.jolley at intel.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20180731/504870f4/attachment-0002.html>