API release stages¶
Last updated on: Tuesday 8 March 2022
This article describes the typical release cycles for the Marigold Engage features & APIs as part of our product roadmap & strategy.
The API release stages Policy is part of our API lifecycle management and sunsetting/deprecation approach, for more information read up on our API Lifecycle & Deprecation Policy. We may make periodic updates to this Policy, at which time we will notify those who have agreements with us.
API release stages¶
New Marigold Engage API features follow a release cycle. The release cycle is broken into three stages:
- Beta (BETA)
- Early Access (EA)
- General Availability (GA)
Beta (BETA) releases¶
The beta release access is to provide customers the option to play with new experimental features, gather feedback to validate new functionality & discover usage patterns and additional needs.
Features in "Beta" are managed and supported by the Product Team and the Customer Success Managers, to provide a set of use cases for validation. Minimal documentation, API endpoint and configuration information are usually provided to customers for API-related Beta releases.
Beta features are tagged with the "BETA" label:
BETA
Selligent selects a small number of customers for early testing of features in a "Beta" release. Customers participating in a "Beta" program agree to provide feedback that is required for maturing the feature. The timeline for addressing specific areas of feedback (including bugs) is determined by Marigold Engage and the requirements for that feature.
Beta releases involve regular contact with Marigold Engage , which may include conference calls that cover specific use cases, implementation guidance, and gathering of feedback. Betas are announced to customers through the Marigold Engage Customer Success Managers.
Early Access (EA) releases¶
An "early access" release is to provide customers early access to an upcoming feature, which allows Marigold Engage to gather feedback to fine-tune the feature & value proposition with the goal to streamline it for General Availability
A feature in an "Early Access" (EA) stage offers a new or enhanced functionality made available for customers that opt-in to use the feature in Production and non-Production environments. Features in "Early Access" are managed and supported by the Product Team and the Customer Success Managers, for onboarding & implementation support
In the developer portal, upcoming features are tagged with the "EARLY ACCESS" label:
EARLY ACCESS
Early Access programs are announced to customers through the Marigold Engage Customer Success Managers. In collaboration and after approval, customers are granted access to the new feature.
Customers participating in an "Early Access" program agree to provide feedback that is required to streamline the feature. The feedback is gathered in regular contacts with Marigold Engage , which may include conference calls that cover specific use cases, implementation guidance. Any bug fixes or improvements are managed and fixed with the same timeline and processes as those in General Availability.
General Availability (GA) releases¶
Features in the "General Availability" (GA) stage are accessible within the Marigold Engage platform and APIs, ready to be used by the customers. The features are fully supported, and issues are addressed according to your Customer Agreement with Marigold Engage .
Documentation for features in GA release are not marked or explicitly tagged with:
LIVE
or
GA
Preview (PREVIEW)¶
The preview tag is to indicate upcoming features that are in active development.
Features in "PREVIEW" are considered "work-in-progress" and subject to change. The goal of exposing the PREVIEW documentation is to share the specifications of the future API & Event references.
Preview features are tagged with the "PREVIEW" label:
PREVIEW