Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status March, 12, 2019 ==
== Yocto Project Weekly Status March, 19, 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 Feb. 25, 2019<br/>
Next Deadline: YP 2.7 M3 Cutoff was Feb. 25, 2019<br/>
Line 5: Line 5:
'''SWAT Team Rotation:'''<br/>
'''SWAT Team Rotation:'''<br/>


*SWAT lead is currently: Anuj
*SWAT lead is currently: Armin  
*SWAT team rotation: Anuj -> Armin on Mar. 15, 2019
*SWAT team rotation: Armin -> Paul on Mar. 23, 2019
*SWAT team rotation: Armin -> Paul on Mar. 23, 2019
*SWAT team rotation: Paul -> Ross on Mar. 30, 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 was released on May 5, 2019.
*M3 has not built yet however most major pieces are in place, including now, agreement on the new QA process. The delay is partly due to RP travel with others able to cover being unavailable for other reasons, combined with infrastructure 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:
*The remaining questions for M3 are:
**5.0 kernel
**Public documentation of the new QA process
**qemuarm transition to armv7
**Upgrade for uninative for glibc 2.29
**Busybox full replacement utils
**Mesa upgrade? (unlikely given failures in testing)
*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.
*The Yocto Project has updated to its new governance model which includes establishing a Technical Steering Committee (TSC) for Yocto Project. This is designed to complement  and work alongside the OpenEmbedded TSC. Three members of the YP TSC are selected by the Yocto Project governing board and those people are Ross Burton, Khem Raj and Richard Purdie. The remaining two seats will be elected by OpenEmbedded. It is intended the TSC will take over the release process, SWAT team, bug triage and feature planning/development for 2.8.
*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.
*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.
*There is discussion on the openembedded-architecture list about changes to the stable branch patch criteria to bring us more into line with current industry best practises and thinking.


'''Planned Releases for YP 2.7:'''<br/>
'''Planned Releases for YP 2.7:'''<br/>
*YP 2.7 M3 Cutoff is Feb. 25, 2019
*YP 2.7 M3 Cutoff was Feb. 25, 2019
*YP 2.7 M3 Release Target is Mar. 8, 2019
*YP 2.7 M3 Release Target was Mar. 8, 2019
*YP 2.7 M4 Cutoff is Apr. 1, 2019
*YP 2.7 M4 Cutoff is Apr. 1, 2019
*YP 2.7 M4 Release Target is Apr. 26, 2019
*YP 2.7 M4 Release Target is Apr. 26, 2019


'''Planned upcoming dot releases:'''<br/>
'''Planned upcoming dot releases:'''<br/>
*YP 2.5.3 (Sumo) will be targeted after YP 2.7 M2 is done.
*YP 2.5.3 (Sumo) will be targeted after YP 2.7 M3 is done.
*YP 2.5.4 (Sumo) will be targeted after YP 2.7 M4 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.
*YP 2.6.2 (Thud) will be targeted after YP 2.5.4 is done.


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


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

Revision as of 14:48, 19 March 2019

Yocto Project Weekly Status March, 19, 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:

  • M3 has not built yet however most major pieces are in place, including now, agreement on the new QA process. The delay is partly due to RP travel with others able to cover being unavailable for other reasons, combined with infrastructure issues.
  • The remaining questions for M3 are:
    • Public documentation of the new QA process
    • Upgrade for uninative for glibc 2.29
    • Mesa upgrade? (unlikely given failures in testing)
  • The Yocto Project has updated to its new governance model which includes establishing a Technical Steering Committee (TSC) for Yocto Project. This is designed to complement and work alongside the OpenEmbedded TSC. Three members of the YP TSC are selected by the Yocto Project governing board and those people are Ross Burton, Khem Raj and Richard Purdie. The remaining two seats will be elected by OpenEmbedded. It is intended the TSC will take over the release process, SWAT team, bug triage and feature planning/development for 2.8.

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.

  • There is discussion on the openembedded-architecture list about changes to the stable branch patch criteria to bring us more into line with current industry best practises and thinking.

Planned Releases for YP 2.7:

  • YP 2.7 M3 Cutoff was Feb. 25, 2019
  • YP 2.7 M3 Release Target was 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 M3 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=49778"