Some man pages were assuming that the "&item" macro
was defined. This change adds that macro and pushes
the affected RST man pages for RTD.
The change also adds a release header for the major
project releases to the relase notes file.
Issue-ID: RIC-510
Signed-off-by: E. Scott Daniels <daniels@research.att.com>
Change-Id: I89b784c4a18ba0ac85aaed2bdde8bda18e3d0946
15 files changed:
Add ability to route messages based on the MEID in a message combined
with the message type/subscription-ID.
Add ability to route messages based on the MEID in a message combined
with the message type/subscription-ID.
-2019 November 14; version 1.11.1 (Amber)
+2019 November 14; version 1.11.1
Fix bug in payload reallocation function; correct length of payload
was not always copied.
2019 November 13; version 1.12.1
New message type constants added to support A1.
Fix bug in payload reallocation function; correct length of payload
was not always copied.
2019 November 13; version 1.12.1
New message type constants added to support A1.
-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.
Version bump to move away from the 1.10.* to distinguish between
release A and the trial.
&li The session to the targeted recipient (endpoint) is not connected.
&half_space
&li The session to the targeted recipient (endpoint) is not connected.
&half_space
&li The payload (actual data)
&half_space
&li The total payload length in bytes
&li The payload (actual data)
&half_space
&li The total payload length in bytes
&li Routing and endpoint selection is based on &ital(message type.)
&half_space
&li Routing and endpoint selection is based on &ital(message type.)
&half_space
.dv beg_list .sp 1 .bl ${1!*} ^: .br
.dv end_list .el .sp 1
.dv li .br .li
.dv beg_list .sp 1 .bl ${1!*} ^: .br
.dv end_list .el .sp 1
.dv li .br .li
.dv ex_start .sp 1 ^:^: .sp 1 .ll -2 .in +2 .nf
.dv ex_end .fo on .in -2 .ll +2 .sp 1
.dv ex_start .sp 1 ^:^: .sp 1 .ll -2 .in +2 .nf
.dv ex_end .fo on .in -2 .ll +2 .sp 1
+.** ------------------------------------------------------------------------
+.** CAUTION: This .xfm file is automatically generated by fmt_changes.ksh
+.** do NOT edit. Use 'make rel-notes.xfm' to regenerate.
+.** ------------------------------------------------------------------------
+
.dv GEN_TITLE 1
.dv doc_title RMR Release Notes
.im setup.im
.dv GEN_TITLE 1
.dv doc_title RMR Release Notes
.im setup.im
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.
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.
endKat
for x in ../../../CHANGES*.txt
do
endKat
for x in ../../../CHANGES*.txt
do
- sed 's/^/!/' $x | awk '
- print_raw && /^!$/ {
+ awk '
+ /^#/ { next } # ditch all comments
+
+ # tag project releases by matching release tag associated
+ /4\.0\.5$/ { printf( "&h1(Bronze Release)\n" ); rheader = 1 }
+ /1\.11\.1$/ { printf( "&h1(Amber Release)\n" ); rheader = 1 }
+
+ print_raw && /^$/ { # include blank lines after first real stuff
printf( "&space\n\n" );
next
}
printf( "&space\n\n" );
next
}
- { gsub ( "!", "", $1 ) }
-
+ print_raw = 1 # safe to print blank lines
printf( "&h2(%s)\n", $0 )
next
}
print_raw { print }
printf( "&h2(%s)\n", $0 )
next
}
print_raw { print }
.** if we can set a license into the output, do it early
.cd 1 11i
&line_len(10i)
.** if we can set a license into the output, do it early
.cd 1 11i
&line_len(10i)
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.
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.
+
+
+Bronze Release
+==============
+
2020 May 06; version 4.0.5
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.
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.
Version bump to move away from the 1.10.* to distinguish
between release A and the trial.
until one of three conditions occurs:
until one of three conditions occurs:
- &item The message is sent without error
+* The message is sent without error
- &item The underlying transport reports a *hard* failure
+* The underlying transport reports a *hard* failure
- &item The maximum number of retry loops has been attempted
+* The maximum number of retry loops has been attempted
A retry loop consists of approximately 1000 send attempts
A retry loop consists of approximately 1000 send attempts
until one of three conditions occurs:
until one of three conditions occurs:
- &item The message is sent without error
+* The message is sent without error
- &item The underlying transport reports a *hard* failure
+* The underlying transport reports a *hard* failure
- &item The maximum number of retry loops has been attempted
+* The maximum number of retry loops has been attempted
A retry loop consists of approximately 1000 send attempts
A retry loop consists of approximately 1000 send attempts
until one of three conditions occurs:
until one of three conditions occurs:
- &item The message is sent without error
+* The message is sent without error
- &item The underlying transport reports a *hard* failure
+* The underlying transport reports a *hard* failure
- &item The maximum number of retry loops has been attempted
+* The maximum number of retry loops has been attempted
A retry loop consists of approximately 1000 send attempts
A retry loop consists of approximately 1000 send attempts
until one of three conditions occurs:
until one of three conditions occurs:
- &item The message is sent without error
+* The message is sent without error
- &item The underlying transport reports a *hard* failure
+* The underlying transport reports a *hard* failure
- &item The maximum number of retry loops has been attempted
+* The maximum number of retry loops has been attempted
A retry loop consists of approximately 1000 send attempts
A retry loop consists of approximately 1000 send attempts
until one of three conditions occurs:
until one of three conditions occurs:
- &item The message is sent without error
+* The message is sent without error
- &item The underlying transport reports a *hard* failure
+* The underlying transport reports a *hard* failure
- &item The maximum number of retry loops has been attempted
+* The maximum number of retry loops has been attempted
A retry loop consists of approximately 1000 send attempts
A retry loop consists of approximately 1000 send attempts
until one of three conditions occurs:
until one of three conditions occurs:
- &item The message is sent without error
+* The message is sent without error
- &item The underlying transport reports a *hard* failure
+* The underlying transport reports a *hard* failure
- &item The maximum number of retry loops has been attempted
+* The maximum number of retry loops has been attempted
A retry loop consists of approximately 1000 send attempts
A retry loop consists of approximately 1000 send attempts