Project

General

Profile

Release Checklist

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

Release Scheduling

  • master branch is closed whenever net-next is closed
  • master 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)
  • maint 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

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 maint branch is merged in master
  • [ ] 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
  • [ ] send release mail
  • [ ] update IRC channel topic

Distributions

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

Aftershow

release_scheduling.svg View (63.5 KB) Sven Eckelmann, 04/19/2015 11:38 PM

release_scheduling.svg View (62.1 KB) Sven Eckelmann, 11/01/2016 05:10 PM