Update releasing docs slightly Change-Id: I0c60698f5277c500fad1c85b212565adca39e3c8 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/81207 Commit-Queue: Lily Chen <chlily@google.com> Reviewed-by: Lily Chen <chlily@google.com> Auto-Submit: David Benjamin <davidben@google.com>
diff --git a/docs/releasing.md b/docs/releasing.md index e610ed8..5da2dfd 100644 --- a/docs/releasing.md +++ b/docs/releasing.md
@@ -14,26 +14,30 @@ The "Annotation" field must be non-empty. (Just using the name of the tag again is fine.) -4. Wait for the tag to be mirrored to GitHub, and create a corresponding - GitHub [release](https://github.com/google/boringssl/releases/new). You - have to be a boringssl owner on github for this to work, if it the new link - does not work, bug davidben to invite you to the repository. +4. Wait for the tag to be mirrored to GitHub. If this takes too long, fetch the + tag in your local checkout and push it by hand. (`git fetch origin` + followed by `git push github NAME_OF_TAG`, if `github` is the name of the + remote in your checkout.) -5. Download the "Source code (tar.gz)" archive from the new release and - re-attach it to the release by clicking the edit button, and selecting "Attach New File" - overtop of the release artifacts in github. (The next step will check that the archive is - correct.) +5. Download the tarball of the tag [from GitHub](https://github.com/google/boringssl/tags) + using the "tar.gz" link. -6. Clone a copy of https://github.com/bazelbuild/bazel-central-registry so that you - can make a github pull request against it. +6. Create a corresponding GitHub + [release](https://github.com/google/boringssl/releases/new). You have to be + an owner of GitHub repository for this to work. Ask in the team chat if it + does not work. Attach the tarball to the release. (The `prepare_bcr_module` + tool will check that this was correct.) -6. Run `go run ./util/prepare_bcr_module TAG` and follow the instructions. The +7. Clone a copy of https://github.com/bazelbuild/bazel-central-registry so that you + can make a GitHub pull request against it. + +8. Run `go run ./util/prepare_bcr_module TAG` and follow the instructions. The tool does not require special privileges, though it does fetch URLs from GitHub and read the local checkout. It outputs a JSON file for BCR's tooling to consume. The instructions will tell you to run a bazelisk command. -7. CD into the root of your bazel-central-registry fork, and run the bazelisk +9. CD into the root of your bazel-central-registry fork, and run the bazelisk command indicated by the script output above. It will add a directory to the - repository which is untracked, use "git status " to find it, and "git add" to + repository which is untracked, use `git status` to find it, and `git add` to add it to what you are about to commit. Then commit the changes and added directory, and submit it as a pr to bazel-central-registry.