Change wording on email address access
What does this MR do and why?
After !137322 (merged) was merged, I realized two things:
- SaaS users aren't going to care about versions very much. Saying, "In 16.7 and after, the feature behaves in X way" may just perpetuate the confusion: Isn't GitLab.com on 16.7 already? If not, which version is it on? When will the feature actually become available?
- The policy about promising future features prohibits definitive statements about when a feature will become available, which is what !137322 (merged) did.
This does mean we'll need to update the docs again once the feature is implemented, but I think this iteration is more intuitive and user-friendly until then.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by John Gaughan