Merge branch 'jswain_whats_new_yaml_content' into 'master'

Whats New - drop content for 3 previous releases

See merge request gitlab-org/gitlab!38976

data/whats_new/202008180001_12_10.yml

+---
+- title: Create and view requirements in GitLab
+  body: The first step towards managing requirements from within GitLab is here! This initial release allows users to create and view requirements at a project level. As Requirements Management evolves in GitLab, stay tuned for support for traceability between all artifacts, creating a seamless workflow to visually demonstrate completeness and compliance.
+  stage: Plan
+  self-managed: true
+  gitlab-com: true
+  packages: ultimate, gold
+  url: https://docs.gitlab.com/ee/user/project/requirements/index.html
+  image_url:
+    published_at: 2020-04-22
+    release: 12.10
+- title: Retrieve CI/CD secrets from HashiCorp Vault
+  body: In this release, GitLab adds support for lightweight JSON Web Token (JWT) authentication to integrate with your existing HashiCorp Vault. Now, you can seamlessly provide secrets to CI/CD jobs by taking advantage of HashiCorp's JWT authentication method  rather than manually having to provide secrets as a variable in GitLab.
+  stage: Release
+  self-managed: true
+  gitlab-com: true
+  packages: All
+  url: https://docs.gitlab.com/ee/ci/examples/authenticating-with-hashicorp-vault/index.html
+  image_url: https://about.gitlab.com/images/12_10/jwt-vault-1.png
+  published_at: 2020-04-22
+  release: 12.10
+- title: Epic and Issue Health Tracking
+  body: To help users track projects and in-flight work GitLab now enables you to report on and quickly respond to the health of individual issues and epics by showing a red, amber, or green health status on your Epic Tree. Assign an issue a health status of On track (green), Needs attention (amber), or At risk (red) and see an aggregate report of health at the Epic level. Quickly view and analyze where a collection of work is at risk so you can open up the right discussions at the right time and keep work on track!
+  stage: Plan
+  self-managed: true
+  gitlab-com: true
+  packages: ultimate, gold
+  url: https://docs.gitlab.com/ee/user/project/issues/index.html#health-status-ultimate
+  image_url: https://about.gitlab.com/images/12_10/epic-health-status.png
+  published_at: 2020-04-22
+  release: 12.10
+- title: Import Issues from Jira to GitLab
+  body: Until now, the only way to get Jira issues into GitLab was manually, with our CSV importer, or by hand-rolling your own migration utility. GitLab 12.10 includes an MVC to automatically import your Jira issues into GitLab. This is the first of many planned enhancements to make transitioning from Jira to GitLab as frictionless as possible.
+  stage: Plan
+  self-managed: true
+  gitlab-com: true
+  packages: All
+  url: https://docs.gitlab.com/ee/user/project/import/jira.html
+  image_url: https://about.gitlab.com/images/12_10/jira-importer.png
+  published_at: 2020-04-22
+  release: 12.10
+- title: Autoscaling GitLab CI jobs on AWS Fargate
+  body: You can now auto-scale GitLab CI on AWS Fargate with the MVC release of GitLab’s AWS Fargate Driver. With this new autoscaling pattern, GitLab’s AWS Fargate driver automatically runs each build in a separate and isolated container on Amazon’s Elastic Container Service (ECS) using a user-defined container image.
+  stage: Verify
+  self-managed: true
+  gitlab-com: false
+  packages: core, starter, premium, ultimate
+  url: https://gitlab.com/gitlab-org/ci-cd/custom-executor-drivers/fargate/-/blob/master/docs/README.md
+  image_url: https://about.gitlab.com/images/12_9/autoscaling_ci_fargate.png
+  published_at: 2020-04-22
+  release: 12.10

data/whats_new/202008180002_13_0.yml

+---
+- title: Gitaly Cluster for High Availability Git Storage
+  body: GitLab now supports highly available Git storage without using NFS. High Availability (HA) configurations improve the availability of important systems, like Git storage, by removing single points of failure, detecting outages, and automatically switching to a replica. This means that an individual component of the system can fail without causing the end user to experience an outage. Access to Git repositories is critical to developers and businesses, because when an outage occurs, developers can’t push code, and deployments are blocked.
+  stage: Create
+  self-managed: true
+  gitlab-com: false
+  packages: core, starter, premium, ultimate
+  url: https://docs.gitlab.com/ee/administration/gitaly/praefect.html
+  image_url: https://about.gitlab.com/images/13_0/praefect-architecture.png
+  published_at: 2020-05-22
+  release: 13.0
+- title: Auto Deploy to ECS
+  body: Until now, there hasn’t been a simple way to deploy to Amazon Web Services. As a result, GitLab users had to  spend a lot of time figuring out their own configuration. In GitLab 13.0, Auto DevOps has been extended to support deployment to AWS! GitLab users who are deploying to AWS Elastic Container Service (ECS) can now take advantage of Auto DevOps, even if they are not using Kubernetes.
+  stage: Release
+  self-managed: true
+  gitlab-com: true
+  packages: All
+  url: https://docs.gitlab.com/ee/topics/autodevops/index.html#aws-ecs
+  image_url:
+  published_at: 2020-05-22
+  release: 13.0
+- title: View Epic Hierarchy on a Roadmap
+  body: When leveraging Multi-Level Epics, it can be difficult to keep track of where each child epic lives on the Roadmap. You can now quickly expand a parent epic on your roadmap to view all its child epics to ensure work is properly organized and your planned timeline is on track!
+  stage: Plan
+  self-managed: true
+  gitlab-com: true
+  packages: ultimate, gold
+  url: https://docs.gitlab.com/ee/user/group/roadmap/
+  image_url: https://about.gitlab.com/images/13_0/Expand-Epic-Hierarchy-Roadmap_roadmap.png
+  published_at: 2020-05-22
+  release: 13.0
+- title: Versioned Snippets
+  body: Snippets in GitLab are now version controlled by a Git repository. When editing a Snippet, each change creates a commit. Snippets can also be cloned to make edits locally, and then pushed back to the Snippet repository.
+  stage: Create
+  self-managed: true
+  gitlab-com: true
+  packages: All
+  url: https://docs.gitlab.com/ee/user/snippets.html#versioned-snippets
+  image_url: https://about.gitlab.com/images/13_0/phikai-versioned-snippets.png
+  published_at: 2020-05-22
+  release: 13.0
+- title: Dark Theme in the Web IDE
+  body: For people who spend time working in code editors, the ability to customize the environment to match their preferences is important. Dark themes are some of the most popular for other editors and important for providing a comfortable experience. That's why we're excited that the GitLab Web IDE is now completely themed dark for users who choose the Dark syntax highlighting theme perference!
+  stage: Create
+  self-managed: true
+  gitlab-com: true
+  packages: All
+  url: https://docs.gitlab.com/ee/user/project/web_ide/#themes
+  image_url: https://about.gitlab.com/images/13_0/phikai-web-ide-dark-theme.png
+  published_at: 2020-05-22
+  release: 13.0

data/whats_new/202008180003_13_01.yml

+---
+- title: Manage IT Alerts in GitLab
+  body: GitLab is excited to introduce Alert Management to aggregate multiple IT service alerts in one interface, helping your team triage alerts and promote them to Incidents. We’ve added the ability to triage alerts in a list view, view alert details, assign alerts, update the status of alerts, and create Incident Issues from Alerts.
+  stage: Monitor
+  self-managed: true
+  gitlab-com: true
+  packages: All
+  url: https://docs.gitlab.com/ee/user/project/operations/alert_management.html
+  image_url: https://about.gitlab.com/images/13_1/alert_management.png
+  published_at: 2020-06-22
+  release: 13.1
+- title: Accessibility Testing Merge Request Widget
+  body: Today, developers who want to ensure their application is accessible to everyone suffer from slow feedback loops, which make it difficult to catch degradations in their code. In GitLab 13.1, merge requests can have a widget that details accessibility degradations related to the changed pages. This will immediately show developers the impact of their changes, which helps prevent degradations before they are merged and deployed.
+  stage: Verify
+  self-managed: true
+  gitlab-com: true
+  packages: All
+  url: https://docs.gitlab.com/ee/user/project/merge_requests/accessibility_testing.html#accessibility-merge-request-widget
+  image_url: https://about.gitlab.com/images/13_1/a11y-merge-request-widget.png
+  published_at: 2020-06-22
+  release: 13.1
+- title: Mark any Design Thread as Resolved
+  body: When you receive lots of feedback on a Design, the number of comment pins can build up quickly! As your discussion thread grows, it gets hard to know which discussions are complete and which still need work. Now you’ll have the ability to mark any comment as Resolved to signify that it is now complete. Even better — your resolved comment pins will disappear from the Design so you can focus on what’s left!
+  stage: Create
+  self-managed: true
+  gitlab-com: true
+  packages: All
+  url: https://docs.gitlab.com/ee/user/project/issues/design_management.html#resolve-design-threads
+  image_url: https://about.gitlab.com/images/13_1/resolve-design-comment.gif
+  published_at: 2020-06-22
+  release: 13.1
+- title: Merge Request Reviews moved to Core
+  body: Originally introduced in GitLab 11.4 as a GitLab Premium feature, Merge Request Reviews allow merge request reviewers to submit multiple comments at once, cutting down on notification noise for the merge request author, and allowing for a more cohesive and streamlined review process.
+  stage: Create
+  self-managed: true
+  gitlab-com: true
+  packages: All
+  url: https://docs.gitlab.com/ee/user/discussions/index.html#merge-request-reviews
+  image_url: https://about.gitlab.com/images/13_1/batch_comments.png
+  published_at: 2020-06-22
+  release: 13.1