Skip to content

Move version info for Geo

Evan Read requested to merge docs/shift-geo-version-info into master

What does this MR do?

I noticed the "Version history" at https://docs.gitlab.com/ee/administration/geo/replication/index.html has more than just version history and, when collapsed, hides important info.

I've moved the version history to the top, and now the important info is in a note that doesn't collapse. See: http://review-docs-docs-wo23i9.178.62.207.141.xip.io/ce/administration/geo/replication/index.html

Author's checklist

  • Follow the Documentation Guidelines and Style Guide.
  • Link docs to and from the higher-level index page, plus other related docs where helpful.
  • Apply the ~Documentation label.

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

  • Optional: 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.

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 and that you merge the equivalent EE MR before the CE MR if both exist.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by Marcia Ramos

Merge request reports