Remove old GitLab versions from Code Review docs

doc/user/project/merge_requests/allow_collaboration.md

@@ -2,13 +2,10 @@
 stage: Create
 group: Code Review
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
-type: reference, howto
 ---
 
 # Allow collaboration on merge requests across forks **(FREE)**
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/17395) in GitLab 10.6.
-
 When a user opens a merge request from a fork, they are given the option to allow
 upstream members to collaborate with them on the source branch. This allows
 the members of the upstream project to make small fixes or rebase branches

doc/user/project/merge_requests/creating_merge_requests.md

@@ -2,7 +2,6 @@
 stage: Create
 group: Code Review
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
-type: howto
 description: "How to create merge requests in GitLab."
 disqus_identifier: 'https://docs.gitlab.com/ee/gitlab-basics/add-merge-request.html'
 ---
@@ -111,10 +110,6 @@ For more information, [see the forking workflow documentation](../repository/for
 
 ## By sending an email
 
-> The format of the generated email address changed in GitLab 11.7.
-  The earlier format is still supported so existing aliases
-  or contacts still work.
-
 You can create a merge request by sending an email message to GitLab.
 The merge request target branch is the project's default branch.
 
@@ -142,8 +137,6 @@ A merge request is created.
 
 ### Add attachments when creating a merge request by email
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22723) in GitLab 11.5.
-
 You can add commits to a merge request by adding
 patches as attachments to the email. All attachments with a filename
 ending in `.patch` are considered patches and are processed

doc/user/project/merge_requests/getting_started.md

@@ -2,7 +2,6 @@
 stage: Create
 group: Code Review
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
-type: index, reference
 description: "Getting started with merge requests."
 ---
 
@@ -92,8 +91,7 @@ and the merge request is added to their
 
 #### Multiple assignees **(PREMIUM)**
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/2004) in GitLab 11.11.
-> - Moved to GitLab Premium in 13.9
+> Moved to GitLab Premium in 13.9
 
 Multiple people often review merge requests at the same time.
 GitLab allows you to have multiple assignees for merge requests

doc/user/project/merge_requests/revert_changes.md

@@ -2,7 +2,6 @@
 stage: Create
 group: Code Review
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
-type: reference, concepts
 ---
 
 # Revert changes **(FREE)**
@@ -12,11 +11,6 @@ by clicking the **Revert** button in merge requests and commit details.
 
 ## Revert a merge request
 
-NOTE:
-The **Revert** button is available only for merge requests
-created in GitLab 8.5 and later. However, you can still revert a merge request
-by reverting the merge commit from the list of Commits page.
-
 NOTE:
 The **Revert** button is shown only for projects that use the
 merge method "Merge Commit", which can be set under the project's

doc/user/project/merge_requests/versions.md

@@ -39,8 +39,6 @@ changes appears as a system note.
 
 ## Find the merge request that introduced a change
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/2383) in GitLab 10.5.
-
 When viewing the commit details page, GitLab links to the merge request (or
 merge requests, if it's in more than one) containing that commit.