kenmirrors/asterisk
1
0
Fork 0
mirror of https://github.com/asterisk/asterisk.git synced 2025-10-10 06:49:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Add version information to configObject and configOption XML elements

Browse Source 
Most of the configObjects and configOptions that are implemented with
ACO or Sorcery now have `<since>/<version>` elements added.  There are
probably some that the script I used didn't catch.  The version tags were
determined by the following...
 * Do a git blame on the API call that created the object or option.
 * From the commit hash, grab the summary line.
 * Do a `git log --grep <summary>` to find the cherry-pick commits in all
   branches that match.
 * Do a `git patch-id` to ensure the commits are all related and didn't get
   a false match on the summary.
 * Do a `git tag --contains <commit>` to find the tags that contain each
   commit.
 * Weed out all tags not <major>.<minor>.0.
 * Sort and discard any <major>.0.0 and following tags where the commit
   appeared in an earlier branch.
 * The result is a single tag for each branch where the API was last touched.

configObjects and configOptions elements implemented with the base
ast_config APIs were just not possible to find due to the non-deterministic
way they are accessed.

Also note that if the API call was on modified after it was added, the
version will be the one it was last modified in.

Final note:  The configObject and configOption elements were introduced in
12.0.0 so options created before then may not have any XML documentation.
This commit is contained in:
George Joseph
2025-01-16 14:54:35 -07:00
parent 317b830c1e
commit a22dc33057
31 changed files with 650 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
res/res_pjproject.c
View File

@@ -67,6 +67,7 @@
</configOption>
</configObject>
<configObject name="log_mappings">
<since><version>13.8.0</version></since>
<synopsis>PJPROJECT to Asterisk Log Level Mapping</synopsis>
<description><para>Warnings and errors in the pjproject libraries are generally handled
by Asterisk. In many cases, Asterisk wouldn't even consider them to
@@ -78,24 +79,31 @@
'log_mappings' or it won't be found.</para></note>
</description>
<configOption name="type">
<since><version>13.8.0</version></since>
<synopsis>Must be of type 'log_mappings'.</synopsis>
</configOption>
<configOption name="asterisk_error" default="0,1">
<since><version>13.8.0</version></since>
<synopsis>A comma separated list of pjproject log levels to map to Asterisk LOG_ERROR.</synopsis>
</configOption>
<configOption name="asterisk_warning" default="2">
<since><version>13.8.0</version></since>
<synopsis>A comma separated list of pjproject log levels to map to Asterisk LOG_WARNING.</synopsis>
</configOption>
<configOption name="asterisk_notice" default="">
<since><version>13.8.0</version></since>
<synopsis>A comma separated list of pjproject log levels to map to Asterisk LOG_NOTICE.</synopsis>
</configOption>
<configOption name="asterisk_verbose" default="">
<since><version>13.8.0</version></since>
<synopsis>A comma separated list of pjproject log levels to map to Asterisk LOG_VERBOSE.</synopsis>
</configOption>
<configOption name="asterisk_debug" default="3,4">
<since><version>13.8.0</version></since>
<synopsis>A comma separated list of pjproject log levels to map to Asterisk LOG_DEBUG.</synopsis>
</configOption>
<configOption name="asterisk_trace" default="5,6">
<since><version>16.21.0</version><version>18.7.0</version></since>
<synopsis>A comma separated list of pjproject log levels to map to Asterisk LOG_TRACE.</synopsis>
</configOption>
</configObject>