sysmocom
/
asterisk
11
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Remove obsolete CHANGES-staging and UPGRADE-staging directories 

These should have been deleted after the release of 21.0.0
but were missed.

(cherry picked from commit df958a7d63)
This commit is contained in:
George Joseph 2023-12-15 09:56:54 -07:00 committed by Asterisk Development Team
parent ce29be5536
commit c0843b907a
13 changed files with 0 additions and 178 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
doc/CHANGES-staging/README.md
View File

@ -1,37 +0,0 @@
## **DO NOT REMOVE THIS FILE!**
The only files that should be added to this directory are ones that will be
used by the release script to update the CHANGES file automatically. The only
time that it is necessary to add something to the CHANGES-staging directory is
if you are either adding a new feature to Asterisk or adding new functionality
to an existing feature. The file does not need to have a meaningful name, but
it probably should. If there are multiple items that need documenting, you can
add multiple files, each with their own description. If the message is going to
be the same for each subject, then you can add multiple subject headers to one
file. The "Subject: xxx" line is case sensitive! For example, if you are making
a change to PJSIP, then you might add the file "res_pjsip_my_cool_feature.txt" to
this directory, with a short description of what it does. The files must have
the ".txt" suffix. If you are adding multiple entries, they should be done in
the same commit to avoid merge conflicts. Here's an example:
> Subject: res_pjsip
> Subject: Core
>
> Here's a pretty good description of my new feature that explains exactly what
> it does and how to use it.
Here's a master-only example:
> Subject: res_ari
> Master-Only: True
>
> This change will only go into the master branch. The "Master-Only" header
> will never be in a change not in master.
Note that the second subject has another header: "Master-Only". Changes that go
into the master branch and ONLY the master branch are the only ones that should
have this header. Also, the value can only be "true" or "True". The
"Master-Only" part of the header IS case-sensitive, however!
For more information, check out the wiki page:
https://wiki.asterisk.org/wiki/display/AST/CHANGES+and+UPGRADE.txt

6
doc/CHANGES-staging/http_bindaddr.txt
View File

@ -1,6 +0,0 @@
Subject: http
Master-Only: True
For bound addresses, the HTTP status page now combines the bound
address and bound port in a single line. Additionally, the SSL bind
address has been renamed to TLS.

37
doc/UPGRADE-staging/README.md
View File

@ -1,37 +0,0 @@
## **DO NOT REMOVE THIS FILE!**
The only files that should be added to this directory are ones that will be
used by the release script to update the UPGRADE.txt file automatically. The
only time that it is necessary to add something to the UPGRADE-staging directory
is if you are making a breaking change to an existing feature in Asterisk. The
file does not need to have a meaningful name, but it probably should. If there
are multiple items that need documenting, you can add multiple files, each with
their own description. If the message is going to be the same for each subject,
then you can add multiple subject headers to one file. The "Subject: xxx" line
is case sensitive! For example, if you are making a change to PJSIP, then you
might add the file "res_pjsip_my_cool_feature.txt" to this directory, with a
short description of what it does. The files must have the ".txt" suffix.
If you are adding multiple entries, they should be done in the same commit
to avoid merge conflicts. Here's an example:
> Subject: res_pjsip
> Subject: Core
>
> Here's a pretty good description of my new feature that explains exactly what
> it does and how to use it.
Here's a master-only example:
> Subject: res_ari
> Master-Only: True
>
> This change will only go into the master branch. The "Master-Only" header
> will never be in a change not in master.
Note that the second subject has another header: "Master-Only". Changes that go
into the master branch and ONLY the master branch are the only ones that should
have this header. Also, the value can only be "true" or "True". The
"Master-Only" part of the header IS case-sensitive, however!
For more information, check out the wiki page:
https://wiki.asterisk.org/wiki/display/AST/CHANGES+and+UPGRADE.txt

6
doc/UPGRADE-staging/app_cdr.txt
View File

@ -1,6 +0,0 @@
Subject: app_cdr
Master-Only: True
The previously deprecated NoCDR application has been removed.
Additionally, the previously deprecated 'e' option to the ResetCDR
application has been removed.

37
doc/UPGRADE-staging/app_macro_removal.txt
View File

@ -1,37 +0,0 @@
Subject: app_macro
Master-Only: True
This module was deprecated in Asterisk 16
and is now being removed in accordance with
the Asterisk Module Deprecation policy.
For most modules that interacted with app_macro,
this change is limited to no longer looking for
the current context from the macrocontext when set.
The following modules have additional impacts:
app_dial - no longer supports M^ connected/redirecting macro
app_minivm - samples written using macro will no longer work.
The sample needs to be re-written
app_queue - can no longer call a macro on the called party's
channel. Use gosub which is currently supported
ccss - no callback macro, gosub only
app_voicemail - no macro support
channel - remove macrocontext and priority, no connected
line or redirection macro options
options - stdexten is deprecated to gosub as the default
and only options
pbx - removed macrolock
pbx_dundi - no longer look for macro
snmp - removed macro context, exten, and priority

6
doc/UPGRADE-staging/app_osplookup_removal.txt
View File

@ -1,6 +0,0 @@
Subject: app_osplookup
Master-Only: True
This module was deprecated in Asterisk 19
and is now being removed in accordance with
the Asterisk Module Deprecation policy.

6
doc/UPGRADE-staging/chan_alsa_removal.txt
View File

@ -1,6 +0,0 @@
Subject: chan_alsa
Master-Only: True
This module was deprecated in Asterisk 19
and is now being removed in accordance with
the Asterisk Module Deprecation policy.

7
doc/UPGRADE-staging/chan_mgcp_removal.txt
View File

@ -1,7 +0,0 @@
Subject: chan_mgcp
Master-Only: True
This module was deprecated in Asterisk 19
and is now being removed in accordance with
the Asterisk Module Deprecation policy.

6
doc/UPGRADE-staging/chan_sip_removal.txt
View File

@ -1,6 +0,0 @@
Subject: chan_sip
Master-Only: True
This module was deprecated in Asterisk 17
and is now being removed in accordance with
the Asterisk Module Deprecation policy.

6
doc/UPGRADE-staging/chan_skinny_removal.txt
View File

@ -1,6 +0,0 @@
Subject: chan_skinny
Master-Only: True
This module was deprecated in Asterisk 19
and is now being removed in accordance with
the Asterisk Module Deprecation policy.

5
doc/UPGRADE-staging/pbx_builtins.txt
View File

@ -1,5 +0,0 @@
Subject: pbx_builtins
Master-Only: True
The previously deprecated ImportVar and SetAMAFlags
applications have now been removed.

13
doc/UPGRADE-staging/res_monitor_removal.txt
View File

@ -1,13 +0,0 @@
Subject: res_monitor
Master-Only: True
This module was deprecated in Asterisk 16
and is now being removed in accordance with
the Asterisk Module Deprecation policy.
This also removes the 'w' and 'W' options
for app_queue.
MixMonitor should be default and only option
for all settings that previously used either
Monitor or MixMonitor.

6
doc/UPGRADE-staging/translate.txt
View File

@ -1,6 +0,0 @@
Subject: translate.c
Master-Only: True
When setting up translation between two codecs the quality was not taken into account,
resulting in suboptimal translation. The quality is now taken into account,
which can reduce the number of translation steps required, and improve the resulting quality.