Skip to content

Make deprecation trials more obvious on the feature details page #4765

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
past opened this issue Feb 7, 2025 · 1 comment
Open

Make deprecation trials more obvious on the feature details page #4765

past opened this issue Feb 7, 2025 · 1 comment

Comments

@past
Copy link
Collaborator

past commented Feb 7, 2025

A new feature can sometimes have both a deprecation trial and a regular trial. Creating a new OT stage currently doesn't distinguish between regular and deprecation trials until the point when the I2E has been approved and the author tries to request a trial. If we move the input field to the OT stage form we would be able to both distinguish reverse from regular OTs in the feature details (providing better naming guidance in help text too), and also simplify the OT creation form (ot_creation_request) by e.g. not showing the web counter field at all.

Image

In order to better distinguish regular and reverse OTs we could start by changing the stage label (Deprecation Trial/Origin Trial) and consider perhaps adding a "deprecation" chip before the OT stage name.

@past
Copy link
Collaborator Author

past commented Feb 7, 2025

Another argument in favor of automatic marking/badging the stage is that feature authors often don't provide a name for the stage (example) leaving readers confused about the feature being both shipping and in OT.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant