v3.10.0

docs/release-notes.md

@@ -2,6 +2,7 @@
 
 # Release notes
 **Contents**<br>
+[3.10.0](#3100)<br>
 [3.9.1](#391)<br>
 [3.9.0](#390)<br>
 [3.8.1](#381)<br>
@@ -69,6 +70,19 @@
 [Even Older versions](#even-older-versions)<br>
 
 
+## 3.10.0
+
+### Fixes
+* pkg-config files will take `DESTDIR` env var into account when selecting install destination (#3006, #3019)
+* Changed `filter` to store the provided predicate by value (#3002, #3005)
+  * This is done to avoid dangling-by-default behaviour when `filter` is used inside `GENERATE_COPY`/`GENERATE_REF`.
+
+### Improvements
+* Escaping XML and JSON output is faster when the strings do not need escaping.
+  * The improvement starts at about 3x throughput, up to 10x for long strings.
+* Message macros (`INFO`, `CAPTURE`, `WARN`, `SUCCEED`, etc) are now thread safe.
+
+
 ## 3.9.1
 
 ### Fixes

docs/thread-safety.md

@@ -44,6 +44,8 @@ they are assertion macro + an if).
 
 ## Assertion-like message macros and spawned threads
 
+> Assertion-like messages were made thread safe in Catch2 3.10.0
+
 Similarly to assertion macros, not all assertion-like message macros can
 be used from spawned thread.
 
@@ -55,6 +57,8 @@ thus can be used from any thread.
 
 ## Message macros and spawned threads
 
+> Message macros were made thread safe in Catch2 3.10.0
+
 Macros that add extra messages to following assertion, such as `INFO`
 or `CAPTURE`, are all thread safe and can be used in any thread. Note
 that these messages are per-thread, and thus `INFO` inside a user-spawned