ApacheCon EU 2016

Backwards compatibility in a distributed, scalable environment has two major components: interface compatibility, and persistence compatibility. Components in this environment can be integrated in two manners: statically and dynamically. Changes to any given component can be backwards compatible, or backwards incompatible. But in all these cases, your customer wants to be able to achieve 100% uptime. These variables, and the distributed nature of open-source development present interesting problems for a projectÛªs release cycle.



Myrle Krantz will propose a general set of rules for achieving a regular release cycle within this environment. First she will explain in detail the various kinds of backwards compatibility problems, and how they interact with the ways in which code is deployed.