Closed nashif closed 3 years ago
Bug status: High: 0 Medium: 10 Low: 88
Git Stats:
Num commits: 52909 (git rev-list --count upstream/main
)
Contributors 976 (From main Zephyr Github Page, under about)
Repositories: 94 (on https://github.com/zephyrproject-rtos)
Num pull requests: 35968 (Look for latest pr number on https://github.com/zephyrproject-rtos/zephyr/pulls)
Closing this out. 2.6 is out the door. Just need to work on the blog.
[x] Major enhancements:
[x] Pre RC1 Steps
See https://docs.zephyrproject.org/latest/development_process/release_process.html#tagging for tagging details
doc/releases/release-notes-2.6.rst
with feature summary from https://www.zephyrproject.org/developers/#releases-overview #22923[x] Update
doc/releases/release-notes-2.6.rst
detailed sections (relative to 2.5.0 release) as important issues are addressed (subsystem owners). See #25869scripts/release/list_issues.py
doc/releases/release-notes-2.6.rst
overview summary and details sections (see Sign-off below)doc/reference/api/overview.rst
doc/conf.py
(add version to pick list)[x] Update
doc/LICENSING.rst
for new components that do not have a license[x] Security - @d3zd3z
[x] Create release and add notes on https://github.com/zephyrproject-rtos/zephyr/releases. Make sure you use the
zephyr-v2.6.0
tag so that the.zip
that GitHub offers has a reasonable name. Add the release notes to the GitHub release.v2.6-branch
branch for 2.6.x releases (from v2.6.0 tag, don't include the switch to patchlevel 99)backport v2.6-branch
label