[Asterisk-Dev] When do we change manager version?

[Alexander Lopez]

 I would use a subversion 1.0.0 to 1.0.1 to reflect syntax changes to
existing functions.
Reserve version 1.0.0 to 1.1.0 when features are added, and push out
2.X.X as a new module.

> -----Original Message-----
> From: asterisk-dev-bounces at lists.digium.com 
> [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of 
> Olle E Johansson
> Sent: Thursday, January 05, 2006 1:47 PM
> To: Asterisk Developers Mailing List
> Subject: [Asterisk-Dev] When do we change manager version?
> 
> Russel and I have been discussing manager version numbers in 
> the bug tracker. There is a version number given when someone 
> logs in. It has, as I remember, never been changed.
> 
> Russel wants to change the syntax of a command. I agree with 
> the change, as my opinion is that we need to change *a lot* 
> of the manager syntax to clean up cases where one keyword is 
> used for many different things.
> 
> Russel thinks it enough to change the README and then change 
> syntax, alerting users of the change.
> 
> My opinion is that if we change an existing and implemented 
> action or event, we need to change the version number. A 
> small change - from 1.0 to 1.1. That way, clients have a way 
> to change its parsing to reflect the proper version.
> 
> At some point, we need to start manager 2.0, propably as a 
> separate optional module to keep backwards compatibility.
> 
> Anyway, do you think we can change syntax *without* changing 
> version number of manager or do you agree that we need to 
> change version numbers and document differences in a 
> README.managerversion?
> 
> /O
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> Asterisk-Dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev
>