From 4270e9fdac410d6bf34f243a95ef84631e8e20cd Mon Sep 17 00:00:00 2001
From: Caleb Jasik <calebjasik@jasik.xyz>
Date: Tue, 4 Feb 2025 13:31:31 -0600
Subject: [PATCH] Write out the entire release process in steps

---
 README.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index a17e2e4..f61652c 100644
--- a/README.md
+++ b/README.md
@@ -43,7 +43,7 @@ In Android Studio, set the line length using Preferences → Editor → Code Sty
 
 # Prerelease
 
-Push a git tag `v#.#.#-##`, e.g. `v0.5.2-0`, and `.github/release.yml` will build a draft release and publish it to iOS TestFlight and Android internal track.
+Push a git tag `v#.#.#-##`, e.g. `v0.5.1-0`, and `.github/release.yml` will build a draft release and publish it to iOS TestFlight and Android internal track.
 
 `./swift-format.sh` can be used to format Swift code in the repo.
 
@@ -51,6 +51,7 @@ Once `swift-format` supports ignoring directories (<https://github.com/swiftlang
 
 # Release
 
-We manually promote a prerelease build from TestFlight and Android internal track to the public app stores, and then mark the associated draft release as published, removing the `-##` from it, ending with a release in the format `v#.#.#`, e.g. `v0.5.2`.
-
-Additionally, we should add the notable changes to the app to the release details.
\ No newline at end of file
+1. Manually promote a prerelease build from TestFlight and Android internal track to the corresponding public app stores. 
+2. Mark the associated draft release as published, removing the `-##` from it, ending with a release in the format `v#.#.#`, e.g. `v0.5.1`.
+3. Remove the old draft releases that will never be published.
+4. Add the notable changes to the app to the release summary, e.g.: <https://github.com/DefinedNet/mobile_nebula/releases/tag/v0.5.1>.
\ No newline at end of file