Add Rails problem in multi version developer docs

What does this MR do?

• Add Rails problem in multi version developer docs

Related issues

https://gitlab.com/gitlab-org/release/retrospectives/-/issues/38

Author's checklist (required)

• Follow the Documentation Guidelines and Style Guide.
• If you have Developer permissions or higher:
  • Ensure that the product tier badge is added to doc's h1.
  • Apply the documentation label, plus:
    • The corresponding DevOps stage and group labels, if applicable.
    • development guidelines when changing docs under doc/development/*, CONTRIBUTING.md, or README.md.
    • development guidelines and Documentation guidelines when changing docs under development/documentation/*.
    • development guidelines and Description templates (.gitlab/*) when creating/updating issue and MR description templates.
  • Request a review from the designated Technical Writer.

Do not add the feature, frontend, backend, ~"bug", or database labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.

When applicable:

• Update the permissions table.
• Link docs to and from the higher-level index page, plus other related docs where helpful.
• Add the product tier badge accordingly.
• Add GitLab's version history note(s).
• Add/update the feature flag section.

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 docs metadata are present and up-to-date.
  • Ensure Technical Writing and documentation are added.
  • Add the corresponding docs:: scoped label.
  • If working on UI text, add the corresponding UI Text scoped label.
  • Add twdoing when starting work on the MR.
  • Add twfinished if Technical Writing team work on the MR is complete but it remains open.

For more information about labels, see Technical Writing workflows - Labels.

For suggestions that you are confident don't need to be reviewed, change them locally and push a commit directly to save others from unneeded reviews. For example:

• Clear typos, like this is a typpo.
• Minor issues, like single quotes instead of double quotes, Oxford commas, and periods.

For more information, see our documentation on Merging a merge request.

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.

added corrective action development guidelines documentation maintenancedependency labels

assigned to @tkuah

changed milestone to %14.1

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/development/multi_version_compatibility.md

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added 1 commit

• 922498d3 - Add what to do with Rails updates

Compare with previous version

added 1 commit

• f8ea20a8 - Fix grammar in sentence

Compare with previous version

Setting label groupsharding based on @tkuah's group.

added grouptenant scale label

Setting label(s) ~"Category:Sharding" devopsenablement sectionenablement based on groupsharding.

added Category:Cell devopssystems sectioncore platform labels

mentioned in issue gitlab-com/gl-infra/production#4788 (closed)

added 1 commit

• 2aa756c5 - Change to just notifying release manager group

Compare with previous version

marked the checklist item Apply the documentation label, plus: as completed

marked the checklist item Request a review as completed

@mkozono @marcia Can you please help review ?

requested review from @mkozono and @marcia

approved this merge request

added Technical Writing twdoing labels

removed review request for @marcia

added docsimprovement label

added 1 commit

• 650478f7 - Apply 2 suggestion(s) to 1 file(s)

Compare with previous version

Thanks @marcia ! Have applied + responded above

requested review from @marcia and removed review request for @mkozono

added tw-weight3 twfinished labels and removed twdoing label

resolved all threads

added 1 commit

• b02b81aa - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

resolved all threads

marked the checklist item 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. as completed

marked the checklist item Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. as completed

marked the checklist item Ensure a release milestone is set. as completed

approved this merge request

enabled an automatic merge when the pipeline for 1cdeaa44 succeeds

aborted the automatic merge because source branch was updated

added 2169 commits

• b02b81aa...e8f349c5 - 2163 commits from branch master
• decf7b6f - Add Rails problem in multi version developer docs
• 9c4fd4a7 - Add what to do with Rails updates
• a5945237 - Fix grammar in sentence
• 3d69d94d - Change to just notifying release manager group
• a45100ee - Apply 2 suggestion(s) to 1 file(s)
• 2693d728 - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

enabled an automatic merge when the pipeline for 31ee96ed succeeds

merged

mentioned in commit f22913c3

mentioned in issue #334767 (closed)

added workflowstaging label

added workflowcanary label and removed workflowstaging label

added workflowproduction label and removed workflowcanary label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label

added typemaintenance label

added devopsdata stores label and removed devopssystems label

added devopstenant scale groupcells infrastructure sectioninfrastructure platforms labels and removed devopsdata stores grouptenant scale [DEPRECATED] sectioncore platform labels