### What we did - Updated amp.dev [release schedule](https://amp.dev/documentation/guides-and-tutorials/learn/spec/release-schedule/) page - Release tagging is live (`PR Use: In Stable / Beta / Experimental`) - Updated cherry-pick template with new release channel names - Added a way to build only the core runtime via `gulp build | dist | watch --core_runtime_only` - Clarified process for adding `amphtml` dependencies using `yarn` - Triaged backlog of infrastructure issues - Renaming `AMP_CANARY` cookie to `__Host-AMP_OPT_IN` ### What's next - Default minified build (`gulp dist`) will now add `AMP_CONFIG` to runtime files - Performance tests as part of CI / release workflow - Make LTS and nightly channel widely available - Take steps to reduce CI flakiness (sauce labs, percy)
What we did
PR Use: In Stable / Beta / Experimental)gulp build | dist | watch --core_runtime_onlyamphtmldependencies usingyarnAMP_CANARYcookie to__Host-AMP_OPT_INWhat's next
gulp dist) will now addAMP_CONFIGto runtime files