API deprecation and decommission policy

This page focuses on what customers can expect from Jutro's commitment to non-breaking changes (NBCs).

Success criteria

Jutro Digital Platform (consuming Jutro directly) customers and customers depending on Jutro for their Digital reference applications experience zero-cost upgrades.

Jutro Digital Platform policy

Deprecation timeline

The timeline below explains what to expect when an API is deprecated. A deprecated item is one that is available but not recommended for use. When Guidewire implements a change and deprecate something, the change proceeds according to the following timeline:

Deprecated but full support

The changelog for the corresponding minor Jutro release discusses the deprecations. The documentation is updated to clearly indicate the deprecation, discouraging the usage of the deprecated functionality in favor of alternative ways. Deprecated functionality does not get any new features added, but it has the same full support as non-deprecated functionality such as bug triaging, bug fixing, and support through answering questions.

The use of the deprecated functionality will be discouraged. Guidewire will inform customers about the dependencies or use of the deprecated APIs through tools such as the console log, Jutro Web Apps, and email digest.

Deprecated but limited support

Documentation indicates that the functionality is considered a legacy functionality, Guidewire strongly recommends customers migrate away from it. Bug fixes are limited, the primary focus is security fixes. Only non-investigative questions about the functionality are being answered. To speed up problem resolution, users are recommended to perform their own investigation if something does not work in their particular environment.

Remaining unconditional support consists of security fixes and any regressions if accidentally introduced. When a new major version of Jutro is released, the functionality might be moved under a legacy space such as a specific directory or package. Usage of any legacy type of functionality might be blocked for new Jutro applications.

Decommissioned

When there is no usage of the legacy functionality in any of the customer apps, Guidewire can remove the legacy functionality entirely in a major release of Jutro Digital Platform. Typically it happens when customers have migrated away from that particular functionality. Customers can also opt-in to own a particular functionality by making it part of the their own application code, for example by moving a deprecated component into the application codebase. In this scenario Guidewire can support such transfer by providing codemods. Once the component has been transferred to the customer's codebase, Guidewire will no longer maintain or update the component.