SDAPI versioning and deprecation policy 2.0

This document describes the versioning and deprecation policy for the Demandware Script Debugger API (SDAPI). This policy is designed to

Version creation and deprecation

A new SDAPI version is created whenever Demandware:

Whenever Demandware creates a new OCAPI version, it also deprecates the former SDAPI version. This encourages customers and developers to:

Version lifecycle

Version State Support Description
Current Yes The newest version. Always develop new applications using the current version. Demandware ensures that the SDAPI version is supported for at least two years. During this period Demandware ensures the stability and backwards-compatibility of the version enclosed feature set.
Deprecated Yes Demandware deprecates an SDAPI version when a new version is published. Support, stability, and backwards-compatibility are ensured for up to two years after the publish date.
Obsolete No Deprecated versions become obsolete automatically two years after being published. Demandware deletes obsolete versions without further notice.

Notification process

Demandware notifies customers about new and deprecated versions on the XChange portal and in the Demandware Release Notes.

X Privacy Update: We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used. By continuing to use this site you are giving us your consent to do this. Privacy Policy.