[pull] master from gravitational:master

.eslintignore

@@ -1,2 +1,7 @@
 **/*_pb.*
 .eslintrc.js
+
+# Ignore WASM generated files:
+web/packages/teleport/src/ironrdp/pkg
+
+web/packages/teleterm/build

.gitattributes

@@ -6,3 +6,6 @@ docs/theme/js/theme.js linguist-vendored=false
 # https://github.com/github/linguist/blob/v7.23.0/lib/linguist/generated.rb#L349-L358
 *_pb.js linguist-generated
 *_pb.d.ts linguist-generated
+*_pb.ts linguist-generated
+*_pb.grpc-*.ts linguist-generated
+*_pb.client.ts linguist-generated

.github/CODEOWNERS

@@ -1,3 +1,4 @@
 # Merge rules are governed by logic in the Workflow Bot. Protect the
 # .github/workflows directory (and the merge logic) using CODEOWNERS.
-/.github/workflows/ @klizhentas @russjones @r0mant @zmb3
+/.github/workflows/ @klizhentas @russjones @r0mant @zmb3 @fheinecke @camscale @tcsc @rosstimothy @codingllama
+/build.assets/tooling/cmd/difftest/ @klizhentas @russjones @r0mant @zmb3

.github/ISSUE_TEMPLATE/documentation.md

@@ -4,11 +4,17 @@ about: Report errors or suggest improvements to Teleport's documentation.
 labels: documentation
 ---
 ## Applies To
+
 <!-- List the URL(s) for existing docs this issue relates to. If this is a proposal for a new doc, you can suggest a path and title here. -->
 
 ## Details
-Describe the documentation improvements you wish to see.
+
+<!-- Describe the documentation improvements you wish to see. -->
+
+## How will we know this is resolved?
+
+<!-- Briefly describe a test we can carry out. Scope this as narrowly as possible. -->
 
 ## Related Issues
 
-<!-- If an existing issue relates to this one, please include it here for reference. -->
+<!-- Please make an effort to find related issues on GitHub and list them here. This makes a big difference in how we prioritize and schedule work. -->

.github/ISSUE_TEMPLATE/test-plan-docs.md

@@ -0,0 +1,88 @@
+---
+name: Documentation Test Plan
+about: Manual test plan for Teleport major releases
+title: "Teleport X Docs Test Plan"
+labels: testplan
+---
+
+Perform the following checks on the Teleport documentation whenever we release a
+new major version of Teleport:
+
+## Is the docs site configuration accurate?
+
+- [ ] Verify the latest version in `gravitational/docs/config.json`
+
+- [ ] Verify that `gravitational/docs/.gitmodules` contains the latest release
+
+- [ ] Ensure that submodule directories in `gravitational/docs` correspond to
+    those in `.gitmodules`.
+
+    Remove the directory of the EOL release and create one for the next release
+    using a command similar to the following:
+
+    ```bash
+    git submodule add https://github.com/gravitational/teleport content/<VERSION>.x
+    ```
+
+## Is the docs site up to date with the new release?
+
+- [ ] Verify that Teleport version variables are correct and reflect the upcoming
+  release. Check `docs/config.json` for this.
+
+- [ ] Remove version warnings in the docs that mention a version we no longer
+  support _except_ for the last EOL version. E.g., if we no longer support
+  version 10, remove messages saying "You need at least version n to use this
+  feature" for all versions before 10, but keep warnings for version 10.
+
+- [ ] Verify that all necessary documentation for the release was backported to
+  the release branch:
+  - [ ] Diff between master and release branch and make sure there are no missed
+    PRs
+  - [ ] Ensure that the release branch's documentation content reflects all
+    changes introduced by the release. If not, plan to update the docs ASAP and
+    notify all relevant teams of the delay (e.g., Developer Relations).
+
+- [ ] Verify that the [changelog](../../CHANGELOG.md) is up to date and complete
+  for the default docs version. If one release branch has a more complete
+  changelog than others, copy that `CHANGELOG.md` to our other support release
+  branches, e.g.,:
+
+  ```bash
+  $ git checkout origin/branch/v<release_version> -- CHANGELOG.md
+  ```
+
+- [ ] Verify the supported versions table in the FAQ
+  (https://goteleport.com/docs/faq/#supported-versions)
+
+- [ ] Verify that the [Upcoming Releases
+  Page](../../docs/pages/upcoming-releases.mdx) only exists for the major
+  version of Teleport we are releasing. Ensure that this page contains the
+  latest information:
+
+  ```bash
+  $ git checkout origin/branch/v<last_version> -- docs/pages/upcoming-releases.mdx
+  ```
+
+## Verify the accuracy of critical docs pages
+
+Follow the docs guides below and verify their accuracy. To do so, open the
+version of the docs site that corresponds to the major release we're testing
+for. For example, for Teleport 12 release use `branch/v12` branch and make sure
+to select "Version 12.0" in the documentation version switcher.
+
+### Installation
+
+- [ ] General [installation page](../../docs/pages/installation.mdx): ensure that
+  installation methods support the new release candidate.
+- [ ] Enterprise Cloud [downloads
+  page](../../docs/pages/choose-an-edition/teleport-cloud/downloads.mdx): ensure that
+  the release cnadidate is available at the repositories we link to.
+
+### Getting started
+
+- [ ] [Teleport Community Edition](../../docs/pages/index.mdx)
+- [ ] [Teleport Enterprise (Cloud)](../../docs/pages/choose-an-edition/teleport-cloud/get-started.mdx).
+- [ ] [Teleport Enterprise (Self-Hosted) with
+  Helm](../../docs/pages/deploy-a-cluster/helm-deployments/kubernetes-cluster.mdx)
+- [ ] [Teleport Enterprise (Self-Hosted) with
+  Terraform](../../docs/pages/deploy-a-cluster/deployments/aws-ha-autoscale-cluster-terraform.mdx)