[asterisk-bugs] [JIRA] (ASTERISK-19818) Rework Asterisk Test Suite version parsing

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-19818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan closed ASTERISK-19818.
----------------------------------

    Resolution: Fixed

Fixed (for as much as version parsing is ever "fixed") quite awhile ago.
                
> Rework Asterisk Test Suite version parsing
> ------------------------------------------
>
>                 Key: ASTERISK-19818
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19818
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Tests/testsuite
>            Reporter: Matt Jordan
>
> The version parsing in the Asterisk Test Suite has had a lot of things bolted onto it, and has become unwieldy.  It is at this point in need of an overhaul such that it can support the various Asterisk branches and versions effectively.  An ideal solution would be able to parse and understand (at a minimum):
> 1) Asterisk branches (1.8, 10, 11, etc.)
> 2) Asterisk tags (1.8.3, 1.8.11.1, 10.3.1)
> 3) Asterisk RCs (1.8.11.0-rc1, 10.2.0-rc2)
> 4) Asterisk betas (11.0.0-beta1, 11.0.0-beta2)
> 5) Certified Asterisk branches (cert-1.8.11)
> 6) Certified Asterisk tags (1.8.11-cert1, 1.8.6-cert2)
> 7) Digium phone branches (10-digiumphones, 11-digiumphones)
> 8) Trunk
> 9) Team branches (or at least, not break on a version it doesn't understand and place it in some default category accordingly)
> Note that since 1.4 and 1.6.2 are EOL, we do not have to add logic for those versions.
> By "understand" the above versions, the class should be able to determine, for any two versions A/B, whether or not version A occurred before version B, after version B, or are the same version, for all the schemes listed above.
> As a first step, this task should be to document all of the version schemes supported by Asterisk, and their relative placement with relation to each other.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira