Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status September 17, 2019 ==
== Yocto Project Weekly Status September 24, 2019 ==
Current Dev Position: YP 2.8 M4 Feature Freeze<br/>
Current Dev Position: YP 2.8 M4 Feature Freeze<br/>
Next Deadline: YP 3.0 Final Release 25th Oct<br/>
Next Deadline: YP 3.0 Final Release 25th Oct<br/>


'''SWAT Team Rotation:'''<br/>
'''SWAT Team Rotation:'''<br/>
*SWAT lead is currently: Paul
*SWAT lead is currently: Amanda
*SWAT team rotation: Ross -> Amanda on Sept. 20, 2019
*SWAT team rotation: Amanda -> Chen on Sept. 27, 2019
*SWAT team rotation: Amanda -> Chen on Sept. 13, 2019
*SWAT team rotation: Chen -> Armin on Oct. 4, 2019
*://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
*://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Sept 19th at 7:30am PDT (https://zoom.us/j/454367603)
*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)
*Monthly Project Meeting Tuesday Oct. 1st at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Sept. 17th at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Sept. 17th at 8am PDT (https://zoom.us/j/990892712)
Line 17: Line 17:
'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We’re now in feature freeze for 3.0 and working on bug fixing for final release
*We’re now in feature freeze for 3.0 and working on bug fixing for final release
*We have not built M3 yet as there are still three issues that need to be resolved:
*We have built M3 and this is due from QA on Thursday
**strace ptest regressions with 5.1/5.2 kernels
*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.
**systemd timeouts on mips
*We also want to find a better solution to the systemd timeout problem before final release.
**hashequiv server rewrite
*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 strace regressions will be discussed with the kernel community, the best workaround may be to lower the individual test timeouts so one the affected individual tests fail rather than all tests timing out.
*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.
*The qemumips issue with systemd is puzzling as its happening in hwdb and hwdb should be generated in advance anyway. Investigation is ongoing about why its being regenerated, a workaround is to increase the timeout as mips is just slow (it does complete eventually, its just marginal).
*The hashequiv server changes are being tested in master-next
It is planned to build M3 this week with the workarounds mentioned above worst case. Its expected there would be further hashequiv fixing during M4.
*We hope to make up time during M4 by having M3 at high quality and take advantage of our automation.
*Documentation - Due to illness Scott is unavailable for the next month or two so doc patches will be handled by Richard or Ross in the short term. We’ll likely limit them to correctness issues and defer any substantial new text. If anyone has availability and skills to work on the manuals please talk to us. We’re aware there is a patch backlog.
*If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+Stephen.
*If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+Stephen.



Revision as of 14:46, 24 September 2019

Yocto Project Weekly Status September 24, 2019

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
    //wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

Next Team Meetings:

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:

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

Archives