Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 4: Line 4:


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Dec. 19th at 7:30am PDT (https://zoom.us/j/454367603)
*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)
*Monthly Project Meeting Tuesday  Jan. 7th  at 8am  PDT (https://zoom.us/j/990892712)
*Weekly Engineering Sync Tuesday Dec. 17th 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 Dec. 17th at 8am PDT (https://www.twitch.tv/yocto_project)
*Twitch - Next event is Tuesday Jan. 14th 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.1 M1 was released.
*YP 3.1 M1 rc8 is in QA
*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.
*YP 3.1 M1 took a record number of build attempts due to various issues which only appeared during the rc builds.
*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.
*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 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.
*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 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.
*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
*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/>

Revision as of 15:51, 7 January 2020

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:

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