commit 3dee41147a4631018649c690da373a7208cdec5b
author David Benjamin <davidben@google.com> Tue Oct 01 18:53:35 2024 -0400
committer Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> Wed Oct 02 19:46:58 2024 +0000
tree b03d2e335d164a64f4348e52b0187448148b8018
parent 0eda639cb78a5cf0b479910d8c9a039e47ad36fe

Note that the tag won't mirror to GitHub immediately

Doing this now and it seems to actually take a bit, which is a bit
annoying.

Change-Id: I85ef8da5054dd6ba6f75768586d48761df9a831b
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71687
Reviewed-by: Bob Beck <bbe@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Auto-Submit: David Benjamin <davidben@google.com>

docs/releasing.md

diff --git a/docs/releasing.md b/docs/releasing.md
index e524197..a5dc2fc 100644
--- a/docs/releasing.md
+++ b/docs/releasing.md
@@ -14,7 +14,8 @@
    The "Annotation" field must be non-empty. (Just using the name of the tag
    again is fine.)
 
-4. Create a corresponding GitHub [release](https://github.com/google/boringssl/releases/new).
+4. Wait for the tag to be mirrored to GitHub, and create a corresponding
+   GitHub [release](https://github.com/google/boringssl/releases/new).
 
 5. Download the "Source code (tar.gz)" archive from the new release and
    re-attach it to the release. (The next step will check that the archive is