From 95e3f069ee9ca7d1b604add4a2620b824d969aca Mon Sep 17 00:00:00 2001 From: Nathan Ridge Date: Fri, 5 Apr 2024 20:15:34 -0400 Subject: [PATCH] Updated Release checklist (markdown) --- Release-checklist.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/Release-checklist.md b/Release-checklist.md index e553e8e..48fb8e1 100644 --- a/Release-checklist.md +++ b/Release-checklist.md @@ -12,4 +12,14 @@ Checklist of tasks to do for every LLVM release. ## Once the LLVM release is out * Prepare the clangd release on our [Github releases page](https://github.com/clangd/clangd/releases) - * TODO: Write down concrete steps for how to do this, and who has the permission \ No newline at end of file + * Steps for doing this: + * Go to https://github.com/clangd/clangd/actions/workflows/autobuild.yaml + * Click "Run workflow" + * In the "Branch" dropdown, leave the selection as `master`. (This is a branch in the `clangd` repo, and does not interfere with the fact that we can build a commit from a release branch of the `llvm-project` repo.) + * In "Commit to build from", enter the full SHA of the appropriate tag from https://github.com/llvm/llvm-project/tags. For example, for releasing version 18.1.3, look at the tag `llvmorg-18.1.3`, and use the corresponding SHA `c13b7485b87909fcf739f62cfa382b55407433c0`. + * In "Repository to build from", leave the contents as `llvm/llvm-project` + * In "Release name", put the full version, e.g. `18.1.3` + * In "Tag name", put the same version, e.g. `18.1.3` + * In "Release description", put e.g. `Stable clangd 18.1.3 release.` + * Click "Run workflow" + * Wait for the builds to run. The release should be created automatically and the release packages attached to it once the build complete. \ No newline at end of file