Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
Line 1: Line 1:
== Yocto Project Weekly Status March 3, 2020 ==
== Yocto Project Weekly Status March 3, 2020 ==
Current Dev Position: YP 3.1 M3  - At Feature Freeze <br/>
Current Dev Position: YP 3.1 M3  - At Feature Freeze, build pending <br/>
Next Deadline: YP 3.1 M3 build date 2/24/2020<br/>
Next Deadline: YP 3.1 M3 build date 2/24/2020<br/>


Line 10: Line 10:


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 2.7.3 rc1 is in QA with the report due next week.
*YP 2.7.3 and 3.0.2 have been released.
*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.
*YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
*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 are now past M3 feature freeze. A number of key issues have been addressed, thanks to everyone who contributed:
*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.
**psplash systemd race issues fixed (Thanks Scott)
*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.
**make mips issue root caused and glibc fix pulled in (Thanks Victor/Khem)
*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.
**ltp upgrade resolved (Thanks Petr)
*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!
**util-linux update resolved (Thanks Pierre-Jean)
*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).
**Uninative tumbleweed issue resolved (Thanks Michael)
*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.
**libgpg-error upgrade (Thanks Alex)
**There were many other fixes and upgrades, thanks all!
*The remaining issues we need to look at addressing before we build M3 are:
**bind upgrade (needs libuv maintainer fix and resend from Armin)
**coreutils ptest blocked on libmodule-build-perl reproducibility issue
**Locked signature selftest failure
**SystemExit() intermittent selftest failure
**pseudo sysroot high priority bug
**gcc buildtools tarball solution for centos7 support
*Recipe upgrades are now much less likely to be accepted unless there is a pressing need, ideally these should be held until 3.1 is released and development for 3.2 is started. We do not have a tracking branch for 3.2 as we’d like to focus people on 3.1 right now.
*Bug metrics are not good with a rise in WDD when typically it should be falling for this point in a release cycle.


'''Proposed YP 3.1 Milestone Dates'''<br/>
'''Proposed YP 3.1 Milestone Dates'''<br/>

Revision as of 15:55, 3 March 2020

Yocto Project Weekly Status March 3, 2020

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

Next Team Meetings:

Key Status/Updates:

  • YP 2.7.3 and 3.0.2 have been released.
  • YP 3.1 has been announced as an LTS release: https://www.yoctoproject.org/yocto-project-long-term-support-announced/
  • We are now past M3 feature freeze. A number of key issues have been addressed, thanks to everyone who contributed:
    • psplash systemd race issues fixed (Thanks Scott)
    • make mips issue root caused and glibc fix pulled in (Thanks Victor/Khem)
    • ltp upgrade resolved (Thanks Petr)
    • util-linux update resolved (Thanks Pierre-Jean)
    • Uninative tumbleweed issue resolved (Thanks Michael)
    • libgpg-error upgrade (Thanks Alex)
    • There were many other fixes and upgrades, thanks all!
  • The remaining issues we need to look at addressing before we build M3 are:
    • bind upgrade (needs libuv maintainer fix and resend from Armin)
    • coreutils ptest blocked on libmodule-build-perl reproducibility issue
    • Locked signature selftest failure
    • SystemExit() intermittent selftest failure
    • pseudo sysroot high priority bug
    • gcc buildtools tarball solution for centos7 support
  • Recipe upgrades are now much less likely to be accepted unless there is a pressing need, ideally these should be held until 3.1 is released and development for 3.2 is started. We do not have a tracking branch for 3.2 as we’d like to focus people on 3.1 right now.
  • Bug metrics are not good with a rise in WDD when typically it should be falling for this point in a release cycle.

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

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