Weekly Status: Difference between revisions

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


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*The project recently updated its git hosting infrastructure and there were some issues encountered with the cgit http/https repository sharing. Those issues should now be resolved, apologies if they caused issues for anyone. The git:// protocol sharing was unaffected.
*YP 2.7.3 rc1 is in QA with the report due next week.
*YP 3.0.2 rc2 is in QA with the report due soon.
*YP 3.0.2 rc2 was rebuilt to remove a broken bash CVE patch, rc3 had automated QA only and is now due for release.
*We continue to see a small number of reproducibility issues with master which need resolving for green builds (in particular gstreamer and perl).
*We are now at the date for M3 which is feature freeze. We are not yet in a position where we can build M3 as there are a number of open high blocking bugs but patches will need to start tapering down to bug fix only. More invasive or unplanned features will no longer be accepted.
*A significant memory usage issue was identified during bitbake parsing where memory usage would grow in each parser thread linearly per number of recipes parsed. This would therefore particularly affect large numbers of layers, multilibs and multiconfig. The fix has merged into bitbake along with the corresponding zeus and warrior branches. For one test case it reduced peak memory usage during parsing for 5 multiconfigs from 20GB to 2GB.
*We have a serious issue with hashequiv but a patch in progress for that. There is also a usability issue raised with hashequiv and this can only realistically be fixed in M4, it means changing the UI message handling within bitbake.
*Warrior patches for 2.7.3 are out for review.
*We continue to see automated test failures with master, most are long standing issues which we’re struggling to resolve. A minority now have had their causes narrowed down or are now reproducible at will which should help but there is concern about the others.
*With the git infrastructure issue updated, we now have centos8 workers added to the autobuilder.
*Some recent changes like psplash systemd support have introduced a race causing intermittent build failures. We had thought those resolved but they reappeared after merging.
*We are making various queued changes to the autobuilder configuration to fix bugs, improve efficiency and test coverage but this may result in some test result instability as we test and resolve issues.
*Alex Kanavin has quietly but very effectively been fixing ptest failures and we now have only a very small number of non-toolchain tests failing, thanks Alex!
*We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
*We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
*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 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.

Revision as of 15:51, 25 February 2020

Yocto Project Weekly Status February 18, 2020

Current Dev Position: YP 3.1 M3 - At Feature Freeze
Next Deadline: YP 3.1 M3 build date 2/24/2020

Next Team Meetings:

Key Status/Updates:

  • YP 2.7.3 rc1 is in QA with the report due next week.
  • YP 3.0.2 rc2 was rebuilt to remove a broken bash CVE patch, rc3 had automated QA only and is now due for release.
  • We are now at the date for M3 which is feature freeze. We are not yet in a position where we can build M3 as there are a number of open high blocking bugs but patches will need to start tapering down to bug fix only. More invasive or unplanned features will no longer be accepted.
  • We have a serious issue with hashequiv but a patch in progress for that. There is also a usability issue raised with hashequiv and this can only realistically be fixed in M4, it means changing the UI message handling within bitbake.
  • We continue to see automated test failures with master, most are long standing issues which we’re struggling to resolve. A minority now have had their causes narrowed down or are now reproducible at will which should help but there is concern about the others.
  • Some recent changes like psplash systemd support have introduced a race causing intermittent build failures. We had thought those resolved but they reappeared after merging.
  • Alex Kanavin has quietly but very effectively been fixing ptest failures and we now have only a very small number of non-toolchain tests failing, thanks Alex!
  • We’re collecting a list of companies, products and projects which use the Yocto Project on the wiki: https://wiki.yoctoproject.org/wiki/Project_Users Please add any you know are missing (or email Richard/Stephen who can add).
  • 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.

Proposed YP 3.1 Milestone Dates

  • 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 built and in QA
  • YP 2.7.3 release date 2/21/2020
  • YP 3.0.2 release soon
  • YP 3.0.3 build date 5/4/2020
  • YP 3.0.3 release date 5/15/2020
  • YP 2.7.4 build date 5/18/2020
  • YP 2.7.4 release date 5/29/2020

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