Lines Matching +full:release +full:- +full:version

4 Release procedure
7 The LLVM project creates a new release twice a year following a fixed
8 `schedule <https://llvm.org/docs/HowToReleaseLLVM.html#annual-release-schedule>`__.
9 This page describes the libc++ procedure for that release.
11 Prepare the release
16 It should be finished before the Release managers start branching the new
17 release:
19 * Make sure ``libcxx/docs/ReleaseNotes/<VERSION>.rst`` is up to date. Typically
24   new deprecated feature should be added to the release notes and this page.
27 * Make sure the latest Unicode version is used. The C++ Standard
32   Typically the Unicode Consortium has one release per year. The libc++
34   latest Unicode version. Updating means using the latest data files and, if
38   latest release.
43 This is done by the LLVM Release managers.
45 After branching for an LLVM release:
48 2. Update the version number in ``libcxx/docs/conf.py``
51 5. Create a release notes file for the next release from the template
52 6. Point to the new release notes file from ``libcxx/docs/ReleaseNotes.rst``
59 After branching it takes a couple of days before the new LLVM ToT version is
60 available on `<https://apt.llvm.org>`_. Once it is available the pre-commit CI
61 can start using the new ToT version. In order to make sure patches can be
62 backported to the release branch the oldest compiler is not removed yet.
64 The section ``Upcoming Deprecations and Removals`` is cleared by the release
67 The items that need changing are marked with ``LLVM POST-BRANCH``.
69 Post release
74 Support for the ToT - 3 version is removed:
76 - Search for ``LLVM RELEASE`` and address their comments
77 - Search for test that have ``UNSUPPORTED`` or ``XFAIL`` for the no longer supported version
78 - Search for ``TODO(LLVM-<ToT>)`` and address their comments