Release Notes

"Release Notes" document each new and enhanced functionality in the Tulip product.

It exhaustively documents changes to:

• The Tulip product i.e. your-instance.tulip.co

Here's an explanation of each column below.

Unique ID: The ID provides a unique reference to the functionality that was merged into the product. It provides a reference to the tickets used internally for development.

Release: The specific release of Tulip where this was launched. I.E. r199

Release Notes: A brief description of the change.

Type of Change: Chosen from one of three options:

• Feature Enhancement: A new capability within an existing feature.

• New Feature: An entirely new feature with functionality independent of all existing features.

• Feature Deprecated: A feature that was removed and will no longer be supported.

• Beta: Use of Beta Features offered by Tulip is optional and is at your sole risk. Due to the unproven nature of Beta versions, they are provided “as is,” “as available,” and without warranty. This means that any warranties, indemnities and other obligations of Tulip under any terms of service or MSA do not apply to Beta Versions. Once this feature comes off Beta for full release, a new release note will communicate this and the Beta tag will be removed from the relevant Product Specification.

Implemented By: The Product Specs where the changes are reflected. In many cases, Product Specs will not be updated due to changes impacting small edge cases that are too specific and unique to document. This document is now ordered by Implemented By.

As an additional source of information see also release notes on our Announcements community page where more illustrative information is provided for each regular release. Follow the link and look for the regular release number that you’re interested in!