Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃摉 Add instructions to start a RTV Experiment #29008

Merged
merged 5 commits into from Jun 26, 2020

Conversation

zhouyx
Copy link
Contributor

@zhouyx zhouyx commented Jun 23, 2020

The doc should help whoever wants to create an experiment. The inabox part will be documented separately and internally.

build-system/global-configs/README.md Outdated Show resolved Hide resolved

We understand that experimenting a new feature or change on the client side is not always practial. For example, if you rewrite a big chunk of the code base, or include add extra step to optimize code in the transpiling process, you want to run the experiment at the server level, where different bianries will be returned.

This doc explains how to create a server side experiment.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe add one sentence how it is different from the other "client side diverted experiments"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added


Once the experimental bianries are shipped, once can access those with different RTV prefix.

For Experiment with `environment = AMP`. The Beta version that has prefix (03) will be used as control build for all experiments.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The control build (which is binary equivalent to stable) is used, so it's 02

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do want to use RC (03) as the control group because RC and the experimental build are promoted at the same time, while control build(02) is promoted a week after.

I renamed the control build to control group, hope that clarify.

@zhouyx zhouyx merged commit 681c218 into ampproject:master Jun 26, 2020
@zhouyx zhouyx deleted the rtv-exp-doc branch June 26, 2020 22:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants