51 lines
1.2 KiB
Markdown
51 lines
1.2 KiB
Markdown
# PREMAKE RELEASE CHECKLIST
|
|
|
|
## PREP
|
|
|
|
* Create a new release branch; push to origin
|
|
|
|
* Notify `@premakeapp` of release branch availability; request testing
|
|
|
|
* Update `CHANGES.txt`
|
|
|
|
* `premake5 --file=scripts/changes.lua --since=<last_release_rev> changes`
|
|
|
|
* Review and clean up as needed
|
|
|
|
* Update `README.md`
|
|
|
|
* "Commits since last release" badge (once out of prerelease replace `v5.0.0-alphaXX` with `latest`)
|
|
|
|
* Update version in `src/host/premake.h`
|
|
|
|
* Update version in `website/src/pages/download.js`
|
|
|
|
* Commit changes and push release branch; wait for CI to pass
|
|
|
|
* Prep release announcement from change log
|
|
|
|
## RELEASE
|
|
|
|
* Run `premake5 package <release branch name> source` (from Posix ideally)
|
|
|
|
* On each platform, run `premake5 package <release branch name> binary`
|
|
|
|
* Submit Windows binary to [Microsoft malware analysis](https://www.microsoft.com/en-us/wdsi/filesubmission/)
|
|
|
|
* Push any remaining changes; tag release branch
|
|
|
|
* Create new release on GitHub from `CHANGES.txt`; upload files
|
|
|
|
* Post announcement to `@premakeapp`
|
|
|
|
|
|
## CYCLE
|
|
|
|
* Update version in `src/host/premake.h` (e.x `"5.0.0-dev"`)
|
|
|
|
* Commit
|
|
|
|
* Merge release branch to master
|
|
|
|
* Delete release branch
|