[libc++] Reword release note section about future releases #138544
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
|
@llvm/pr-subscribers-libcxx Author: Louis Dionne (ldionne) ChangesFor 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:
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.