Zephyr 2.5.0 RC3 tagged
The third release candidate for Zephyr v2.5.0 has been tagged (v2.5.0-rc3).
The merge window for features and enhancements remains closed until v2.5.0 is released. The next release milestone is code freeze. The final release remains scheduled for 12 Feb.
The focus now should be shifted to testing and documentation of the release. If you are a maintainer, please provide release notes for the areas you are responsible for and any other contributions you might have submitted since the last release. Everyone is encouraged to contribute to the release notes. The draft release notes file can be found here:
During the stabilization period only bug-fix, documentation, and stabilization-related patches may be merged to master.
Additional features or enhancements for the v2.5.0 release require approval by the TSC.
As we need to reduce bug counts for the release, you are all encouraged to submit PRs that close existing bug reports, and to help reviewing such PRs submitted by other contributors or maintainers. Current bug counts are:
High: 3 (Target: 0)
Medium: 21 (Target: 20)
Low: 94 (Target: 100)
More information about bugs counts and real-time tracking of bug counts can be found here: https://testing.zephyrproject.org/issues/zephyrproject-rtos/zephyr/index.html
Testing Zephyr master branch during the stabilization period is also requested; please test the code base and file bug reports so they can be addressed before the release deadline.
All changes since 2.5.0-rc2 can be found here:
More details about Zephyr releases can found on the pages below:
You may continue to send Pull Requests for new features in order to gather feedback early or collaborate with others, but the release team would like to encourage everyone to focus on bugfixes and documentation improvements to the largest extent possible, so that we can release v2.5.0 on time and in the best shape possible. If you have a feature or enhancement you would like to submit to the TSC, please tag the Pull Request with the "TSC" label, make sure it is approved and passing CI, and attend the next TSC meeting.