What is the name for framework-style development?

When developing targeting frameworks, I tend to follow principles to support backward-compatibly (within reason), to avoid breaking existing application code:

1. Don't change class names or namespaces.


2. Don't rename or remove properties or public fields.


3. If there is a significant churn in a class, create a new class and keep the old one but deprecate it.

The principles are not exactly as strict as developing services using service-oriented development, but close. Is there a specific name for this style of development?

Is there a reference with best-practices available for this?