Skip to content

[libc++] Reword release note section about future releases #138544

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ldionne
Copy link
Member

@ldionne ldionne commented May 5, 2025

For several releases, we had a section in the release notes that was called "Upcoming Deprecations and Removals". That section was used to advertize breaking changes in future releases as opposed to ones in the current release.

However, the way this section was worded and organized made it unclear what release these announcements related to. This patch rewords that section of the release notes to make it less ambiguous and moves items that aren't done yet (but relate to the ongoing release) to a different section with a TODO.

For several releases, we had a section in the release notes that was
called "Upcoming Deprecations and Removals". That section was used to
advertize breaking changes in future releases as opposed to ones in the
current release.

However, the way this section was worded and organized made it unclear
what release these announcements related to. This patch rewords that
section of the release notes to make it less ambiguous and moves items
that aren't done yet (but relate to the ongoing release) to a different
section with a TODO.
@ldionne ldionne requested a review from a team as a code owner May 5, 2025 15:38
@llvmbot llvmbot added the libc++ libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi. label May 5, 2025
@llvmbot
Copy link
Member

llvmbot commented May 5, 2025

@llvm/pr-subscribers-libcxx

Author: Louis Dionne (ldionne)

Changes

For several releases, we had a section in the release notes that was called "Upcoming Deprecations and Removals". That section was used to advertize breaking changes in future releases as opposed to ones in the current release.

However, the way this section was worded and organized made it unclear what release these announcements related to. This patch rewords that section of the release notes to make it less ambiguous and moves items that aren't done yet (but relate to the ongoing release) to a different section with a TODO.


Full diff: https://github.com/llvm/llvm-project/pull/138544.diff

1 Files Affected:

  • (modified) libcxx/docs/ReleaseNotes/21.rst (+5-10)
diff --git a/libcxx/docs/ReleaseNotes/21.rst b/libcxx/docs/ReleaseNotes/21.rst
index a7382c5222d08..c571dd6f08fe9 100644
--- a/libcxx/docs/ReleaseNotes/21.rst
+++ b/libcxx/docs/ReleaseNotes/21.rst
@@ -80,16 +80,18 @@ Deprecations and Removals
 - The ``_LIBCPP_VERBOSE_ABORT_NOT_NOEXCEPT`` has been removed, making ``std::__libcpp_verbose_abort``
   unconditionally ``noexcept``.
 
+- TODO: The non-conforming extension ``packaged_task::result_type`` has been removed in LLVM 21.
+
 Potentially breaking changes
 ----------------------------
 
 - The implementation of ``num_put::do_put`` has been replaced to improve the performance, which can lead to different
   output when printing pointers.
 
-Upcoming Deprecations and Removals
-----------------------------------
+Announcements About Future Releases
+-----------------------------------
 
-LLVM 21
+LLVM 22
 ~~~~~~~
 
 - The status of the C++03 implementation will be frozen after the LLVM 21 release. This means that starting in LLVM 22,
@@ -101,13 +103,6 @@ LLVM 21
   If you are using C++03 in your project, you should consider moving to a newer version of the Standard to get the most
   out of libc++.
 
-- Non-conforming extension ``packaged_task::result_type`` will be removed in LLVM 21.
-
-LLVM 22
-~~~~~~~
-
-- TODO
-
 
 ABI Affecting Changes
 ---------------------

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
libc++ libc++ C++ Standard Library. Not GNU libstdc++. Not libc++abi.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants