You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
asterisk/doc/UPGRADE-staging
Joshua C. Colp 0ddeac0e36
res_monitor: Disable building by default.
4 years ago
..
README.md doc: Fix CHANGES entries to have .txt suffix and update READMEs 5 years ago
app_dahdiras_removal.txt app_dahdiras: Remove deprecated module. 4 years ago
app_fax_removal.txt app_fax: Remove deprecated module. 4 years ago
app_ices_removal.txt app_ices: Remove deprecated module. 4 years ago
app_image_removal.txt app_image: Remove deprecated module. 4 years ago
app_meetme_deprecation.txt policy: Deprecate modules and add versions to others. 4 years ago
app_mysql_removal.txt app_mysql: Remove deprecated module. 4 years ago
app_nbscat_removal.txt app_nbscat: Remove deprecated module. 4 years ago
app_osplookup_deprecation.txt policy: Deprecate modules and add versions to others. 4 years ago
app_url_removal.txt app_url: Remove deprecated module. 4 years ago
cdr_mysql_removal.txt cdr_mysql: Remove deprecated module. 4 years ago
cdr_syslog_removal.txt cdr_syslog: Remove deprecated module. 4 years ago
chan_alsa_deprecation.txt policy: Deprecate modules and add versions to others. 4 years ago
chan_mgcp_deprecation.txt policy: Deprecate modules and add versions to others. 4 years ago
chan_misdn_removal.txt chan_misdn: Remove deprecated module. 4 years ago
chan_nbs_removal.txt chan_nbs: Remove deprecated module. 4 years ago
chan_oss_removal.txt chan_oss: Remove deprecated module. 4 years ago
chan_phone_removal.txt chan_phone: Remove deprecated module. 4 years ago
chan_skinny_deprecation.txt policy: Deprecate modules and add versions to others. 4 years ago
chan_vpb_removal.txt chan_vpb: Remove deprecated module. 4 years ago
conf2ael_removal.txt conf2ael: Remove deprecated application. 4 years ago
http-media-cache-lookup-order.txt res_http_media_cache: Cleanup audio format lookup in HTTP requests 4 years ago
muted_removal.txt muted: Remove deprecated application. 4 years ago
res_config_sqlite_removal.txt res_config_sqlite: Remove deprecated module. 4 years ago
res_monitor_disabled.txt res_monitor: Disable building by default. 4 years ago
res_pktccops_deprecation.txt policy: Deprecate modules and add versions to others. 4 years ago

README.md

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