[all-commits] [llvm/llvm-project] b88db4: [libc++] Encode the version in the ReleaseNotes file

[Louis Dionne via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: b88db47bd2085c2c8a246751feb63a3ac20a3665
      https://github.com/llvm/llvm-project/commit/b88db47bd2085c2c8a246751feb63a3ac20a3665
  Author: Louis Dionne <ldionne.2 at gmail.com>
  Date:   2023-07-18 (Tue, 18 Jul 2023)

  Changed paths:
    A libcxx/docs/Helpers/ReleaseNotesTemplate.rst
    R libcxx/docs/ReleaseNotes.rst
    A libcxx/docs/ReleaseNotes/17.rst
    M libcxx/docs/ReleaseProcedure.rst
    M libcxx/docs/index.rst

  Log Message:
  -----------
  [libc++] Encode the version in the ReleaseNotes file

This way, we don't need to remove the contents of the ReleaseNotes file
after the branch. This should make it much easier and natural to cherry-pick
changes onto the release branch. Typically, we need two patches for those.
First, we need the code changes against `main`, and then we need a patch
that updates the release notes on the just-created branch.

By versioning the release notes, it becomes easy to author a change
against `main` that targets a just-branched LLVM release by simply
adding it to the release notes for the right version. This has been
a pain point in previous releases.

Differential Revision: https://reviews.llvm.org/D155024