Feature release stages

A 'Closed Beta' is a private testing phase where a limited group of invited users can access the new feature in a Stage environment. This stage is typically by invitation only and not publicly advertised.

Characteristics:

• Limited Access: Only selected users or specific groups (for example, chosen partners and customers) are allowed to participate.
• Confidentiality: Participants may be required to sign non-disclosure agreements (NDAs) to ensure the feature remains confidential until it is ready for broader release.
• Early Stage: Features are still in development and may contain significant bugs or missing functionality. These features do not guarantee backward compatibility. They may change in future releases, depending on the feedback. They may be removed anytime from existing and future releases without prior announcement.
• Documentation: Resources are provided by the product management team who work directly with the participants to help them get familiar with the feature. These features are not announced in the product What's New.
• Private Feedback: Participants provide feedback about the design, usability, and other potential improvements, confirming that the desired outcome is achieved. This feedback is often collected through a private community or group where the participants collaborate as group members with the other participants and the product managers.
• Support: No support is provided in this phase. Functional queries are handled by the product management team who work directly with the participants.

A 'Beta' or 'Open Beta' is a more mature testing phase where the feature is made available to a wider audience for testing in a Stage environment, but is still not considered fully ready for general release.

Characteristics:

• Broader Access: Generally open to the public or a larger subset of the user base who opt-in or register to participate. The feature is available in UAT or User Acceptance Testing (also known as Preview or Non-Prod). It is typically identified as Beta in both the product and documentation.
• Feedback and Testing: Users can report bugs and provide feedback through private communities or groups, contributing to the final development stages before the general release.
• Improved Stability: More stable than a Closed Beta, but still may have some bugs and issues that need resolution.
• Increased Awareness: Often used to generate interest and increase awareness before the official launch.
• Documentation: Limited documentation and resources are typically available to assist users with adoption and usage. The documentation categorically marks the feature as Beta and describes the associated limitations and conditions to set expectations with customers.
• Support: Limited technical and customer support is provided in this phase. The provider values feedback, and allows you to log support tickets, but does not guarantee timely fixes for any issues you encounter with these features.

The 'Early Adopter' (EA) phase involves releasing the feature to all users who are willing to use new technologies early in their lifecycle, often for strategic benefits or to gain a competitive advantage.

Characteristics:

• Targeted Release: Offered to all users or organizations in a Production environment on an opt-in basis. They can decide whether they want to activate the feature or not.
• Innovation Leaders: Early adopters are often seen as innovators within their respective industries or communities.
• Refinement Needed: Although more refined than Beta versions, the feature may not meet some complex use cases and may still undergo changes based on the feedback from this group.
• Documentation: Comprehensive documentation and resources are typically available to assist users with adoption and usage. The documentation categorically marks the feature as Early Adopter.
• Support: Same level of support as General Availability features and products.

'General Availability' (GA) signifies that the feature or product is fully tested, validated, and released to the entire user base.

Characteristics:

• Wide Release: Available to all users without restrictions on access.
• Stable and Reliable: Considered stable and reliable for production use with most major bugs and issues resolved.
• Marketing Push: Accompanied by significant marketing efforts to promote the feature to the general public.
• Documentation: Comprehensive documentation and resources are typically available to assist users with adoption and usage.
• Support: Comes with full technical and customer support from the provider.