[llvm-branch-commits] [clang-tools-extra] [clangd] Add clangd 23 release notes (PR #211990)

[Nathan Ridge via llvm-branch-commits]

HighCommander4 wrote:

> just realized tho, it is pretty easy to forget to add information here after a new feature has been added, after all if we miss adding it in the PR we have to remember what happened in the last 6 months

I prepare these release notes by looking through the output of a command like `git log origin/release/23.x ^origin/release/22.x clang-tools-extra/clangd/`, picking out changes that seem worth mentioning, and organizing them.

It's a bit of work for me as maintainer, but it does mean the chances of something being overlooked are low.

Of course, when I find something to be already release-noted (like e.g. `InsertReplaceEdit` this release), that's a nice bonus.

> Would be cool if he had an automatic reminder for every PR to check if it should be added.

I could go either way on this. We do get a number of PRs which I don't need think need to be release-noted separately. For example, we have a lot of crash fixes, which I just lump together under "stability improvements", because I think it would just add noise to have a bunch of entries of the form "Fixed a crash when [describe edge case here]". (This is particularly the case this release, where many of the crashes were issues found by fuzzers which users are unlikely to run into in practice.) Doing a single pass after the release has branched makes it easier to be consistent about what is included.

https://github.com/llvm/llvm-project/pull/211990