|[cdt-dev] RE: [cdt-debug-dev] List of Plan items|
Breaking API is never a good thing. Really the focus of the 4.0 release as far as APIs go is to identify the APIs that we want to freeze going forward. Some of the less mature APIs will likely undergo change so that we freeze them in at a higher quality level. The CDI is pretty mature in it’s current state so I don’t anticipate much change. But as Mikhail mentions, if the community approves API changes, they can happen.
I will be starting this week to put together guidelines like this for us to vote on and follow. If anyone has any input on the process that we should follow for API management, please let me know and I’ll try and integrate it.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Back to the top