Updated Release checklist (markdown)

James Groom 2024-04-01 12:04:35 +10:00
parent 0642329cbe
commit b5e15c26d8
1 changed files with 1 additions and 0 deletions

@ -15,6 +15,7 @@ Note that some of these can be done concurrently.
- Separately upload the release archive and `EmuHawk.exe` alone to [VirusTotal](https://www.virustotal.com/gui/home/upload). A false positive from the Microsoft engine is the only one that really matters.
- If it does happen... add a random `<EmbeddedResource/>` to the assembly or something and try again idk ¯\\\_(ツ)\_/¯
1. Create a "Release" on GitHub
- Check the date—if it's April 1st or thereabouts, ABORT MISSION. Seriously, it's just not worth it.
- Set it to create a new tag.
- [GitLab CI](https://gitlab.com/TASVideos/BizHawk/-/pipelines?page=1&scope=all&ref=release) will build the `release` branch shortly after pushing it. Grab the `package_release_*` artifacts, replace "VERSIONHERE" in the filenames, recompress the Linux release as `.tar.gz`, and attach them to the Release.
- For the description, list any new or graduating cores, optionally some large improvements, and if the Windows prereq installer was updated link that too.