Hi @bsavery,
I already replied on bf-committers here. Thanks for your input! Same goes for @testure, appreciated 
As I mentioned on the ML I hadn’t really given much thought to it, but I understand the burden the pace of breaking changes is tough to keep up with.
I’d like to see us do a better controlled approach to our API development, taking the add-on eco-system at large into account better.
As @testure I’d say that adding new API should be always possible, even between subsequent ‘minor’ releases, but a better scheduled (read: longer adjustment period) deprecation scheme along with improved warnings for add-on devs would in my opinion we should try to accomplish.
I hope we can discuss this further also during the upcoming dev meeting.
We’ll need some concrete proposal from the Python team that addresses your points as well as it can. It’d be nice if @ideasman42, @mont29, @BrendonMurphy, @jacqueslucke, @sybren et al to put their heads together and see if they could whip up something in the coming few weeks. Please?