From bbe4046bab39a1377300ab4d26d2e888ccd75a59 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?kadir=20=C3=A7etinkaya?= Date: Tue, 16 Apr 2024 13:45:07 +0200 Subject: [PATCH] add a step to mention testing binaries, and marking the release as latest --- Release-checklist.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Release-checklist.md b/Release-checklist.md index d980754..836c0e0 100644 --- a/Release-checklist.md +++ b/Release-checklist.md @@ -23,4 +23,6 @@ Checklist of tasks to do for every LLVM release. * 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. - * Mark the release as a stable release by unchecking the "pre-release" checkbox. \ No newline at end of file + * Test out the binaries on as many platforms as possible, e.g. running `clangd --check=/tmp/foo.cc` to ensure binaries can "run". + * Mark the release as a stable release by unchecking the "pre-release" checkbox. + * Mark the release as latest after couple weeks if there are no issues. This will result in new binaries being picked up by [vscode-clangd](github.com/clangd/vscode-clangd) extension and some other integrations like [chrome](https://github.com/clangd/chrome-remote-index)/[llvm](https://github.com/clangd/llvm-remote-index) remote indexers and servers. \ No newline at end of file