Updated Release checklist (markdown)

Release-checklist.md

@@ -3,11 +3,12 @@ Note that some of these can be done concurrently.
 1. Choose to merge or not merge pending changes
 	- Ideally there would be a release candidate and rigorous testing, but there never seems to be enough time...
 1. Write the changelog
-	- You can use `git log --pretty='format:[%h %an] %s%n%b%n' 2.8..` (substitute the last release tag for "2.8") as a starting point.
+	- You can use `git log --pretty='format:[%h %an] %s%n%b%n' 2.x..` (substitute the last release tag for "2.x") as a starting point.
 	- After parsing through the commits to get a list of user-facing changes, group them as in the example below. You should include Issue numbers for bugs and feature requests, but not PRs.
 	- This needs to be prepended to `/Assets/changelog.md` (Markdown) *immediately before* updating the `release` branch so that it ends up in the build artifacts.
 	- It also needs to be prepended to [the `ReleaseHistory` article](https://tasvideos.org/Bizhawk/ReleaseHistory) (TASVideos wiki markup). Apart from changing markup language, also remember to include download links and the release date (will need to finish this after publishing).
 	- There's also [the ext. tool changelog](https://github.com/TASEmulators/BizHawk-ExternalTools/wiki/Partial-changelog-for-ApiHawk). If an ApiHawk change doesn't affect Lua then it might not warrant inclusion on the main changelog, but this one includes even the tiny method signature changes.
+1. Update `VersionInfo.MainVersion` if it was set for a point release but this will be a minor release
 1. Update the `release` branch to point to `master`
 1. Check for AV false positives
 	- Separately upload the release archive and just `EmuHawk.exe` to [VirusTotal](https://www.virustotal.com/gui/home/upload). A false positive from the Microsoft engine is the only one that really matters.