wg-infra Status Update 2020-02-03

[rsimha]

What we did

• Updated amp.dev 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)

[rcebulko]

Also release automation for most of the AMP GitHub apps

[alanorozco]

Is --core_runtime_only different than doing --extensions=amp-img?

[rsimha]

Is --core_runtime_only different than doing --extensions=amp-img?

Yes, it only builds amp.js.

[dreamofabear]

Any high-level plans for performance tests that can be shared yet? E.g. which metrics and how to manage data noise.

@rcebulko Curious what release automation for our GH apps is. A bit of an overloaded term. 😄

[rsimha]

Any high-level plans for performance tests that can be shared yet? E.g. which metrics and how to manage data noise.

@estherkim is meeting with folks from @ampproject/wg-performance this week. We should have more on this in the next update.

[rcebulko]

@choumx See ampproject/amp-github-apps#664

TL;DR - Previously only the author of each app (owners, bundle-size, test-status, pr-deploy, etc) could deploy an update in most cases, because it relied on manually deploying to GCloud with a .env with secrets and configs that couldn't be checked in and were rarely shared efficiently. Now any of us can push a tag and deploy an app using encrypted secrets and google cloud build.