[prev in list] [next in list] [prev in thread] [next in thread] 

List:       asterisk-dev
Subject:    Re: [asterisk-dev] AMI/ARI versioning
From:       Kevin Harwell <kharwell () digium ! com>
Date:       2017-04-05 19:31:23
Message-ID: CAM-yhnnw6G_vBwn8SGgSQKk3GdVTPxVD6KJP-e-5pi89ZK7xUQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>In order to \
bring this topic to conclusion I think we&#39;ll move forward with the following \
versioning model for AMI and ARI since it seems to have garnered the most \
votes:</div><div><br></div><div>MAJOR.MINOR.PATCH</div><div><br></div><div>Where the \
following definitions apply:</div><div><br></div><div>MAJOR - changes when a new \
major version of Asterisk is released</div><div>MINOR - changes when an incompatible \
API modification is made</div><div>PATCH -  changes when backwards compatible updates \
are made (new additions or bug fixes)</div><div><br></div><div>This is basically \
option number 2 that was outlined in the &quot;ARI versioning in 13 and 14&quot; \
thread [1].</div><div><br></div><div>I&#39;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.</div><div><br></div><div>Thanks to all for your input and \
suggestions!<br></div><div><br></div><div>[1] <a \
href="http://lists.digium.com/pipermail/asterisk-dev/2016-November/075964.html">http:/ \
/lists.digium.com/pipermail/asterisk-dev/2016-November/075964.html</a><br></div><div>[2] \
<a href="https://wiki.asterisk.org/wiki/display/AST/ARI+Versioning">https://wiki.asterisk.org/wiki/display/AST/ARI+Versioning</a></div><div>[3] \
<a href="https://wiki.asterisk.org/wiki/display/AST/Asterisk+Manager+Interface+%28AMI% \
29+Changes">https://wiki.asterisk.org/wiki/display/AST/Asterisk+Manager+Interface+%28AMI%29+Changes</a></div><div><br></div></div><div \
class="gmail_signature"><div dir="ltr"><pre style="padding:2px;border:1px solid \
rgb(114,99,77);background-color:rgb(238,238,238);color:rgb(0,0,0);overflow:auto">Kevin \
Harwell Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> \
&amp; <a href="http://asterisk.org" \
target="_blank">http://asterisk.org</a></pre></div></div> </div></div>



-- 
_____________________________________________________________________
-- 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

[prev in list] [next in list] [prev in thread] [next in thread]