ShuriZma
/
BizHawk
mirror of https://github.com/TASEmulators/BizHawk.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Release checklist (markdown)

James Groom 2022-06-03 07:00:52 +10:00
parent 1ef4439f53
commit 6c0ca8b4b3
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Release-checklist.md

@ -18,13 +18,15 @@ Note that some of these can be done concurrently.
- [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. - [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. - For the description, list any new or graduating cores, optionally some large improvements, and if the Windows prereq installer was updated link that too.
- Click "Publish" and pray. - Click "Publish" and pray.
1. Update Labels and Milestone on GitHub 1. Update Issues, Labels, and Milestone on GitHub
- (where this release will be 2.x.1) - (where this release will be 2.x.1)
- Rename "Repro: Fixed/added in 2.x.1 dev" to "Repro: Fixed/added in 2.x.1" (i.e. remove "dev"; do not rename "Repro: Affects 2.x.1 dev", these should be re-triaged). - Rename "Fixed/added in 2.x.1 dev" to "Fixed/added in 2.x.1" (i.e. remove "dev"; do not rename "Affects 2.x.1 dev", these should be re-triaged).
- Add "Repro: Affects 2.x.1", "Repro: Regression from 2.x.1", and "Repro: Affects 2.x.2 dev". - Add "Affects 2.x.1", "Regression from 2.x.1", and "Affects 2.x.2 dev".
- Create a new Milestone "2.x.2" with target date 3 months from this release. - Create a new Milestone "2.x.2" with target date 3 months from this release.
- Move some or all open Issues to the new Milestone. There's no policy for this as we don't really use it for project management. - Move some or all open Issues to the new Milestone. There's no policy for this as we don't really use it for project management.
- Close the "2.x.1" Milestone. - Close the "2.x.1" Milestone.
- If any Issue was critical enough to warrant pinning, but was fixed for this release, unpin it.
- Re-triage Issues which were only reproduced on dev builds ("Repro: Affects 2.x.1 dev"), and Issues which affected cores that were updated in this release.
1. Update `VersionInfo.MainVersion` and `VersionInfo.ReleaseDate` 1. Update `VersionInfo.MainVersion` and `VersionInfo.ReleaseDate`
- `ReleaseDate` is overwritten by CI for release builds, but needs to be checked-in. `MainVersion` should be set to e.g. `"2.x.2"` after releasing 2.x.1. - `ReleaseDate` is overwritten by CI for release builds, but needs to be checked-in. `MainVersion` should be set to e.g. `"2.x.2"` after releasing 2.x.1.
1. Update readme 1. Update readme
@ -36,6 +38,7 @@ Note that some of these can be done concurrently.
Treat Libretro as just another core in this context. Treat Libretro as just another core in this context.
The cores under "Other cores:" are in alphabetical order, new/graduating aren't. The cores under "Other cores:" are in alphabetical order, new/graduating aren't.
The changes should be sorted with the most important first, but that's kinda subjective so don't try too hard. The changes should be sorted with the most important first, but that's kinda subjective so don't try too hard.
Obviously omit empty headings.
``` ```
- Misc. changes to EmuHawk: - Misc. changes to EmuHawk:
- change - change