Document extra pre-release updates

This commit is contained in:
ISSOtm
2024-09-18 19:38:03 +02:00
parent b03a5b13b7
commit d494f73825

View File

@@ -3,13 +3,14 @@
This describes for the maintainers of RGBDS how to publish a new release on This describes for the maintainers of RGBDS how to publish a new release on
GitHub. GitHub.
1. Update, commit, and push [include/version.hpp](include/version.hpp) with 1. Update the following files, then commit and push.
values for `PACKAGE_VERSION_MAJOR`, `PACKAGE_VERSION_MINOR`, You can use <code>git commit -m "Release <i>&lt;version&gt;</i>"</code> and `git push origin master`.
`PACKAGE_VERSION_PATCH`, and `PACKAGE_VERSION_RC`, as well as
[Dockerfile](Dockerfile) with a value for `ARG version`. Only define - [include/version.hpp](include/version.hpp): set appropriate values for `PACKAGE_VERSION_MAJOR`, `PACKAGE_VERSION_MINOR`, `PACKAGE_VERSION_PATCH`, and `PACKAGE_VERSION_RC`
`PACKAGE_VERSION_RC` if you are publishing a release candidate! You can **Only** define `PACKAGE_VERSION_RC` if you are publishing a release candidate!
use <code>git commit -m "Release <i>&lt;version&gt;</i>"</code> and - [Dockerfile](Dockerfile): update `ARG version`.
`git push origin master`. - [test/fetch-test-deps.sh](test/fetch-test-deps.sh): update test dependency commits (preferably, use the latest available).
- [man/\*](man/): update dates and authors.
2. Create a Git tag formatted as <code>v<i>&lt;MAJOR&gt;</i>.<i>&lt;MINOR&gt;</i>.<i>&lt;PATCH&gt;</i></code>, 2. Create a Git tag formatted as <code>v<i>&lt;MAJOR&gt;</i>.<i>&lt;MINOR&gt;</i>.<i>&lt;PATCH&gt;</i></code>,
or <code>v<i>&lt;MAJOR&gt;</i>.<i>&lt;MINOR&gt;</i>.<i>&lt;PATCH&gt;</i>-rc<i>&lt;RC&gt;</i></code> or <code>v<i>&lt;MAJOR&gt;</i>.<i>&lt;MINOR&gt;</i>.<i>&lt;PATCH&gt;</i>-rc<i>&lt;RC&gt;</i></code>