asterisk

History

George Joseph fe9c904a65 test.c: Fix counting of tests and add 2 new tests The unit test XML output was counting all registered tests as "run" even when only a subset were actually requested to be run and the "failures" attribute was missing. * The "tests" attribute of the "testsuite" element in the output XML now reflects only the tests actually requested to be executed instead of all the tests registered. * The "failures" attribute was added to the "testsuite" element. Also added 2 new unit tests that just pass and fail to be used for CI testing. Change-Id: Ia137814b5aeb0e1a44c75034bd3615c26021da69		3 years ago
..
README.md	doc: Fix CHANGES entries to have .txt suffix and update READMEs	6 years ago
app_directory_skip_call.txt	app_directory: Add a 'skip call' option.	3 years ago
app_mixmonitor_mute_by_id.txt	res_mixmonitor: MixMonitorMute by MixMonitor ID	3 years ago
app_read_return_terminator.txt	app_read: Add an option to return terminator on empty digits.	3 years ago
app_senddtmf_answer.txt	app_senddtmf: Add option to answer target channel.	3 years ago
bridge_builtin_features_beep_on_monitor.txt	bridge_builtin_features: add beep via touch variable	3 years ago
cli_channel_display_length_increase.txt	cli: increase channel column width	3 years ago
format_sln_support_for_slin.txt	format_sln: add .slin as supported file extension	3 years ago
test.txt	test.c: Fix counting of tests and add 2 new tests	3 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 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