RELEASING.md

Making a release

1. Find the contents of VERSION (strip the +dev) throughout the code. This should result in six places:
   • VERSION
   • UConfig.pas
   • variables.nsh
   • ultrastardx.appdata.xml
   • 2x Info.plist
2. Make the release:
   • in the first two files, update it to the new version without the +dev bit
   • in variables.nsh update both blocks immediately and swap the comments
   • in ultrastardx.appdata.xml add a new entry
   • in Info.plist update the version number
3. If there are pre-releases in mxe releases, see UPDATING-DLLS.md.
4. Commit, git tag v<the-new-version> and then git push origin master v<the-new-version> master:release
5. Wait and get the artifacts from the CI. If any of them fail, retry the job.
6. Add +dev to the version in the first two files and swap the comments in variables.nsh again, commit, push. This is just to set the dev version again.
7. Attach the artifacts to the release page and publish it.
   You need to extract all the zips except the portable: for i in UltraStarDeluxe-*{linux,mac,installer}*; do unzip $i; rm $i; done
8. Create a PR in the FlatHub repository that updates the tag and commit values. See this PR for an example: https://github.com/flathub/eu.usdx.UltraStarDeluxe/pull/7/files
9. Create a PR in the github.io repository
10. By now the FlatHub build will probably have completed. If it builds successfully, merge it using the Rebase and Merge option.
11. Merge the github.io PR.
12. Close the USDX Draft Release Notes issue and make an announcement in Discord.