46244 (cont.): Flesh out the TODO from the previous commit.

2 files changed, 22 insertions, 2 deletions

diff --git a/ChangeLog b/ChangeLog
index b5cee137e..ffcb1778f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,8 @@
 2020-07-14  Daniel Shahaf  <d.s@daniel.shahaf.name>
 
+	* 46244 (cont.): Etc/creating-a-release.txt: Flesh out the TODO
+	from the previous commit.
+
 	* 46244: Etc/creating-a-release.txt: Start to introduce a
 	release managers keyring.
 
diff --git a/Etc/creating-a-release.txt b/Etc/creating-a-release.txt
index 38d34743e..16784a054 100644
--- a/Etc/creating-a-release.txt
+++ b/Etc/creating-a-release.txt
@@ -75,8 +75,9 @@ To create a zsh release:
 - [one time step] Add your key to the Keys/ directory in the 'web' repository, using
   `gpg --armor --export $YourPublicKeyFingerprint`.
 
-  TODO: cat Keys/*.asc into a zsh-keyring.asc, upload it along with the
-  tarballs, link to it from Arc/source.html and elsewhere
+- Create the keyring:
+
+        cat web.git/Keys/*.asc > zsh-keyring.asc
 
 - Upload to sf.net:
 
@@ -87,6 +88,22 @@ To create a zsh release:
 	[Select All] next to "Default Download For:".  This should cause sf.net
 	to offer that artifact in the "Looking for the latest version?" line.
 
+  You should upload five files:
+
+        zsh-5.8.tar.xz
+        zsh-5.8.tar.xz.asc
+        zsh-doc-5.8.tar.xz
+        zsh-doc-5.8.tar.xz.asc
+        zsh-keyring.asc
+
+        (TODO: what about MD5SUM, FAQ, META-FAQ, all in www.zsh.org/pub/?)
+
+  Note that zsh-keyring.asc is fine to just overwrite, since it's only ever
+  appended to, and in any case the underlying Keys/*.asc files are in version
+  control.
+
+  TODO: link to zsh-keyring.asc from Arc/source.html and elsewhere
+
 - If the new release is a stable release, update zsh.sf.net:
 
 	# Move into the 'web' repository mentioned above