Timeline for notices

As part of our change policy, we've also established a timeline for how we classify changes and when they will take effect.

Change Category	Description	Time until deployment
Normal Changes	These are “business as usual” changes which are expected to make up the majority of the changes. There is no impact on partner integration. No action required on partner integration of the Service	No notification
Major Changes	There are either breaking changes that impact partner integration of the service (e.g. modification of a web service response body), or modifications of a business critical service. There is an action to be carried out on partner integration of the service. The change will be automatically released for production on the planned release date. In the meantime, the partner will be able to test and integrate the change (refer to the testing and integration of upcoming released)	Up to six months for Business Critical change
Emergency Changes	While all changes that may be necessary should be anticipated and planned, there will be times when business requirements will require changes to be made in an emergency. Withings will use commercially reasonable efforts to solve any issue that impacts internal or external “live” systems and requires implementation in order to resolve (or prevent) a current high priority incident or problem.	Up to two weeks