Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status December 10, 2019 ==
== Yocto Project Weekly Status December 17, 2019 ==
Current Dev Position: YP 3.1 M1 <br/>
Current Dev Position: YP 3.1 M2 <br/>
Next Deadline: YP 3.1 M1 build Dec. 2, 2019<br/>
Next Deadline: YP 3.1 M2 build date 1/20/2020<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Dec. 12th at 7:30am PDT (https://zoom.us/j/454367603)
*Bug Triage meeting Thursday Dec. 19th at 7:30am PDT (https://zoom.us/j/454367603)
*Monthly Project Meeting Tuesday  Jan. 7th  at 8am  PDT (https://zoom.us/j/990892712)
*Monthly Project Meeting Tuesday  Jan. 7th  at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Dec. 10th at 8am PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Dec. 17th at 8am PDT (https://zoom.us/j/990892712)
*Twitch - Next event is Tuesday Dec. 17th at 8am PDT (https://www.twitch.tv/yocto_project)
*Twitch - Next event is Tuesday Dec. 17th at 8am PDT (https://www.twitch.tv/yocto_project)


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.0.1 was released.
*YP 3.0.1 was released.
*Python 2.x has been removed from HOSTTOOLS so OE-Core is python2 use free.
*YP 3.1 M1 rc8 is in QA
*Hash Equivalency has been enabled by default for poky using a local server.
*YP 3.1 M1 took a record number of build attempts due to various issues which only appeared during the rc builds.
*YP 3.1 M1 was due to be built but issues have been encountered in the release builds, both with previously unseen hash equivalence issue and a ptest performance regression on the autobuilders. Both issues are being worked on but are further delaying a successful M1 build.
*Despite a successful rc8 build (which still had reproducible build test failures) there are a number of concerns, particularly as there appears to be very slow builds for some ‘pathological’ hashequiv scenarios. There has been some progress over the weekend on identifying the causes of that and partially addressing them.
*Intermittent build failures continue to hamper builds, particularly combined with the above issues and as few people are available to attempt to debug and resolve them.
*There remains a growing set of intermittent autobuilder failures which occur with varying frequencies. We’re struggling to find anyone with time/interest to resolve these and they are becoming problematic for reviewing/testing patches and  triaging builds.
*Patch review and testing has run into new issues with a number of regressions from upgrades causing instability. Most of these were isolated pre-merge but not all.
*The TSC is working on LTS plans, productive discussions have been had and a new policy on handling this and stable releases should be available in the coming weeks.
*The TSC is working on LTS plans, productive discussions have been had and a new policy on handling this and stable releases should be available in the coming weeks.
*We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
*We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
*If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard and Stephen.
*Due to holidays in EU/US, the next status report will be sent in early January (likely 7th). If there is anything critical to report this will happen as needed.


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Proposed YP 3.1 Milestone Dates'''<br/>
*YP 3.1 M1 build date 12/2/2019
*YP 3.1 M1 is in QA
*YP 3.1 M1 release date 12/13/2019
*YP 3.1 M1 release date 12/13/2019
*YP 3.1 M2 build date 1/20/2020
*YP 3.1 M2 build date 1/20/2020
Line 31: Line 30:


'''Planned upcoming dot releases:'''<br/>
'''Planned upcoming dot releases:'''<br/>
*YP 3.0.1 is released.
*YP 2.7.3 build date  2/10/20
*YP 2.7.3 build date  2/10/20
*YP 2.7.3 release date 2/21/20
*YP 2.7.3 release date 2/21/20
Line 38: Line 36:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2698 (last week 2620) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2718 (last week 2698) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1410 (last week 1444)
**Total patches found: 1410 (last week 1410)
**Patches in the Pending State: 564 (40%) [last week 571 (40%)]
**Patches in the Pending State: 564 (40%) [last week 564 (40%)]


'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>

Revision as of 16:04, 17 December 2019

Yocto Project Weekly Status December 17, 2019

Current Dev Position: YP 3.1 M2
Next Deadline: YP 3.1 M2 build date 1/20/2020

Next Team Meetings:

Key Status/Updates:

  • YP 3.0.1 was released.
  • YP 3.1 M1 rc8 is in QA
  • YP 3.1 M1 took a record number of build attempts due to various issues which only appeared during the rc builds.
  • Despite a successful rc8 build (which still had reproducible build test failures) there are a number of concerns, particularly as there appears to be very slow builds for some ‘pathological’ hashequiv scenarios. There has been some progress over the weekend on identifying the causes of that and partially addressing them.
  • There remains a growing set of intermittent autobuilder failures which occur with varying frequencies. We’re struggling to find anyone with time/interest to resolve these and they are becoming problematic for reviewing/testing patches and triaging builds.
  • The TSC is working on LTS plans, productive discussions have been had and a new policy on handling this and stable releases should be available in the coming weeks.
  • We are continuing to collect ideas for YP 3.1 in this document: https://docs.google.com/document/d/1UKZIGe88-eq3-pOPtkAvFAegbQDzhy_f4ye64yjnABc/edit?usp=sharing
  • Due to holidays in EU/US, the next status report will be sent in early January (likely 7th). If there is anything critical to report this will happen as needed.

Proposed YP 3.1 Milestone Dates

  • YP 3.1 M1 is in QA
  • YP 3.1 M1 release date 12/13/2019
  • YP 3.1 M2 build date 1/20/2020
  • YP 3.1 M2 release date 1/31/2020
  • YP 3.1 M3 build date 2/24/2020
  • YP 3.1 M3 release date 3/6/2020
  • YP 3.1 M4 build date 3/30/2020
  • YP 3.1 M4 release date 4/24/2020

Planned upcoming dot releases:

  • YP 2.7.3 build date 2/10/20
  • YP 2.7.3 release date 2/21/20
  • YP 3.0.2 build date 2/3/20
  • YP 3.0.2 release date 2/14/20

Tracking Metrics:

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Archives

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