Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status March, 5, 2019 ==
== Yocto Project Weekly Status March, 12, 2019 ==
Current Dev Position: YP 2.7 M3 <br/>
Current Dev Position: YP 2.7 M3 <br/>
Next Deadline: YP 2.7 M3 Cutoff was Mar. 5, 2019<br/>
Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019<br/>


'''SWAT Team Rotation:'''<br/>
'''SWAT Team Rotation:'''<br/>


*SWAT lead is currently: Chen
*SWAT lead is currently: Anuj  
*SWAT team rotation: Chen -> Anuj on Mar. 8, 2019
*SWAT team rotation: Anuj -> Armin on Mar. 15, 2019
*SWAT team rotation: Anuj -> Armin on Mar. 15, 2019
*SWAT team rotation: Armin -> Paul on Mar. 23, 2019
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
*https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.7 M2 rc2 is being released today Mar. 5, 2019.
*YP 2.7 M2 rc2 was released on May 5, 2019.
*YP 2.7 M3 has not yet been built but progress has been made in resolving several issues:
*We believe we now have all the key components for 2.7M3 in master-next but have not completed a successful test run with this. In addition to the list last week, this means M3 will include:
**bug 13178 “X server and matchbox desktop don't start up properly on beaglebone” was fixed
**5.0 kernel
**multiconfig bugs have been fixed and a test case added
**qemuarm transition to armv7
**qemu virgl code and selftests have been added (not enabled as default)
**Busybox full replacement utils
**qemu native build was split into user and system components
*Some invalid source revisions tested in master-next have broken the autobuilder causing build hangs and failures. With travel and other distractions, nobody is available to dive in and debug this immediately so it will block M3.
**lttng-tools ptest timeout fixed
*We also want to complete the transition to the new QA process and test this for M3. Aproov is going to send out details of this imminently, we believe the main code work is complete and its process/documentation that remains. We will block on this as we want to use the new QA process for M3 and the final 2.7 release.
**systemd version upgrade
*YP 2.5.3 continues to be blocked on autobuilder-helper changes for the stable branches and the resulttool changes in master to move to the new QA process.
**ltp recipe version upgrade
**perl ptest regressions fixed
*The list of remaining potential items for M3 is:
**5.0 linux kernel (and libc headers) (Bruce)
**qemuarm to v7 changes (Jon)
**Aarch64 build host support finalization (Jon)
**Busybox ‘full’ utility replacement (Tom)
*YP 2.5.3 is nearly ready for building however the autobuilder-helper changes need to be resolved for the stable branches, as do the resulttool changes in master to move to the new QA process.


'''Planned Releases for YP 2.7:'''<br/>
'''Planned Releases for YP 2.7:'''<br/>
*YP 2.7 M2 Released Mar. 5, 2019
*YP 2.7 M3 Cutoff is Feb. 25, 2019
*YP 2.7 M3 Cutoff is Feb. 25, 2019
*YP 2.7 M3 Release Target is Mar. 8, 2019
*YP 2.7 M3 Release Target is Mar. 8, 2019
Line 41: Line 32:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2436 (last week 2415) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2439 (last week 2436) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1502 (last week 1516)
**Total patches found: 1523 (last week 1502)
**Patches in the Pending State: 658 (44%) [last week 660 (44%)]
**Patches in the Pending State: 657 (43%) [last week 658 (44%)]


'''Key Status Links for YP:'''<br/>
'''Key Status Links for YP:'''<br/>

Revision as of 16:03, 12 March 2019

Yocto Project Weekly Status March, 12, 2019

Current Dev Position: YP 2.7 M3
Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019

SWAT Team Rotation:

Key Status/Updates:

  • YP 2.7 M2 rc2 was released on May 5, 2019.
  • We believe we now have all the key components for 2.7M3 in master-next but have not completed a successful test run with this. In addition to the list last week, this means M3 will include:
    • 5.0 kernel
    • qemuarm transition to armv7
    • Busybox full replacement utils
  • Some invalid source revisions tested in master-next have broken the autobuilder causing build hangs and failures. With travel and other distractions, nobody is available to dive in and debug this immediately so it will block M3.
  • We also want to complete the transition to the new QA process and test this for M3. Aproov is going to send out details of this imminently, we believe the main code work is complete and its process/documentation that remains. We will block on this as we want to use the new QA process for M3 and the final 2.7 release.
  • YP 2.5.3 continues to be blocked on autobuilder-helper changes for the stable branches and the resulttool changes in master to move to the new QA process.

Planned Releases for YP 2.7:

  • YP 2.7 M3 Cutoff is Feb. 25, 2019
  • YP 2.7 M3 Release Target is Mar. 8, 2019
  • YP 2.7 M4 Cutoff is Apr. 1, 2019
  • YP 2.7 M4 Release Target is Apr. 26, 2019

Planned upcoming dot releases:

  • YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
  • YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 is done.
  • YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.

Tracking Metrics:

Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=49449"