search for: immobl

Hi Juergen, Sean, I definitely agree with needing to write down the policy and definitely any policy should include a deprecation time :) Did you want to write up something and let us poke at it? A couple of thoughts outside of a deprecation policy: a) guarantee that the api itself won't go away, but could possibly be turned into a noop? (i.e. source compatibility) b) versioning? (Should

On 07/17/2015 02:05 PM, Rafael Espíndola wrote: >> c) One of the big things appears to be the push and pull for "A C API for >> all C++ entry points" along with "We don't want to get locked into >> immobility because we have a C API for all C++ entry points". Perhaps part >> of this might be defining an actual stable set of things along with an

Hi @ll, a few of us had recently a discussion about how to manage the C API and possible policies regarding addition, maintenance, deprecation, and removal of API. Even thought there is a strong agreement in the community that we shouldn't break released C API and should be backwards compatible, there doesn’t seem to be a developer policy that backs that up. This is something we should fix.