Add 2.10.3 changelog

doc/release/2.10.2.rst

@@ -11,8 +11,7 @@ Overview
 
 2.10.2 is the third
 :doc:`stable </release/policy/>` version of the 2.10 release series.
-version of the 2.10 release series. It introduces 1 improvement and
-resolves 8 bugs since 2.10.1.
+It introduces 1 improvement and resolves 8 bugs since 2.10.1.
 
 The “stable” label means that we have all planned features implemented
 and we see no high-impact issues. However, if you encounter an issue,

doc/release/2.10.3.rst

@@ -0,0 +1,126 @@
+Tarantool 2.10.3
+================
+
+Released on 2022-09-30.
+
+*   Release: :tarantool-release:`2.10.3`.
+*   Tag: ``2.10.3``.
+
+Overview
+--------
+
+2.10.3 is the fourth
+:doc:`stable </release/policy/>` version of the 2.10 release series.
+It introduces 2 improvements and resolves 19 bugs since 2.10.2.
+
+The “stable” label means that we have all planned features implemented
+and we see no high-impact issues. However, if you encounter an issue,
+feel free to `report it <https://github.com/tarantool/tarantool/issues>`__ on GitHub.
+
+Compatibility
+-------------
+
+Tarantool 2.x is backward compatible with Tarantool 1.10.x in the binary
+data layout, client-server protocol, and replication protocol.
+
+Please :doc:`upgrade </book/admin/upgrades>`
+using the ``box.schema.upgrade()`` procedure to unlock all the new
+features of the 2.x series.
+
+Functionality added or changed
+------------------------------
+
+Build
+~~~~~
+
+-  RedOS 7.3 is now supported.
+-  Added the ``-DENABLE_HARDENING=ON/OFF`` CMake option that enables
+   hardening against memory corruption attacks (:tarantool-issue:`7536`).
+
+Bugs fixed
+----------
+
+Core
+~~~~
+
+-  Fixed a bug introduced in Tarantool 2.10.2: log messages could be
+   written to data files thus causing data corruption. The issue was
+   fixed by reverting the fix for :tarantool-issue:`4450`.
+-  Switched from MT-Unsafe ``strerror()`` to MT-Safe ``strerror_r()``.
+   The usage of the unsafe function could result in corrupted error
+   messages.
+-  Fixed a bug when a single JSON update couldn’t insert and update a
+   field of a map or an array in two sequential calls. It would either
+   crash or return an error (:tarantool-issue:`7705`).
+
+Memtx
+~~~~~
+
+-  Fixed incorrect handling of transaction conflicts in full scans by
+   HASH indexes (:tarantool-issue:`7493`).
+-  Fixed ``use after free`` that could occur in the transaction manager
+   in certain states (:tarantool-issue:`7449`).
+-  Fixed possible phantom reads with ``get`` on TREE indexes containing
+   nullable parts (:tarantool-issue:`7685`).
+-  Fixed an inconsistency in ``index:random`` in the context of
+   transaction management (:tarantool-issue:`7670`).
+-  Fixed unserializable reads tracked incorrectly after transaction
+   rollbacks (:tarantool-issue:`7343`).
+
+Replication
+~~~~~~~~~~~
+
+-  Fixed a bug when a fiber committing a synchronous transaction could
+   hang if the instance got a term bump during that or its synchro-queue
+   was fenced in any other way (:tarantool-issue:`7253`).
+-  Fixed master occasionally deleting xlogs needed by replicas even
+   without a restart (:tarantool-issue:`7584`).
+
+Raft
+~~~~
+
+-  Fixed a bug when ``box.ctl.promote()`` could hang and bump thousands
+   of terms in a row if called on more than one node at the same time
+   (part of :tarantool-issue:`7253`).
+-  Fixed a bug when a node with ``election_mode='voter'`` could hang in
+   ``box.ctl.promote()`` or become a leader (part of :tarantool-issue:`7253`).
+-  Fixed a bug when a replicaset could be split into parts if a node
+   voted for another instance while having local WAL writes unfinished
+   (part of :tarantool-issue:`7253`).
+
+Lua
+~~~
+
+Merger
+^^^^^^
+
+-  Fixed ``use after free`` that could occur during iteration over
+   ``merge_source:pairs()`` or ``merger:pairs()`` (:tarantool-issue:`7657`).
+
+Popen
+^^^^^
+
+-  Fixed a race condition in ``<popen handle>:signal()`` on Mac OS 12
+   and newer (:tarantool-issue:`7658`).
+
+Box
+~~~
+
+-  Fixed a bug when ``fiber.yield()`` might break the execution of a
+   shutdown trigger (:tarantool-issue:`7434`).
+-  Fixed a possible high CPU usage caused by shutdown triggers
+   (:tarantool-issue:`6801`).
+
+Synchro
+~~~~~~~
+
+-  Fixed assertions in debug builds and undefined behaviour in release
+   builds when simultaneous elections started or another instance was
+   promoted while an instance was acquiring or releasing the synchro
+   queue (:tarantool-issue:`7086`).
+
+Uri
+~~~
+
+-  Fixed a bug in the URI parser: tarantoolctl could not connect when
+   the host name was skipped (:tarantool-issue:`7479`).

doc/release/2.10_series.rst

@@ -7,6 +7,7 @@ Tarantool 2.10 series includes the following releases:
 ..  toctree::
     :maxdepth: 1
 
+    2.10.3
     2.10.2
     2.10.1
     2.10.0

doc/release/calendar.rst

@@ -30,6 +30,10 @@ End of series support means the release series will no longer receive any patche
             -   Release date
             -   End of series support
 
+        *   -   :doc:`2.10.3 </release/2.10.3>`
+            -   September 30, 2022
+            -   Not planned yet
+
         *   -   :doc:`2.10.2 </release/2.10.2>`
             -   September 1, 2022
             -   Not planned yet

doc/release/major-features.rst

@@ -20,6 +20,11 @@ Versions that only include bug fixes are not listed in this table.
         *   -   Since version
             -   Feature
 
+        *   -   2.10.3
+            -   RedOS 7.3 is now supported.  |br|
+                Added the ``-DENABLE_HARDENING=ON/OFF`` CMake option that enables
+                hardening against memory corruption attacks (:tarantool-issue:`7536`).
+
         *   -   2.10.2
             -   Internal fibers cannot be cancelled from the Lua public API anymore (:tarantool-issue:`7473`)