Follow up issue to update documentation based on [slack discussion around frontend/backend multi version compatibility](https://gitlab.slack.com/archives/C02PF508L/p1595216592013300). > caalberts 20 Jul at 11:43 > I have a question on @smcgivern’s note in week in review about multi-version compatibility. If a backend changed is deployed first to production, but frontend is still using an older version of an API, how would the backend respond to this request? Am I right to say that the backend change itself is required to be backward compatible with older frontend code? > > stanhu 10 days ago > yes > > simon 10 days ago > think it's worth a clarifying statement around that after "We must make sure that the application works properly in these states."? > > simon 10 days ago > "the backend change itself is required to be backward compatible with older frontend code" was very clear to me > > smcgivern 7 hours ago > @simon @caalberts this is a good suggestion. would either of you feel up to creating an MR to https://gitlab.com/gitlab-org/gitlab/-/blob/master/doc/development/multi_version_compatibility.md make that more prominent? > GitLabGitLab > doc/development/multi_version_compatibility.md · master · GitLab.org / GitLab > GitLab is an open source end-to-end software development platform with built-in version control, issue tracking, code review, CI/CD, and more. Self-host GitLab on your own servers, in a container, or... > > stanhu 7 hours ago > @nolith is adding this in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/38205/diffs > > smcgivern 7 hours ago > oh, perfect! > > stanhu 7 hours ago > though maybe this has more to do with DB migrations now that I read it...but it could be extended to frontend/backend > > smcgivern 7 hours ago > yeah, I think Heinrich's comment is valid > > smcgivern 7 hours ago > commented