> The correct way to notify developers can’t just be to send out an > email after merging changes to Common and assume they implement > required changes without any planning. This just does not work > really well. We can decide not to accept intrusive changes in IVI > for a while but unfortunately dependencies lead to growing delta > quite fast. Of course I might have just missed the memo but in case > not I really think next time CAPI used by verticals gets changed we > must handle the changes in a more controlled manner.____
Indeed we have a procedure for API changes, though it seems to have fallen into disuse in recent months. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
