[asterisk-bugs] [JIRA] (ASTERISK-29021) [patch] Fix VERSION(ASTERISK_VERSION_NUM) on certified versions

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-29021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251598#comment-251598 ] 

Asterisk Team commented on ASTERISK-29021:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> [patch] Fix VERSION(ASTERISK_VERSION_NUM) on certified versions
> ---------------------------------------------------------------
>
>                 Key: ASTERISK-29021
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29021
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Functions/func_version
>    Affects Versions: 16.8.0
>            Reporter: cmaj
>            Severity: Minor
>
> The output of ${VERSION(ASTERISK_VERSION_NUM)} normally produces an integer of 6 digits, eg. Asterisk 16.8.0 produces 160800.
> There is corner case for git/svn pulls that should produce 999999, which makes sense (although 169999, 179999, 189999, etc. might make more sense.)
> Anyhow, certified versions fail to parse in reasonable manner; eg. Asterisk certified version 16.3-cert1 produces 00300, while both Asterisk certified versions 16.8-cert2 and 16.8-cert3 produce the same number 00800. This prevents dial plans from making adjustments on-the-fly to support earlier or later versions of Asterisk using different call flows.
> Pending patch adds a sed pipe before awk in Makefile to produce output like 160301, 160802, 160803, etc. The trade-off is potential conflict with non-certified versions if naming is not carefully considered, but none of the certified version 16's released so far would cause this problem because the naming is already being carefully considered (there is no 16.3.1, 16.8.2, or 16.8.3 in the non-certified releases.)



--
This message was sent by Atlassian JIRA
(v6.2#6252)