From 20ed6a52eea7900e6615270eb1b66d46de2b8a2f Mon Sep 17 00:00:00 2001 From: Rangi42 Date: Mon, 30 Jun 2025 15:52:42 -0400 Subject: [PATCH] Clarify release procedure checklist --- RELEASE.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 4feef903..cb121f7b 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -68,7 +68,7 @@ GitHub. 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. @@ -77,9 +77,7 @@ GitHub. to list the new release. 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) - if necessary) to use the new release, and - [index.html](https://github.com/gbdev/rgbds-live/blob/master/index.html) - to link to the new manual version. + if necessary) to use the new release. 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. If the object file revision has been updated, `rgbobj` will need a corresponding release.