This issue is for tracking progress on updating angular.io deployments to match our new versioning/branching process.

Planning

1. What Firebase projects/sites need to be created?

   • angular-io > v2-angular-io-site
   • angular-io > v4-angular-io-site
   • angular-io > v5-angular-io-site
   • angular-io > v6-angular-io-site
   • angular-io > v7-angular-io-site
   • angular-io > v8-angular-io-site
   • angular-io > v9-angular-io-site
   • angular-io > v10-angular-io-site
   • angular-io > v11-angular-io-site
   • angular-io > rc-angular-io-site
   • angular-io > next-angular-io-site
   
   

   Note 1: The angular-io Firebase project will be the canonical one, so all sites should be created there.

   Note 2: There is Firebase project named v10-angular-io and therefore we are not allowed to have v10-angular-io site. For consistency, all site names should have a -site suffix (i.e. <xyz>-angular-io-site).

   
   

2. What Firebase projects/sites will be obsolete (and can be deleted at the very end)?

   • v2-angular-io
   • v4-angular-io
   • v5-angular-io
   • v6-angular-io
   • v7-angular-io
   • v8-angular-io
   • aio-staging (including aio-staging > v9-angular-io)
   
   

3. What DNS/Firebase redirects do we need?

   • v2.angular.io --s--> angular-io > v2-angular-io-site (previously v2-angular-io)
   • v4.angular.io --s--> angular-io > v4-angular-io-site (previously v4-angular-io)
   • v5.angular.io --s--> angular-io > v5-angular-io-site (previously v5-angular-io)
   • v6.angular.io --s--> angular-io > v6-angular-io-site (previously v6-angular-io)
   • v7.angular.io --s--> angular-io > v7-angular-io-site (previously v7-angular-io)
   • v8.angular.io --s--> angular-io > v8-angular-io-site (previously v8-angular-io)
   • v9.angular.io --s--> angular-io > v9-angular-io-site (previously aio-staging > v9-angular-io)
   • v10.angular.io --r--> angular.io (might be already configured on DNS)
   • www.angular.io --r--> angular.io --s--> angular-io > v10-angular-io-site (previously angular-io)
   • v11.angular.io --r--> rc.angular.io (previously next.angular.io)
   • rc.angular.io --s--> angular-io > rc-angular-io-site (previously -)
   • next.angular.io --s--> angular-io > next-angular-io-site (previously aio-staging)
   
   

   <sub>* --s-->: Must be configured in Firebase to serve the specified project.
   * --r-->: Must be configured in DNS (and possibly in Firebase) to redirect to the specified domain.</sub>

   
   

4. What existing projects/sites need to be cloned (and where to)?

   • v2-angular-io --> angular-io > v2-angular-io-site
   • v4-angular-io --> angular-io > v4-angular-io-site
   • v5-angular-io --> angular-io > v5-angular-io-site
   • v6-angular-io --> angular-io > v6-angular-io-site
   • v7-angular-io --> angular-io > v7-angular-io-site
   • (v8-angular-io --> angular-io > v8-angular-io-site - will be deployed when we update the merge scripts)
   • (aio-staging > v9-angular-io --> angular-io > v9-angular-io-site - will be deployed when we update the merge scripts)
   • (angular-io --> angular-io > v10-angular-io-site - will be deployed when we update the merge scripts)
   • (aio-staging --> angular-io > rc-angular-io-site - will be deployed when we update the merge scripts)
   • (aio-staging --> angular-io > next-angular-io-site - will be deployed when we update the merge scripts)
   
   

5. What branches need to be updated for future deployements (all active LTS and releasable branches)?

   • 8.2.x (for https://v8.angular.io/) | PR: [8.2.x] build(docs-infra): update angular.io deployments to match new versioning/branching process #39479
   • 9.1.x (for https://v9.angular.io/) | PR: [9.1.x] build(docs-infra): update angular.io deployments to match new versioning/branching process #39478
   • 10.1.x (for https://angular.io/) | PR: build(docs-infra): update angular.io deployments to match new versioning/branching process #39470
   • 11.0.x (for https://rc.angular.io/) | PR: build(docs-infra): update angular.io deployments to match new versioning/branching process #39470
   • master (for https://next.angular.io/) | PR: build(docs-infra): update angular.io deployments to match new versioning/branching process #39470

Execution

• 1. Create the necessary projects/sites.
• 2. Manually re-upload latest minor versions of all (non-releasable) majors to sites. (Version cloning)
  • I cloned the version (using firebase hosting:clone), but it seems to only clone the content and not the hosting config. Looking for another way to address that (hopefully without having to build each version from the sources 😱).
  • I asked about it in the Firebase Community Slack and @bkendall (from the Firebase team) offered to look into it.
    • UPDATE: It is indeed a bug in Firebase. They'll get it fixed.
  • In the meantime, (after trying a couple of things to fix it) I ended up building each version locally a manually deploying. I tested the deployments as best as I could and they seem to be correct™️.
• 3. Create PRs for all necessary branches to deploy to new sites (instead of old projects).
  • PRs: build(docs-infra): update angular.io deployments to match new versioning/branching process #39470, [9.1.x] build(docs-infra): update angular.io deployments to match new versioning/branching process #39478, [8.2.x] build(docs-infra): update angular.io deployments to match new versioning/branching process #39479
• 4. Once merged, verify sites work (both for manually cloned versions and merged PRs).
• 5. Update DNS/Firebase redirects.
• 6. Verify angular.io sub-domains work and point to sites (by looking at the deployed SHA in the footer).
• 7. Delete unnecessary projects/sites.