You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update doc/releases/release-notes-2.4.rst detailed sections (relative to 2.3.0 release) as important issues are addressed (subsystem owners). See 2.3: Missing release notes #25869
Finalize Release Notes
Add list of GitHub issues (spell check issue list and fix in GitHub as needed) using scripts/release/list_issues.py
Review doc/releases/release-notes-2.4.rst overview summary and details sections (see Sign-off below)
Request summary details from code owners
update doc/reference/overview.rst
Update doc/conf.py (add version to pick list)
Update doc/LICENSING.rst for new components that do not have a license
Create release and add notes on https://github.com/zephyrproject-rtos/zephyr/releases. Make sure you use the zephyr-v2.4.0 tag so that the .zip that GitHub offers has a reasonable name. Add the release notes to the GitHub release.
After Release
Update patchlevel in Makefile (PATCHLEVEL = 99)
Update doc generation (in future should be automatic based on tag) ping @nashif
Major enhancements:
Pre RC1 Steps
See https://docs.zephyrproject.org/latest/development_process/release_process.html#tagging for tagging details
doc/releases/release-notes-2.4.rst
with feature summary from https://www.zephyrproject.org/developers/#releases-overview doc: releases: Release notes for v2.3 - initial (empty) draft #22923doc/releases/release-notes-2.4.rst
detailed sections (relative to 2.3.0 release) as important issues are addressed (subsystem owners). See 2.3: Missing release notes #25869scripts/release/list_issues.py
doc/releases/release-notes-2.4.rst
overview summary and details sections (see Sign-off below)doc/reference/overview.rst
doc/conf.py
(add version to pick list)doc/LICENSING.rst
for new components that do not have a licensezephyr-v2.4.0
tag so that the.zip
that GitHub offers has a reasonable name. Add the release notes to the GitHub release.v2.4-branch
branch for 2.4.x releases (from v2.4.0 tag, don't include the switch to patchlevel 99)The text was updated successfully, but these errors were encountered: