Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gitlab-runner
gitlab-runner
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,029
    • Issues 2,029
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 192
    • Merge Requests 192
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • gitlab-runnergitlab-runner
  • Merge Requests
  • !2690

Open
Opened Jan 18, 2021 by Alvin Gounder@alvinDeveloper0 of 17 tasks completed0/17 tasks
  • Report abuse
Report abuse

Docs - Update Supported Windows Versions Note

  • Overview 2
  • Commits 2
  • Pipelines 2
  • Changes 1

What does this MR do?

Have changed the wording in the note for supported versions as well as the location of the note. The wording so that there is less ambiguity as the table below implies that Windows 10 is a supported Docker Executor version while our supported versions doc states that it isn't. This is in response to this Windows Runner ticket(internal) where our client made the same assumption that I did in thinking that Windows 10 Pro could run the Docker Executor. Iterative MR 😄

Related issues

Author's checklist (required)

  • Follow the Documentation Guidelines and Style Guide.
  • If you have developer access or higher (for example, GitLab team members or Core Team members)
    • Apply the documentation label.
    • Assign the designated Technical Writer.

When applicable:

  • Update the permissions table.
  • Link docs to and from the higher-level index page, plus other related docs where helpful.
  • Add GitLab's version history note(s).
  • Add/update the feature flag section.
  • If you're changing document headings, search docs/* for old headings and replace them with the new ones to avoid broken anchors.

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
    • Ensure Technical Writing, documentation, and a docs:: scoped label are added.
    • Add docs-only when the only files changed are under docs/*.
    • Add twdoing when starting work on the MR.
    • Add twfinished if Technical Writing team work on the MR is complete but it remains open.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited Jan 18, 2021 by Alvin Gounder
Assignee
Assign to
Reviewer
Request review from
13.10
Milestone
13.10
Assign milestone
Time tracking
Reference: gitlab-org/gitlab-runner!2690
Source branch: alvin-master-patch-07345