User Tools

Site Tools


docs:guide-developer:making-service-release

HOWTO make a service release

1) Prepare release tag

  • Fetch maintainer scripts from https://git.openwrt.org/maintainer-tools.git
  • Ensure that GPG and usign keys are published and working according to https://openwrt.org/docs/guide-user/security/keygen
  • Fetch pristine source tree, best do a new local clone, e.g.
    git clone git@git.openwrt.org:openwrt/openwrt.git
    git checkout openwrt-19.07
    • Replace branch name with appropriate one
  • Place maketag.sh script from maintainer repo into the clone
  • Execute ./maketag.sh -k 818021EBB6C9ECDA -v 19.07.0-rc2
    • 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 v19.07.0-rc2
    • Should show a git tag with associated GPG info and commit references
    • Replace version number accordingly
  • Push auto generated commits and tag to the remote:
    git push origin openwrt-19.07
    git push --follow-tags origin refs/tags/v19.07.0-rc2:refs/tags/v19.07.0-rc2

2) Trigger builds

    • Use credentials provided by admin
  • Open the “Builders” page
    • Scroll down to “Force All Builds” form
  • Fill out the form
    • Enter “Trigger release builds” as reason
    • In the first “Name:” field enter tag
    • In the first “Value:” field enter 19.07.0-rc2
      • Replace version number accordingly
      • Note the missing v prefix! Enter only the number
    • Click “Force Build”
  • Review buildbot activity in waterfall view

3) Create changelogs

  • Copy make-changelog.pl from maintainer repo into the local clone
  • Execute ./make-changelog.pl v17.01.4..v17.01.5
    • 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

4) Update release information page

5) Announce

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
docs/guide-developer/making-service-release.txt · Last modified: 2019/11/30 19:11 by hauke