commit 529beb87076bdd7e139b49203080f45e70cfcc09
from: Thomas Adam <thomas@xteddy.org>
date: Fri Sep 23 15:12:29 2022 UTC

portable: clarify release instructions

commit - fbe6c5905d61b8ca15b00cc5982dd40ef75bb564
commit + 529beb87076bdd7e139b49203080f45e70cfcc09
blob - dcc48a947d9bc1a946d8f0bcf2cb48147c7288eb
blob + 98c987a5918be5e34702c57fee238d2732dda753
--- .github/README.md
+++ .github/README.md
@@ -186,10 +186,10 @@ were an out-of-band release to `-portable`.  In such c
 the form:
 
 ```
-0.75a
+0.75.1
 ```
 
-Where the suffix of `a`, `b`, etc., can be used to denote any sub-releases
+Where the suffix of `1`, `2`, etc., can be used to denote any sub-releases
 from the `0.75` version.
 
 The variable `GOT_RELEASE` needs be changed to `yes` so that the
@@ -209,6 +209,19 @@ This can then be copied to the `got-www` repository an
 changing a couple of HTML pages therein to represent the new released version.
 Additionally, the CHANGELOG file can be copied to the `got-www` and committed.
 
+Once all of that has been done, the repository should be tagged to indicate
+the release, hence:
+
+```
+git tag -a 0.75
+```
+
+This can then be pushed out to `gh` and `origin`.
+
+After that point, the version of `GOT_PORTABLE_VER` in
+`util/got-portable-ver.sh` should be changed to the next version, and
+`GOT_RELEASE` should be setg back to `no`.
+
 TODO
 ====
 
blob - 11e876c094e50eec8919342191039a9d0c987897
blob + af14ec7d0117f355bd9973d9c92edca6e13073d9
--- README.portable
+++ README.portable
@@ -189,10 +189,10 @@ were an out-of-band release to `-portable`.  In such c
 the form:
 
 ```
-0.75a
+0.75.1
 ```
 
-Where the suffix of `a`, `b`, etc., can be used to denote any sub-releases
+Where the suffix of `1`, `2`, etc., can be used to denote any sub-releases
 from the `0.75` version.
 
 The variable `GOT_RELEASE` needs be changed to `yes` so that the
@@ -212,6 +212,19 @@ This can then be copied to the `got-www` repository an
 changing a couple of HTML pages therein to represent the new released version.
 Additionally, the CHANGELOG file can be copied to the `got-www` and committed.
 
+Once all of that has been done, the repository should be tagged to indicate
+the release, hence:
+
+```
+git tag -a 0.75
+```
+
+This can then be pushed out to `gh` and `origin`.
+
+After that point, the version of `GOT_PORTABLE_VER` in
+`util/got-portable-ver.sh` should be changed to the next version, and
+`GOT_RELEASE` should be setg back to `no`.
+
 TODO
 ====