Boie, Andrew P
I already got feedback from people developing either drivers or sample
I'm not advocating anything w.r.t. a policiy for changing APIs rightI think we shouldn't change our existing APIs at all. They should be treated as a contract. Someone who builds code against 1.0 should be able to do so against later versions until we make a conscious decision otherwise.
I think if we want to change something, we mark the old APIs with __attribute__((deprecated)) so that it's clear that the old API is going away at some point by generating a warning. But they should still be *usable*.
Then, in the fullness of time, remove the APIs that were previously deprecated. Whether that is Zephyr 1.5, 2.0, doesn't matter to me.
VxWorks), they did _not_ like the fact that even a small amount of ourWhat specifically changed that caused consternation?