3.1.0). When the wrapper code was moved to a different repo
the need to leap frog versions ceased, and beginning with
version 4.0.0, the RMR versions should no longer skip.
+
+
+2020 June 22; version 4.1.1
+---------------------------
+
+Add new message types to RIC header file for
+ RIC_ALARM (110)
+ RIC_ALARM_QUERY (111)
+ RIC_METRICS (120)
+ RAN_E2_RESET_REQ (12008)
+ RAN_E2_RESET_RESP (12009)
+
+
+
+2020 June 18; version 4.1.0
+---------------------------
+
+Bump version minor to move away from 4.0.* which will bump
+for any patches applied back to bronze.
+Add magic C++ goo to symtab header file allowing C++ xAPPs to
+use the symbol table directly.
+
+
+
+Bronze Release
+==============
+
2020 May 06; version 4.0.5
-2019 November 14; version 1.11.1 (Amber)
-----------------------------------------
+Amber Release
+=============
+
+
+
+2019 November 14; version 1.11.1
+--------------------------------
Fix bug in payload reallocation function; correct length of
payload was not always copied.
-2019 November 4; version 1.11.0 (Amber)
----------------------------------------
+2019 November 4; version 1.11.0
+-------------------------------
Version bump to move away from the 1.10.* to distinguish
between release A and the trial.
2019 September 19; version 1.8.0
--------------------------------
-New message types added: RAN_CONNECTED, RAN_RESTARTED,
-RAN_RECONFIGURED
+New message types added:
+ RAN_CONNECTED, RAN_RESTARTED, RAN_RECONFIGURED
---------------------------------------------
Support for the Nanomsg transport library has been dropped.
-The library librmr.* will no longer be included in packages.
+ The library librmr.* will no longer be included in packages.
Packages will install RMR libraries into the system preferred
-target directory. On some systems this is /usr/local/lib and
-on others it is /usr/local/lib64. The diretory is determined
-by the sytem on which the package is built and NOT by the
-system installing the package, so it's possible that the RMR
-libraries end up in a strange location if the .deb or .rpm
-file was generated on a Linux flavour that has a different
-preference than the one where the package is installed.
+ target directory. On some systems this is /usr/local/lib
+ and on others it is /usr/local/lib64. The diretory is
+ determined by the sytem on which the package is built and
+ NOT by the system installing the package, so it's possible
+ that the RMR libraries end up in a strange location if the
+ .deb or .rpm file was generated on a Linux flavour that
+ has a different preference than the one where the package
+ is installed.
----------------------------
-librmr and librmr_nng - Add message buffer API function
-rmr_trace_ref() (see rmr_trace_ref.3 manual page in dev
-package).
+librmr and librmr_nng
+ - Add message buffer API function rmr_trace_ref()
+ (see rmr_trace_ref.3 manual page in dev package).