Zephyr 3.0 Release Checklist

[cfriedt]

• [ ] Major enhancements:

  • See https://github.com/zephyrproject-rtos/zephyr/projects/9

• [x] Pre RC1 Steps

  • [x] Create v3.0.1 milestone so that features that don't make it to the release can be assigned a milestone
  • [x] Verify that all external components and external dependencies are up to date, for example
    • mbedTLS
    • tinycrypt
    • FatFS
  • [x] Check known vulnerabilities, and fix exploitable vulnerabilities or verify them as un-exploitable (Security working group).

See https://docs.zephyrproject.org/latest/development_process/release_process.html#tagging for tagging details

---

• [x] Release Notes WIP
  • [x] Make sure to tell everybody to use the past tense (i.e. "X has been added" or "X is now Y")
  • [x] Create draft doc/releases/release-notes-3.0.rst with feature summary from https://www.zephyrproject.org/developers/#releases-overview #22923

  • [x] Update doc/releases/release-notes-3.0.rst detailed sections (relative to 2.7.0 release) as important issues are addressed (subsystem owners). See #25869

• [x] Finalize Release Notes
  • [x] Add list of GitHub issues (spell check issue list and fix in GitHub as needed) using scripts/release/list_issues.py
  • [x] Review doc/releases/release-notes-3.0.rst overview summary and details sections (see Sign-off below)
  • [x] Request summary details from code owners
• [x] Update doc/reference/api/overview.rst
• [x] Update doc/conf.py (add version to pick list)

• [x] Update doc/LICENSING.rst for new components that do not have a license

• [x] Final Release Notes Sign-off
  • Subsystems
  • [x] #42974
  • [x] #42975
  • [x] #42976
  • [x] #42977
  • [x] #42978
  • [x] #42979
  • [x] #42980
  • [x] #42981
  • [x] #42982
  • Architectures
  • [x] #42983
  • [x] #42984
  • [x] #42985
  • [x] #42986
  • [x] Xtensa, NIOS-II - @nashif, @dcpleung
  • Board an Soc support - many

  • [x] #42987

• [x] Update version in VERSION
• [x] Tag both v3.0.0 and zephyr-v3.0.0
• [x] Tag v3.0.0 in example-application

• [x] Create release and add notes on https://github.com/zephyrproject-rtos/zephyr/releases. Make sure you use the zephyr-v3.0.0 tag so that the .zip that GitHub offers has a reasonable name. Add the release notes to the GitHub release.

• [x] After Release
  • [x] Update patchlevel in Makefile (PATCHLEVEL = 99)
  • [x] Update https://www.zephyrproject.org/developer-resources/#current-release (email Brett)
  • [x] Create v3.0-branch branch for 3.0.x releases (from v3.0.0 tag, don't include the switch to patchlevel 99)
  • [x] Create backport v3.0-branch label
  • [x] Merge all post-release PRs in https://github.com/zephyrproject-rtos/zephyr/projects/27
  • [x] Move all PRs/Issues in the v3.0.0 milestone to the next milestone
  • [x] Close v3.0.0 milestone
  • [x] Email devel@lists.zephyrproject.org & announce@lists.zephyrproject.org lists about release and announce the opening of the merge window
  • [x] Create checklist issue for next release
  • [x] Add a comment to this issue linking to the next release checklist issue
  • [x] Marketing Blog for announcing release (https://www.zephyrproject.org/blog)
  • [x] Update https://www.zephyrproject.org with latest stats from GitHub (email Brett)
  • [x] Store the number of currently open PRs to keep track of post-release PR overhead over time

[de-nordic]

The release is done. Shouldn't this be closed?

[dkalowsk]

@de-nordic yep. Thought I did close it, thanks for calling it out.