Lifecycle

From APIDesign

Revision as of 09:01, 4 April 2018 (edit) JaroslavTulach (Talk | contribs) (New page: When designing an API of your framework you need to realize that you no longer control all the code on top of your project. In case you need to do a breaking, incompatible change, it i...) ← Previous diff

Current revision (09:01, 4 April 2018) (edit) (undo) JaroslavTulach (Talk | contribs) (New page: When designing an API of your framework you need to realize that you no longer control all the code on top of your project. In case you need to do a breaking, incompatible change, it i...)

---

Current revision

When designing an API of your framework you need to realize that you no longer control all the code on top of your project. In case you need to do a breaking, incompatible change, it is impossible to do it at once without having very negative effect on all the downstream projects. See ContinuousIntegration post for details. Instead one needs to adopt some for of an API lifecycle.

TBD