diff --git a/content/ui-patterns/feature-onboarding.mdx b/content/ui-patterns/feature-onboarding.mdx index 3b44fe869..f03b95673 100644 --- a/content/ui-patterns/feature-onboarding.mdx +++ b/content/ui-patterns/feature-onboarding.mdx @@ -365,9 +365,9 @@ Note: The `Technical preview` label may sometimes be used by the Next team for e ||Stage|Details| |--|--|--| -| ![private preview](https://github.com/user-attachments/assets/c509e399-0b44-4009-8fed-708042aa33b8) |**Private Preview**
(formerly Alpha, Private Beta, Staff) |- Not publicly announced
- Support handled by the product and engineering team (no SLAs) | -| ![public preview](https://github.com/user-attachments/assets/3f549ab1-3b1c-425d-b7c3-95c591bed4fc) |**Public Preview**
(formerly Limited Public Beta, Public Beta) |- Publicly announced
- Customers should not yet take production dependencies on the service (no SLAs)
- Support handled by the product and engineering teams. With VP Support approval, exceptions allow the Support team to handle tickets. | -| | **General Availability** |- Available to ALL GHEC Customers
- SLAs apply (where applicable, some products do not have SLAs)
- Support provided | +| ![private preview](https://github.com/user-attachments/assets/c509e399-0b44-4009-8fed-708042aa33b8) |**Private Preview**
(formerly Alpha, Private Beta, Staff) |- Not publicly announced
- Support handled by the product and engineering team (no SLAs) | +| ![public preview](https://github.com/user-attachments/assets/3f549ab1-3b1c-425d-b7c3-95c591bed4fc) |**Public Preview**
(formerly Limited Public Beta, Public Beta) |- Publicly announced
- Customers should not yet take production dependencies on the service (no SLAs)
- Support handled by the product and engineering teams. With VP Support approval, exceptions allow the Support team to handle tickets. | +| | **General Availability** |- Available to ALL GHEC Customers
- SLAs apply (where applicable, some products do not have SLAs)
- Support provided | We recommend gathering feedback through a discussion to enable seamless follow-up with the user. This discussion should specify the changes made, providing clarity to the user about what's new. In case of deprecating a feature, it's crucial to provide additional information through our documentation. Note that features that were never promoted beyond the `Private preview` lifecycle do not need to go through a deprecation lifecycle.