Sidebar
docs:guide-developer:making-service-release
Table of Contents
HOWTO make a service release
1) Prepare release tag
- Fetch maintainer scripts from https://github.com/KanjiMonster/maintainer-tools
- 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 https://git.openwrt.org/openwrt/openwrt.git git checkout lede-17.01
- Replace branch name with appropriate one
- Place
maketag.shscript from maintainer repo into the clone - Execute
./maketag.sh -k 818021EBB6C9ECDA -v 17.01.5- 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 autogenerated tag with
git show v17.01.5- Should show a git tag with associated GPG info and commit references
- Replace version number accordingly
- Push autogenerated ocmmits and tag to the remote:
git push origin lede-17.01 git push --follow-tags origin refs/tags/v17.01.5:refs/tags/v17.01.5
- Replace version numbers and branch name accordingly
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
17.01.5- Replace verison number accordingly
- Note the missing
vprefix! Enter only the number
- Click “Force Build”
- Review buildbot activity in waterfall view
3) Create changelogs
- Copy
make-changelog.plfrom 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
- Copy resulting change log into https://openwrt.org/releases/17.01/changelog-17.01.5
- 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
- Once the release builds are finished and uploaded to https://downloads.openwrt.org/releases/17.01.5/targets/ …
- … head to release series parent page at https://openwrt.org/releases/17.01/start
- Replace base version accordingly if needed
- Update timeline and latest version number, links etc. to point to the latest release
- Start preparing release notes at https://lede-project.org/releases/17.01/notes-17.01.5
- Replace version accordingly
- Mention most important changes since last release
- Use old release note pages as template
- Good technique is to skim through detailed change log and taking note of outstanding commits or series of commits
5) Announce
- Write an announcement to the mailing lists
- Write an announcement in the forum
- Use https://forum.openwrt.org/t/lede-v17-01-4-service-release/7573 as template
- “Pin” the topic for 4-8 weeks
- Update IRC channel topics
docs/guide-developer/making-service-release.txt · Last modified: 2018/09/03 17:13 by tmomas
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
