-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Synchronize Unicode license text from unicode.org #133236
Conversation
The text of <https://unicode.org/license.txt> was swapped out from "UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE" to "UNICODE LICENSE V3" between the dates of 2023.06.03 and 2023.09.11, which means between Unicode 15.0.0 (2022.09.13) and Unicode 15.1.0 (2023.09.12). https://web.archive.org/web/20230603182532/https://www.unicode.org/license.txt https://web.archive.org/web/20230911222703/https://www.unicode.org/license.txt https://unicode.org/versions/Unicode15.0.0/ https://unicode.org/versions/Unicode15.1.0/ A license wording change is not mentioned in the 15.1.0 release summary or announcement post. https://www.unicode.org/versions/Unicode15.1.0/ http://blog.unicode.org/2023/09/announcing-unicode-standard-version-151.html But I guess we are intended to infer that data files from Unicode 15.1.0 should be specified as licensed Unicode-3.0 as opposed to Unicode-DFS-2016. https://spdx.org/licenses/Unicode-3.0.html https://spdx.org/licenses/Unicode-DFS-2016.html
rustbot has assigned @Mark-Simulacrum. Use |
@bors r+ rollup=iffy |
☀️ Test successful - checks-actions |
Finished benchmarking commit (67a8c64): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.
Max RSS (memory usage)Results (secondary -2.7%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
CyclesResults (secondary -3.9%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 796.657s -> 795.632s (-0.13%) |
The text of https://unicode.org/license.txt was swapped out from "UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE" to "UNICODE LICENSE V3" between the dates of 2023.06.03 and 2023.09.11, which means between Unicode 15.0.0 (2022.09.13) and Unicode 15.1.0 (2023.09.12). A license wording change is not mentioned in the 15.1.0 release summary or announcement post. But I guess we are intended to infer that data files from Unicode 15.1.0 should be specified as licensed Unicode-3.0 as opposed to Unicode-DFS-2016.
The Rust standard library has been using Unicode 15.1.0+ since #120777.