[mpris] [RFC] MprisVersion method

[Ian Monroe]

On Fri, Mar 21, 2008 at 6:05 AM, Rafaël Carré <funman at videolan.org> wrote:
>  I propose:
>
>  API addition : revision change
>  API modification (signature change) : minor change
>
>  Wide acceptance/implementation : major change

I disagree. I think we should use Qt-like versioning, where they only
have a major change if it breaks ABI. Obviously we don't have ABI, but
we have something like it: anytime we change a signature that could
break current scripts it should be a major version increment. Having
major version increment based on just on "acceptance"... is useless.

So we should start out at 1.0.0. If someone adds a few methods, that
would like be 1.1.0. If we remove methods or change current methods,
it would be 2.0.0.

Anyways sorry for the silly mistake. :)

Ian