[OE-core] Yocto Project Status WW39’19

[ChenQi]

On 09/24/2019 10:50 PM, Stephen K Jolley wrote:
>
> Current Dev Position: YP 2.8 M4 Feature Freeze
>
> Next Deadline: YP 3.0 Final Release 25th Oct
>
>
> SWAT Team Rotation:
>
>  *
>
>     SWAT lead is currently: Amanda
>
>  *
>
>     SWAT team rotation: Amanda -> Chen on Sept. 27, 2019
>
>  *
>
>     SWAT team rotation: Chen -> Armin on Oct. 4, 2019
>
>  *
>
>     https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
>
>

Hi Armin and Anju,

I want to switch the rotation with you two.
Because Oct. 1st is our National Day. We'll have a one-week holiday to 
celebrate it.

I've updated 
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team#Members 
for now.
If you have any concern, please let me know.
Thanks in advance.

Best Regards,
Chen Qi



> Next Team Meetings:
>
>  *
>
>     Bug Triage meeting Thursday Sept 26th at 7:30am PDT
>     (https://zoom.us/j/454367603)
>
>  *
>
>     Monthly Project Meeting Tuesday Oct. 1st at 8am PDT
>     (https://zoom.us/j/990892712) <https://zoom.us/j/990892712>
>
>  *
>
>     Weekly Engineering Sync Tuesday Sept. 24th at 8am PDT
>     (https://zoom.us/j/990892712) <https://zoom.us/j/990892712>
>
>  *
>
>     Twitch - Next event is Tuesday Octt. 8th at 8am PDT
>     (https://www.twitch.tv/yocto_project)
>
>
> Key Status/Updates:
>
>  *
>
>     We’re now in feature freeze for 3.0 and working on bug fixing for
>     final release
>
>  *
>
>     We have built M3 and this is due from QA on Thursday
>
>  *
>
>     The main unresolved issue for 3.0 is with the hash equivalence
>     server causing problems with the eSDK and this issue is being
>     investigated but can’t be reproduced as yet.
>
>  *
>
>     We also want to find a better solution to the systemd timeout
>     problem before final release.
>
>  *
>
>     A significant performance problem has been found on the
>     autobuilder where some builds are scaling in time badly as the
>     sstate cache grows, taking 12 hours or more in some cases.
>     Unfortunately nobody seems motivated to help work on this kind of
>     issue.
>
>  *
>
>     The plan for M4 is to resolve the above issues and any issues
>     raised from M3 QA, then proceed with the main release rc builds.
>     The first M4 build is scheduled for next week.
>
>  *
>
>     If anyone has any status items for the project they’d like to add
>     to the weekly reports, please email Richard+Stephen.
>
>
> Planned Releases for YP 3.0 {2.8}:
>
>  *
>
>     M3 Release 6th Sept
>
>  *
>
>     M4 Cutoff 30th Sept - this will be YP 3.0.
>
>  *
>
>     YP 3.0 {2.8 (M4)} Final Release 25th Oct
>
>
> Planned upcoming dot releases:
>
>  *
>
>     YP 2.7.2 (Warrior) is planned for after YP 3.0 release.
>
>  *
>
>     YP 2.6.4 (Thud) is planned for after YP 2.7.2  release.
>
>
> Tracking Metrics:
>
>  *
>
>     WDD 2505 (last week
>     2449)(https://wiki.yoctoproject.org/charts/combo.html)
>
>  *
>
>     Poky Patch Metrics
>
>      o
>
>         Total patches found: 1427 (last week 1424)
>
>      o
>
>         Patches in the Pending State: 587 (41%) [last week 587 (41%)]
>
>
> Key Status Links for YP:
>
> https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule
>
> https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features
>
>
> 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*
>
> *7867 SW Bayberry Dr., Beaverton, OR 97007*
>
> (*Cell*: (208) 244-4460
>
> * *Email*:_stephen.k.jolley at intel.com <mailto:stephen.k.jolley at intel.com>_
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20190925/4a677455/attachment-0001.html>