Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status November 19, 2019 ==
== Yocto Project Weekly Status November 26, 2019 ==
Current Dev Position: YP 3.1 M1 <br/>
Current Dev Position: YP 3.1 M1 <br/>
Next Deadline: YP 3.1 M1 build Dec. 2, 2019<br/>
Next Deadline: YP 3.1 M1 build Dec. 2, 2019<br/>


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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.7.2 is under review by the TSC and likely to be released.
*YP 2.7.2 should be released imminently.
*Tests were made on making reproducibility the default for poky. There were several issues found for which bugs were filed:
*The reproducibility issues from last week have been addressed and we are hoping to enable this by default soon, thanks to everyone who helped fix issues.
**A double free issue in opkg (Alejandro looking into, thanks)
*The news for hash equivalence is not so promising. Whilst a number of bugs were fixed, we’ve found a major problem which explains some of the failures we’ve seen and are currently working out how we may be able to resolve that issue.
**devtool failures (Paul sent a fix, thanks)
**recipetool failures (Richard sent a fix)
*Tests were made on making the hashserver default for poky. There were also several issues found and RP is trying to understand and work through those. At least one critical issue has been identified and due to be tested.
*The SWAT team no longer has enough people on it to make it sustainable and has therefore been disbanded. This means build owners need to triage their own build failures. Richard will be responsible for failures in the scheduled master builds.
*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.
*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.
*The focus on hash equivalence and reproducibility has slowed patch merging in other areas. Patch testing has been problematic as there are a lot of regressions being found in submitted patches which also slows down the whole merging process.
*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 next couple of 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 next couple of weeks.
*We have begun collecting 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
*Due to the number of key fixes being found we have delayed YP 3.0.1 being built slightly whilst we merge those fixes, it should build in the next few days.
*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.


Line 42: Line 40:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2533 (last week 2508) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2578 (last week 2533) (https://wiki.yoctoproject.org/charts/combo.html)
*Poky Patch Metrics   
*Poky Patch Metrics   
**Total patches found: 1461 (last week 1445)
**Total patches found: 1450 (last week 1461)
**Patches in the Pending State: 579 (40%) [last week 579 (40%)]
**Patches in the Pending State: 579 (40%) [last week 579 (40%)]


Revision as of 15:43, 26 November 2019

Yocto Project Weekly Status November 26, 2019

Current Dev Position: YP 3.1 M1
Next Deadline: YP 3.1 M1 build Dec. 2, 2019

Next Team Meetings:

Key Status/Updates:

  • YP 2.7.2 should be released imminently.
  • The reproducibility issues from last week have been addressed and we are hoping to enable this by default soon, thanks to everyone who helped fix issues.
  • The news for hash equivalence is not so promising. Whilst a number of bugs were fixed, we’ve found a major problem which explains some of the failures we’ve seen and are currently working out how we may be able to resolve that issue.
  • 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.
  • The focus on hash equivalence and reproducibility has slowed patch merging in other areas. Patch testing has been problematic as there are a lot of regressions being found in submitted patches which also slows down the whole merging process.
  • 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 next couple of 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 the number of key fixes being found we have delayed YP 3.0.1 being built slightly whilst we merge those fixes, it should build in the next few days.
  • If anyone has any status items for the project they’d like to add to the weekly reports, please email Richard+Stephen.

Proposed YP 3.1 Milestone Dates

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

Planned upcoming dot releases:

  • YP 2.7.2 Should release this week.
  • YP 3.0.1 Proposed build date 11/25/2019
  • YP 3.0.1 Proposed release date 12/06/2019
  • YP 2.7.3 Proposed build date 2/10/20
  • YP 2.7.3 Proposed release date 2/21/20
  • YP 3.0.2 Proposed build date 2/3/20
  • YP 3.0.2 Proposed 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=64156"