Note, that the 5.3 branch in this repo is already created, but the latest pointer on the web will be set to it automatically when the tag in Client is set. This means, that in the docs homepage, latest will point to 5.2 until the tag in Client is set accordingly. When merging this PR, 5.1 will be dropped from the web.
Note that this PR must be merged before the 5.3 tag in Client is set to avoid a 404 for latest.
Note before merging this PR, we should take care that 5.1 has all necessary changes merged.
@TheOneRing fyi
@mmattel @phil-davis
Post merging this, we need to backport all relevant changes to 5.3
These are the changes necessary to finalize the creation of the 5.3 branch.
The 5.3 branch is already pushed and prepared and is included in the branch protection rules.
When 5.3 is finally out, the 5.1 branch can be archived, see step 3 in Create a New Version Branch
Note, that the 5.3 branch in this repo is already created, but the
latestpointer on the web will be set to it automatically when the tag in Client is set. This means, that in the docs homepage,latestwill point to 5.2 until the tag in Client is set accordingly. When merging this PR, 5.1 will be dropped from the web.Note that this PR must be merged before the 5.3 tag in Client is set to avoid a 404 for
latest.Note before merging this PR, we should take care that 5.1 has all necessary changes merged.
@TheOneRing fyi
@mmattel @phil-davis Post merging this, we need to backport all relevant changes to 5.3