asterisk

History

George Joseph 3f093b8dda bundled_pjproject: Make it easier to hack There are times when you need to troubleshoot issues with bundled pjproject or add new features that need to be pushed upstream but... * The source directory created by extracting the pjproject tarball is not scanned for code changes so you have to keep forcing rebuilds. * The source directory isn't a git repo so you can't easily create patches, do git bisects, etc. * Accidentally doing a make distclean will ruin your day by wiping out the source directory, and your changes. * etc. This commit makes that easier. See third-party/pjproject/README-hacking.md for the details. ASTERISK-29824 Change-Id: Idb1251040affdab31d27cd272dda68676da9b268		3 years ago
..
README.md	doc: Fix CHANGES entries to have .txt suffix and update READMEs	5 years ago
ami_wink.txt	ami: Add AMI event for Wink	3 years ago
app_mf_mf.txt	app_mf: Add full tech-agnostic MF support	4 years ago
app_queue_DIALEDPEERNUMBER.txt	app_queue.c: added DIALEDPEERNUMBER on outgoing channel	4 years ago
app_queue_nordic_language.txt	app_queue.c: Support for Nordic syntax in announcements	3 years ago
app_sendtext.txt	app_sendtext: Add ReceiveText application	4 years ago
app_voicemail_danish_syntax.txt	app_voicemail.c: Support for Danish syntax in VM	4 years ago
bundled-pjproject-build.txt	bundled_pjproject: Make it easier to hack	3 years ago
cli_refresh.txt	cli: Add module refresh command	3 years ago
func_json.txt	func_json: Adds JSON_DECODE function	4 years ago
res_fax_spandsp.txt	res_fax_spandsp: Add spandsp 3.0.0+ compatibility	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 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