In order to bring this topic to conclusion I think we'll move forward with the following versioning model for AMI and ARI since it seems to have garnered the most votes:
MAJOR.MINOR.PATCH Where the following definitions apply: MAJOR - changes when a new major version of Asterisk is released MINOR - changes when an incompatible API modification is made PATCH - changes when backwards compatible updates are made (new additions or bug fixes) This is basically option number 2 that was outlined in the "ARI versioning in 13 and 14" thread [1]. I've created a page [2] on the Asterisk wiki for ARI and updated an existing page for AMI [3] that essentially states the above for each. Thanks to all for your input and suggestions! [1] http://lists.digium.com/pipermail/asterisk-dev/2016-November/075964.html [2] https://wiki.asterisk.org/wiki/display/AST/ARI+Versioning [3] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Manager+Interface+%28AMI%29+Changes Kevin Harwell Digium, Inc. | Software Developer 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
