Remove outdated GitLab versions

Remove outdated GitLab versions

doc/administration/lfs/index.md

@@ -2,18 +2,15 @@
 stage: Create
 group: Source Code
 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
 disqus_identifier: 'https://docs.gitlab.com/ee/workflow/lfs/lfs_administration.html'
 ---
 
 # GitLab Git Large File Storage (LFS) Administration **(FREE SELF)**
 
-> - Git LFS is supported in GitLab starting with version 8.2.
-> - Support for object storage, such as AWS S3, was introduced in 10.0.
-> - LFS is enabled in GitLab self-managed instances by default.
-
 Documentation about how to use Git LFS are under [Managing large binary files with Git LFS doc](../../topics/git/lfs/index.md).
 
+LFS is enabled in GitLab self-managed instances by default.
+
 ## Requirements
 
 - Users need to install [Git LFS client](https://git-lfs.github.com) version 1.0.1 or later.
@@ -346,8 +343,6 @@ git lfs version
 
 ## Known limitations
 
-- Support for removing unreferenced LFS objects was added in 8.14 onward.
-- LFS authentications via SSH was added with GitLab 8.12.
 - Only compatible with the Git LFS client versions 1.1.0 and later, or 1.0.2.
 - The storage statistics count each LFS object for
   every project linking to it.

doc/api/commits.md

@@ -2,7 +2,6 @@
 stage: Create
 group: Source Code
 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, api
 ---
 
 # Commits API **(FREE)**
@@ -75,8 +74,6 @@ Example response:
 
 ## Create a commit with multiple files and actions
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/6096) in GitLab 8.13.
-
 Create a commit by posting a JSON payload
 
 ```plaintext
@@ -256,8 +253,6 @@ Example response:
 
 ## Get references a commit is pushed to
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/15026) in GitLab 10.6
-
 Get all references (from branches or tags) a commit is pushed to.
 The pagination parameters `page` and `per_page` can be used to restrict the list of references.
 
@@ -291,8 +286,6 @@ Example response:
 
 ## Cherry-pick a commit
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/8047) in GitLab 8.15.
-
 Cherry-picks a commit to a given branch.
 
 ```plaintext
@@ -366,8 +359,6 @@ dry run.
 
 ## Revert a commit
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22919) in GitLab 11.5.
-
 Reverts a commit in a given branch.
 
 ```plaintext
@@ -622,7 +613,7 @@ Example response:
 
 ## Commit status
 
-In GitLab 8.1 and later, this is the new commit status API.
+This is the commit status API for use with GitLab.
 
 ### List the statuses of a commit
 
@@ -752,8 +743,6 @@ Example response:
 
 ## List Merge Requests associated with a commit
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/18004) in GitLab 10.7.
-
 Get a list of Merge Requests related to the specified commit.
 
 ```plaintext

doc/api/merge_request_approvals.md

@@ -2,7 +2,6 @@
 stage: Create
 group: Source Code
 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, api
 ---
 
 # Merge request approvals API **(PREMIUM)**
@@ -15,8 +14,7 @@ in the project. Must be authenticated for all endpoints.
 
 ### Get Configuration
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/183) in GitLab 10.6.
-> - Moved to GitLab Premium in 13.9.
+> Moved to GitLab Premium in 13.9.
 
 You can request information about a project's approval configuration using the
 following endpoint:
@@ -44,8 +42,7 @@ GET /projects/:id/approvals
 
 ### Change configuration
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/183) in GitLab 10.6.
-> - Moved to GitLab Premium in 13.9.
+> Moved to GitLab Premium in 13.9.
 
 If you are allowed to, you can change approval configuration using the following
 endpoint:
@@ -180,7 +177,7 @@ GET /projects/:id/approval_rules
 
 ### Get a single project-level rule
 
-> - Introduced 13.7.
+> Introduced in GitLab 13.7.
 
 You can request information about a single project approval rules using the following endpoint:
 
@@ -527,8 +524,7 @@ Configuration for approvals on a specific Merge Request. Must be authenticated f
 
 ### Get Configuration
 
-> - Introduced in GitLab 8.9.
-> - Moved to GitLab Premium in 13.9.
+> Moved to GitLab Premium in 13.9.
 
 You can request information about a merge request's approval status using the
 following endpoint:
@@ -574,8 +570,7 @@ GET /projects/:id/merge_requests/:merge_request_iid/approvals
 
 ### Change approval configuration
 
-> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/183) in GitLab 10.6.
-> - Moved to GitLab Premium in 13.9.
+> Moved to GitLab Premium in 13.9.
 
 If you are allowed to, you can change `approvals_required` using the following
 endpoint:
@@ -955,8 +950,7 @@ These are system generated rules.
 
 ## Approve Merge Request
 
-> - Introduced in GitLab 8.9.
-> - Moved to GitLab Premium in 13.9.
+> Moved to GitLab Premium in 13.9.
 
 If you are allowed to, you can approve a merge request using the following
 endpoint:
@@ -1019,8 +1013,7 @@ does not match, the response code is `409`.
 
 ## Unapprove Merge Request
 
-> - Introduced in GitLab 9.0.
-> - Moved to GitLab Premium in 13.9.
+> Moved to GitLab Premium in 13.9.
 
 If you did approve a merge request, you can unapprove it using the following
 endpoint:

doc/user/project/repository/branches/index.md

@@ -2,7 +2,6 @@
 stage: Create
 group: Source Code
 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: concepts, howto
 ---
 
 # Branches **(FREE)**
@@ -57,8 +56,6 @@ To compare branches in a repository:
 
 ## Delete merged branches
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/6449) in GitLab 8.14.
-
 ![Delete merged branches](img/delete_merged_branches.png)
 
 This feature allows merged branches to be deleted in bulk. Only branches that
@@ -83,8 +80,6 @@ Search results appear in the following order:
 
 ## Branch filter search box
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/22166) in GitLab 11.5.
-
 ![Branch filter search box](img/branch_filter_search_box_v13_12.png)
 
 This feature allows you to search and select branches quickly. Search results appear in the following order: