From 9a9885aa73ecab063dca5035740f409f9cbca6d4 Mon Sep 17 00:00:00 2001
From: Mikhail Timofeev <48208649+miketimofeev@users.noreply.github.com>
Date: Tue, 17 Aug 2021 22:45:20 +0300
Subject: [PATCH] Change the message as macos11 is GA in GH (#3912)
---
README.md | 12 ++++++------
docs/macos-11-onboarding.md | 25 -------------------------
2 files changed, 6 insertions(+), 31 deletions(-)
delete mode 100644 docs/macos-11-onboarding.md
diff --git a/README.md b/README.md
index 6870746d6..5337a24c4 100644
--- a/README.md
+++ b/README.md
@@ -21,13 +21,13 @@ Ubuntu 16.04 has been deprecated and will be removed on September 20, 2021. Its
Existing workflows using `Ubuntu 16.04` should migrate to `Ubuntu 20.04` or `Ubuntu 18.04`
```
-> The macOS 11 virtual environment is currently in preview and is automatically available to the existing Enterprise plan customers who used macOS hosted runners at least once between May, 1 - June, 1. New Enterprise plan customers, or customers on other plans, should fill the form to request access to macOS 11 virtual environment. Please view our [Big Sur guide](./docs/macos-11-onboarding.md) for more details.
+> The macOS 11 virtual environment is currently available only on GitHub Actions. Azure DevOps users can track the macOS 11 onboarding progress in [this issue](https://github.com/actions/virtual-environments/issues/2072).
The `macos-latest` YAML workflow label still uses the macOS 10.15 virtual environment.
***What images are available for GitHub Actions and Azure DevOps?***
-The availability of images for GitHub Actions and Azure DevOps is different. See documentation for more details:
-- [GitHub Actions](https://docs.github.com/en/free-pro-team@latest/actions/reference/specifications-for-github-hosted-runners#supported-runners-and-hardware-resources)
-- [Azure DevOps](https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software)
+The availability of images for GitHub Actions and Azure DevOps is different. See documentation for more details:
+- [GitHub Actions](https://docs.github.com/en/free-pro-team@latest/actions/reference/specifications-for-github-hosted-runners#supported-runners-and-hardware-resources)
+- [Azure DevOps](https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml#software)
***What image version is used in my build?*** Usually, image deployment takes 3-4 days, and documentation in the `main` branch is only updated when deployment is finished. To find out which image version and what software versions are used in a specific build, see `Set up job` (GitHub Actions) or `Initialize job` (Azure DevOps) step log.
@@ -45,9 +45,9 @@ we pin the tool to specific version(s).
*Following Along / Change Notifications*
-* **High Impact Changes** (ex. breaking changes, new or deprecated environments) will be posted to the GitHub Changelog on our [blog](https://github.blog/changelog/) and on [twitter](https://twitter.com/GHchangelog).
+* **High Impact Changes** (ex. breaking changes, new or deprecated environments) will be posted to the GitHub Changelog on our [blog](https://github.blog/changelog/) and on [twitter](https://twitter.com/GHchangelog).
* **Low Impact Changes** will be pinned in this repository and marked with the [Announcement](https://github.com/actions/virtual-environments/labels/Announcement) label.
-* **Regular Weekly Rhythm** can be followed by watching [Releases](https://github.com/actions/virtual-environments/releases). Pre-release is created when deployment is started. As soon as deployment is finished, it is converted to release.
+* **Regular Weekly Rhythm** can be followed by watching [Releases](https://github.com/actions/virtual-environments/releases). Pre-release is created when deployment is started. As soon as deployment is finished, it is converted to release.
You can also track upcoming changes using the [awaiting-deployment](https://github.com/actions/virtual-environments/labels/awaiting-deployment) label.
[ubuntu-20.04]: https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-README.md
diff --git a/docs/macos-11-onboarding.md b/docs/macos-11-onboarding.md
deleted file mode 100644
index f4e11a81c..000000000
--- a/docs/macos-11-onboarding.md
+++ /dev/null
@@ -1,25 +0,0 @@
-# macOS 11 (Big Sur) onboarding guide
-
-macOS 11 pools were opened to existing customers only, and we are working on making them ready for production use, rebalancing capacity, and analyzing possible load.
-
-Meanwhile, we'd like to start including customers to private preview on demand.
-
-> Big Sur will automatically become available to existing Enterprise customers. New enterprises and customers on other plans, please go through the sign up process described below.
-
-## Sign up process
-
-If you need to build and test your project with macOS 11, please, fill out the [form](https://forms.office.com/r/Pn0a7NqBXg).
-
-We will review the incoming requests periodically and open macOS 11 pool for some amount of them. These are the aspects we consider when processing requests:
-- _Pool capacity_. New onboardings are only possible if current performance won't degrade for existing customers.
-- _Billing plan_. New Enterprise or Teams customers will be given a priority in joining macOS 11.
-- _Necessity of macOS 11_. We can currently afford to add only those projects that really depend on the latest macOS version and its features.
-
-## Usage
-
-macOS 11 image label was changed to `macos-11` to avoid confusion with the minor version. We always update images to the latest available OS version. Use the following code snippet to run your builds on macOS Big Sur:
-```
-jobs:
- build:
- runs-on: macos-11
-```