Clarify release procedure checklist

This commit is contained in:
Rangi42
2025-06-30 15:52:42 -04:00
parent 8b85875b67
commit 20ed6a52ee

View File

@@ -68,7 +68,7 @@ GitHub.
6. Click the "Publish release" button to publish it! 6. Click the "Publish release" button to publish it!
7. Update the `release` branch. You can use `git push origin release`. 7. Update the `release` branch. You can use `git push origin master:release`.
8. Update the following related projects. 8. Update the following related projects.
@@ -77,9 +77,7 @@ GitHub.
to list the new release. to list the new release.
2. [rgbds-live](https://github.com/gbdev/rgbds-live): update the `rgbds` submodule (and 2. [rgbds-live](https://github.com/gbdev/rgbds-live): update the `rgbds` submodule (and
[patches/rgbds.patch](https://github.com/gbdev/rgbds-live/blob/master/patches/rgbds.patch) [patches/rgbds.patch](https://github.com/gbdev/rgbds-live/blob/master/patches/rgbds.patch)
if necessary) to use the new release, and if necessary) to use the new release.
[index.html](https://github.com/gbdev/rgbds-live/blob/master/index.html)
to link to the new manual version.
3. [rgbobj](https://github.com/gbdev/rgbobj) and [rgbds-obj](https://github.com/gbdev/rgbds-obj): 3. [rgbobj](https://github.com/gbdev/rgbobj) and [rgbds-obj](https://github.com/gbdev/rgbds-obj):
make sure that object files created by the latest RGBASM can be parsed and displayed. make sure that object files created by the latest RGBASM can be parsed and displayed.
If the object file revision has been updated, `rgbobj` will need a corresponding release. If the object file revision has been updated, `rgbobj` will need a corresponding release.