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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cleanup the amp-story-hold-to-pause experiment. #19332

Merged

Conversation

gmajoulet
Copy link
Contributor

Cleanup the amp-story-hold-to-pause experiment.

#18714 #18715

Copy link
Contributor

@newmuis newmuis left a comment

Choose a reason for hiding this comment

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

Is it safe for code and config to be in the same PR? My assumption was that the prod-config.json would hit prod in the next release, whereas the code would hit canary in the next release and prod in the release after. That would effectively unlaunch the feature for a week, if true.

/cc @choumx or @rsimha do you know?

@rsimha
Copy link
Contributor

rsimha commented Nov 15, 2018

Not safe. The PR check should have failed.

@gmajoulet
Copy link
Contributor Author

Thanks for catching this! Good news: PR check did fail :)

@gmajoulet gmajoulet force-pushed the clean_hold_to_pause_experiment branch from a5e06b6 to 9df17e8 Compare November 15, 2018 21:11
@gmajoulet
Copy link
Contributor Author

PTAL

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

6 participants