Release Checklist¶

This page contains a checklist of things that need to be done for a release.

Release Scheduling¶

• main branch is closed whenever net-next is closed
• main branch is released as feature release 20_ _.a after net-next is closed (whenever Linus released a final Linux version)
  • actually only the patches which were really submitted should be released (when possible)
• stable branch is released on demand
  • for example after security issues
  • when net.git/Linux was released with important fixes and users cannot switch to new feature release (which is done at the same time)

Documentation¶

• [ ] build changelog
• [ ] update README
• [ ] write release announcement
• [ ] update wiki documentation

Code¶

• [ ] make sure all code contains the release version strings
• [ ] update copyright years (if needed)
• [ ] check coverity scan status
• [ ] remove dead code (if any)
• [ ] check against kernel versions
• [ ] check that stable branch is merged in main
• [ ] check for open patches on the ml
• [ ] git tag release

Release¶

• [ ] build package tar.gz and generate checksums
• [ ] move packages/checksums to stable/sources / create symlinks from releases
• [ ] update download links in the redmine downloads page
• [ ] Add news based on News-draft
• [ ] update IRC channel topic

Distributions¶

• [ ] update alfred openwrt package
• [ ] update alfred/batman-adv/batctl openwrt package
• [ ] update gentoo package
• [ ] update alfred/debian batctl package

Aftershow¶

• [ ] Merge current git tag into stable (must be --ff-only or pre-tagging steps were done wrong - git merge --ff-only v20xx.x.x)
• [ ] close current version
• [ ] add new upcoming version
• [ ] Mark issues from Resolved to Closed