Release model under new subscription licensing?

Hi all,

There's a lot of internet drama about the new pricing right now, but I'm interested in whether the release model is expected to change since that will affect how plugins are developed. Is the plan to move to a rolling update model, like browsers have, or maintain a major version scheme? What will the implications be for plugin development and API versioning?

Similarly, for paid plugins are there any plans to allow third party plugins to piggyback on the licensing scheme? If development switches to a rolling update model that will pretty much force all plugins to use a subscription model as well since the underlying platform will be continuously upgraded. For locked down environments without outbound HTTP access it will be a pain to have to write a license server, and a pain for clients to have to install and maintain two.

Cheers,
Colin

3 comments
Comment actions Permalink

We don't have anything specific to announce at this moment. We've discussed the possibility of switching to a rolling update model, but if it will happen, it won't be soon, and we'll give plugin developers a heads-up in advance.

As for using our license server for third-party plugins, we aren't ready to offer it at this time, but it's also possible in the future.

0
Comment actions Permalink

So it looks like with the announcement of the v16 EAP that you're moving to more of a rolling update model? Is the idea that v16.x will be released in 2016 and so forth? What are the implications for API stability across v16.x releases? There was often significant API breakage from the major releases to the x.1 point releases (e.g. multiple cursors in v14.1).

0
Comment actions Permalink

No, not really. The current plan is to have three 4-month releases instead of one 4-month release and one 8-month release, basically.

0

Please sign in to leave a comment.