-
Notifications
You must be signed in to change notification settings - Fork 293
Release checklist
Jakob Gahde edited this page Nov 11, 2025
·
32 revisions
Only bug fixes and testing should be done prior to a release. However, should it happen that a feature is introduced right before a scheduled release, postpone the release and make sure everything works as expected!
- Bump version number (common.pri)
- Prepare release notes for CHANGELOG
- Make sure all unit tests are working and are OK
- Test all features known to work and make sure they behave the same
- Update contributor list
- Update MetaInfo
- Add entry for new release
- If the new release makes visible changes to the user interface, update the screenshot in accordance with the Flathub quality guidelines @J5lx
- Make sure 0 issues in milestone
- Add release tag to the correct commit
- Push to release branch
- When renaming the AppImage, also update the plaintext metadata block at the beginning of the *.AppImage.zsync file accordingly
- Build and upload manually compiled versions:
- 32-bit Linux AppImage
- Add downloads to the Bitbucket mirror
- Update download links:
- Update packages
- Arch Linux (unmaintained)
- Homebrew Cask (macOS) @scribblemaniac
- Apt (Debian/Ubuntu) @fabiomt
- Flatpak (Linux) @J5lx @eszlari
- RPM (Fedora) @musicinmybrain
- FreeBSD @yurivict
- KCP (KaOS) @scribblemaniac
- NixOS @agvantibo-again
Make announcement with release notes (or a link to the release notes) on the following platforms: