Zephyr 3.2 release checklist

[carlescufi]

• Make sure the release plan is kept up to date:

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

• Pre RC1 Steps

  • Create v3.2.1 milestone so that features that don't make it to the release can be assigned a milestone
  • Verify that all external components and external dependencies are up to date Zephyr 3.2 module updates overview #49678
  • Check known vulnerabilities, and fix exploitable vulnerabilities or verify them as un-exploitable (Security working group).
  • Make sure there's no pending "Release Blocker" issues

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

---

• Release Notes WIP
  • Make sure to tell everybody to use the past tense (i.e. "X has been added" or "X is now Y")
  • Create draft doc/releases/release-notes-3.2.rst with feature summary from the previous one (if not there already)
  • Update doc/releases/release-notes-3.2.rst detailed sections (relative to 3.1.0 release) as important issues are addressed (subsystem owners). Zephyr 3.2 release notes overview #50423

---

• Finalize Release Notes: Finalize release notes for 3.2 #50764
  • 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-3.2.rst overview summary and details sections
    • Request summary details from subsystem maintainers
• Update doc/develop/api/overview.rst doc: api: update overview page #50604
• Update doc/conf.py (add version to relevant list in html_context)
• Update doc/LICENSING.rst for new components that do not have a license

---

• Remaining Release Notes Zephyr 3.2 release notes overview #50423
• Check the CI bi-weekly run for build failures that should be fixed

---

• Update version in VERSION (EXTRAVERSION must be empty, not zero 0)
• Tag both v3.2.0 and zephyr-v3.2.0 (see https://docs.zephyrproject.org/latest/project/release_process.html#tagging)
• Tag v3.2.0 in example-application Create a 3.2 tagpoint example-application#24
• Create release and add notes on https://github.com/zephyrproject-rtos/zephyr/releases. Make sure you use the zephyr-v3.2.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 VERSION (PATCHLEVEL = 99)
  • Create v3.2-branch branch for 3.2.x releases (from v3.2.0 tag, don't include the switch to patchlevel 99)
  • Create backport v3.2-branch label
  • Move all PRs/Issues in the v3.2.0 milestone to the next milestone
  • Close v3.2.0 milestone
  • Update current release and GitHub stats on the website (email Brett)
  • Email devel@lists.zephyrproject.org & announce@lists.zephyrproject.org lists about release and announce the opening of the merge window
  • Create checklist issue for next release
  • Add a comment to this issue linking to the next release checklist issue
  • Marketing Blog for announcing release (https://www.zephyrproject.org/blog)
  • Store the number of currently open PRs to keep track of post-release PR overhead over time
    • 584 at tag time, 552 after the release

[carlescufi]

Link back to previous checklist: #43286