To me version numbers are just a label. It's more about exposure, communication and documentation.
If we employ the standard deprecation techniques for the native platforms enough ahead of time, blog about upcoming breaking changes, provide tutorials and documentation for how to migrate, I am fine with it. On 6/18/12 3:25 PM, "Brian LeRoux" <[email protected]> wrote: >We don't really have one tho I think we loosely follow Semantic >Versioning. In Android-land we recently merged in CordovaView which >has an API change which will break many plugins. In Semantic >Versioning reality we are completely justified to kill an API in 2.x >which would make a great deal of pain for plugin authors at that time. >Major release, break all the things, seems bad. > >Anyhow, I'm thinking we look to create a policy that is time based. We >make a change, its got 6 months of deprecation notices, and then its >gone, regardless of version number. > >Thoughts?
