[libcxx-commits] [libcxx] [libc++] Update release procedure for libc++ & friends (PR #210383)

[Nikolas Klauser via libcxx-commits]

================
@@ -37,39 +35,31 @@ release:
 * Make sure all libc++ supported compilers in the CI are updated to their
   latest release.
 
-Branching
-=========
-
-This is done by the LLVM Release managers.
+After the branch is created
+===========================
 
 After branching for an LLVM release:
 
 1. Update ``_LIBCPP_VERSION`` in ``libcxx/include/__config``
 2. Update the version number in ``libcxx/docs/conf.py``
 3. Update ``_LIBCPPABI_VERSION`` in ``libcxxabi/include/cxxabi.h``
 4. Update ``_LIBUNWIND_VERSION`` in ``libunwind/include/__libunwind_config.h``
-5. Create a release notes file for the next release from the template
-6. Point to the new release notes file from ``libcxx/docs/ReleaseNotes.rst``
-
-Post branching
-==============
-
-This is done by the libc++ developers.
-
-After branching it takes a couple of days before the new LLVM ToT version is
-available on `<https://apt.llvm.org>`_. Once it is available the pre-commit CI
-can start using the new ToT version. In order to make sure patches can be
-backported to the release branch the oldest compiler is not removed yet.
-
-The section ``Upcoming Deprecations and Removals`` is cleared by the release
-managers. Copy back the items that were in this section.
+5. Create a release notes file for the next release from the previous ones and point to it from
+   ``libcxx/docs/ReleaseNotes.rst``. Remove entries that do not apply anymore, but keep in mind
+   that some entries (such as upcoming deprecations) may still apply, may need rewording and may
+   also require follow up PRs to implement.
+6. Update the set of runners targeted by the CI on the release branch to ``llvm-premerge-libcxx-release-runners``, and
+   make sure that runner set is using the appropriate image. This ensures that the release branch CI keeps working even
+   if the main branch starts using newer images.
+7. It takes a couple of days before the new LLVM ToT version is available on `<https://apt.llvm.org>`_ after a
----------------
philnik777 wrote:

This isn't up-to-date anymore. We've dropped using https://apt.llvm.org in favour of pulling all our compilers from compiler-explorer.

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