Weekly Status

Yocto Project Weekly Status January 7, 2020

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

Next Team Meetings:

• Bug Triage meeting Thursday Jan. 9th at 7:30am PDT (https://zoom.us/j/454367603)
• Monthly Project Meeting Tuesday Jan. 7th at 8am PDT (https://zoom.us/j/990892712)
• Weekly Engineering Sync Tuesday Jan. 14th at 8am PDT (https://zoom.us/j/990892712)
• Twitch - Next event is Tuesday Jan. 14th at 8am PDT (https://www.twitch.tv/yocto_project)

Key Status/Updates:

• YP 3.1 M1 was released.
• Over the last two weeks there were a number of significant fixes for hash equivalence which should resolve some of the long standing bugs reported here. Some of these fixes may require further architectural tweaks to the codebase but those are cleanups which can happen in due course now the root causes are identified.
• There are performance issues that remain in hashequivlence but these will be looked at only once the correctness issues and intermittent test failures are addressed.
• There are some puzzling selftest failures that remain, in particular a locked signatures one which seems to be caused through bad interaction with the hash equivalence code but is intermittent and does not make sense.
• The patch queue for master should be roughly up to date which some key changes such as the gettext upgrade having merged recently. Some pending changes like the glibc upgrade look problematic.
• A key functionality change has merged this week where the layout of the sstate directory has changed. This was done to try and improve performance and handle some performance issues where the previous code simply wasn’t scaling. There is no user visible impact but it does mean new sstate will be generated into a new layout and the older sstate will be ignored. The sstate filename length issues should also be addressed by this patchset.
• Whilst the SWAT process is disbanded, the effect of this is that Richard now has to file the bugs personally. This distracts from other things that could be worked on.
• The triage team is worried about attendance at triage meetings and the project is finding it hard to find people to help fix bugs. If anyone is willing to work on bugs, assistance would be greatly appreciated.
• 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

Proposed YP 3.1 Milestone Dates

• 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:

• WDD 2773 (last week 2783) (https://wiki.yoctoproject.org/charts/combo.html)
• Poky Patch Metrics
  • Total patches found: 1400 (last week 1400)
  • Patches in the Pending State: 562 (40%) [last week 561 (40%)]

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

Archives

• 2020 Yocto Project Weekly Status Archive
• 2019 Yocto Project Weekly Status Archive
• 2018 Yocto Project Weekly Status Archive