Fix potential race in route table load
If route tables are received in quick succession there is a potential
race condition that can cause the xAPPs thread to use a stale pointer
likely resulting in a segfault.
Issue-ID: RIC-674
Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: I5536d3f30646dca0ed375468719fa3cf0920c103
Signed-off-by: E. Scott Daniels <daniels@research.att.com>
diff --git a/docs/rel-notes.rst b/docs/rel-notes.rst
index d244c0c..a37304b 100644
--- a/docs/rel-notes.rst
+++ b/docs/rel-notes.rst
@@ -22,6 +22,14 @@
version 4.0.0, the RMR versions should no longer skip.
+2020 November 4; Version 4.4.0
+------------------------------
+
+Changes to address a potential race condition when route
+tables arrive in quick succession. (RIC-674)
+
+
+
2020 October 30; Version 4.3.1
------------------------------