How to create a service release

See also release-process for more general guidance.

  • Fetch pristine source tree, best do a new local clone, e.g.
    git clone git@git.openwrt.org:openwrt/openwrt.git
    git checkout openwrt-22.03
    • Replace branch name with appropriate one
  • Place maketag.sh script from maintainer repo into the clone
  • Execute ./maketag.sh -k 818021EBB6C9ECDA -v 22.03.0
    • Replace key ID and version number with appropriate values
  • Review auto generated commits with git log -p -2
    • Should show one setting adjustment and one setting revert commit
  • Review auto generated tag with git show v22.03.0
    • Should show a git tag with associated GPG info and commit references
    • Replace version number accordingly
  • Compare the files changed automatically with a previous tag
    • git diff v22.03.0-rc2 v22.03.0-rc3 -- feeds.conf.default include/version.mk package/base-files/image-config.in version version.date
  • Check the signature on the tag with git verify-tag -v v22.03.0
    • Should show “Good signature from <your name>
  • Push auto generated commits and tag to the remote:
    git push origin openwrt-22.03
    git push --follow-tags origin refs/tags/v22.03.0:refs/tags/v22.03.0
    • Use credentials provided by admin
  • Open the “Builds → Builders” page
    • Select 00_force_build builder
    • Click on Force builds button at the top of the page
  • Fill out the form
    • Enter your name at Your name input box :-)
    • Enter for example “Trigger release builds” as reason
    • Select Git tag you want to build from Build tag list
    • Click “Force Build”
  • Review buildbot activity in waterfall view
  • Copy make-changelog.pl from maintainer repo into the local clone
    • The script needs the perl module JSON.pm, install libjson-perl and libtext-csv-perl on Debian
  • Execute ./make-changelog.pl v22.03.0..v22.03.1
    • Replace version numbers accordingly
    • Revision range should cover all commits since last release
    • Suggest to redirect stdout to a file
    • Replace base and minor versions accordingly
    • Take care to preserve the first introductory paragraph in the wiki pages
    • Ideally use a prior change log page as template
This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2022/10/18 09:11
  • by hauke