From: Asterisk Development Team <asteriskteam@digium.com>
Date: Thu, 12 Nov 2020 11:50:09 +0000 (-0500)
Subject: Update CHANGES and UPGRADE.txt for 18.1.0
X-Git-Tag: 18.1.0-rc1~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=98d1537c1eab8334416238091632025325297319;p=thirdparty%2Fasterisk.git

Update CHANGES and UPGRADE.txt for 18.1.0
---

diff --git a/CHANGES b/CHANGES
index b164c45598..7eb52e8d29 100644
--- a/CHANGES
+++ b/CHANGES
@@ -12,6 +12,36 @@
 ===
 ==============================================================================
 
+------------------------------------------------------------------------------
+--- Functionality changes from Asterisk 18.0.0 to Asterisk 18.1.0 ------------
+------------------------------------------------------------------------------
+
+Core
+------------------
+ * Added debug logging categories that allow a user to output debug information
+   based on a specified category. This lets the user limit, and filter debug
+   output to data relevant to a particular context, or topic. For instance the
+   following categories are now available for debug logging purposes:
+
+     dtls, dtls_packet, ice, rtcp, rtcp_packet, rtp, rtp_packet, stun, stun_packet
+
+   These debug categories can be enable/disable via an Asterisk CLI command:
+
+     core set debug category <category>[:<sublevel>] [category[:<sublevel] ...]
+     core set debug category off [<category> [<category>] ...]
+
+   If no sub-level is associated all debug statements for a given category are
+   output. If a sub-level is given then only those statements assigned a value
+   at or below the associated sub-level are output.
+
+app_confbridge
+------------------
+ * app_confbridge now has the ability to force the estimated bitrate on an SFU
+   bridge.  To use it, set a bridge profile's remb_behavior to "force" and
+   set remb_estimated_bitrate to a rate in bits per second.  The
+   remb_estimated_bitrate parameter is ignored if remb_behavior is something
+   other than "force".
+
 ------------------------------------------------------------------------------
 --- Functionality changes from Asterisk 17.0.0 to Asterisk 18.0.0 ------------
 ------------------------------------------------------------------------------
diff --git a/doc/CHANGES-staging/app_confbridge.txt b/doc/CHANGES-staging/app_confbridge.txt
deleted file mode 100644
index 092e392f5d..0000000000
--- a/doc/CHANGES-staging/app_confbridge.txt
+++ /dev/null
@@ -1,7 +0,0 @@
-Subject: app_confbridge
-
-app_confbridge now has the ability to force the estimated bitrate on an SFU
-bridge.  To use it, set a bridge profile's remb_behavior to "force" and
-set remb_estimated_bitrate to a rate in bits per second.  The
-remb_estimated_bitrate parameter is ignored if remb_behavior is something
-other than "force".
diff --git a/doc/CHANGES-staging/logger_category.txt b/doc/CHANGES-staging/logger_category.txt
deleted file mode 100644
index 67cc3ec7ad..0000000000
--- a/doc/CHANGES-staging/logger_category.txt
+++ /dev/null
@@ -1,18 +0,0 @@
-Subject: Core
-
-Added debug logging categories that allow a user to output debug information
-based on a specified category. This lets the user limit, and filter debug
-output to data relevant to a particular context, or topic. For instance the
-following categories are now available for debug logging purposes:
-
-  dtls, dtls_packet, ice, rtcp, rtcp_packet, rtp, rtp_packet, stun, stun_packet
-
-These debug categories can be enable/disable via an Asterisk CLI command:
-
-  core set debug category <category>[:<sublevel>] [category[:<sublevel] ...]
-  core set debug category off [<category> [<category>] ...]
-
-If no sub-level is associated all debug statements for a given category are
-output. If a sub-level is given then only those statements assigned a value
-at or below the associated sub-level are output.
-