Update the UI text for the experimental/beta feature
Description
From the discussion, we want to simplify the text in the popover and align the text with the documentation.
-
Experiment:
What's an Experimental feature?
An experimental feature is not yet production-ready, but is released for initial testing and feedback during development. Experimental features:- Might be unstable or cause data loss.
- Are not supported and might not be documented.
- Could be changed or removed at any time.
-
Beta:
What's a beta feature?
A Beta feature is not yet production-ready, but is ready for testing and unlikely to change significantly before it's released. Beta features:
- Have a low risk of data loss, but might still be unstable.
- Are supported on a commercially reasonable effort.
- Are complete or near completion.
Related to !3374 (merged)
Changes needed
-
Pajamas document (https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/blob/main/contents/usability/feature-management.md): !3710 (merged) -
Finalize addition to the Pajamas library (Figma) -
UI component (https://gitlab.com/gitlab-org/gitlab-ui/-/blob/main/src/components/experimental/experiment_badge/experiment_badge.vue): gitlab-org/gitlab-ui!4212 (merged) -
Shared code: gitlab-org/gitlab!153199 (merged)
Next steps
Switch to GlExperimentBadge as SSOT for Beta/Ex... (gitlab-org&13980)
Checklist
Make sure the following are completed before closing the issue:
-
Assign the correct component label to this issue. -
Create an MR with the additions or updates needed. -
When applicable, create an issue using the Figma update
issue template to update the component in Figma, and mark it as related to this one. Bring the issue to your team planning session for prioritization and scheduling. -
When applicable, create an MR in GitLab UI to update the component. If you do not have capacity or are unable to update the component directly, create a GitLab UI issue using the Component
issue template. Mark the new issue as related to this one. Bring the issue to your team planning session for prioritization and scheduling. Mark the issue as related to this one. -
When introducing a major or breaking change, communicate the changes within the Engineering Week in Review and UX Weekly meeting. -
🎉 Congrats, you made it! You can now close this issue.
Edited by Sunjung Park