Note, that the 5.2 branch in this repo is already created, but the latest pointer on the web will be set to it automatically when the tag in Desktop is set. This means, that in the docs homepage, latest will point to 5.1 until the tag in Desktop is set accordingly. When merging this PR, 5.0 will be dropped from the web but is available via pdf as usual.
Note, this PR must be merged before the 5.2 tag in Desktop is set to avoid a 404 for latest.
Note that a PR in docs must be made to announce the 5.2 branch. The docs PR must be merged AFTER this PR is merged to avoid a CI error in docs.
Before merging this PR, we should take care that 5.0 has all changes necessary merged as post
merging the 5.0 pdf is fixed.
@michaelstingl @HanaGemela fyi
@mmattel @EParzefall @phil-davis
Post merging this, we need to backport all relevant changes to 5.2
These are the changes necessary to finalize the creation of the 5.2 branch.
The 5.2 branch is already pushed and prepared and is included in the branch protection rules.
When 5.2 (Desktop) is finally out, the 5.0 branch can be archived, see step 4 in https://github.com/owncloud/docs-client-desktop/blob/master/docs/new-version-branch.md
Note, that the 5.2 branch in this repo is already created, but the
latestpointer on the web will be set to it automatically when the tag in Desktop is set. This means, that in the docs homepage,latestwill point to 5.1 until the tag in Desktop is set accordingly. When merging this PR, 5.0 will be dropped from the web but is available via pdf as usual.Note, this PR must be merged before the 5.2 tag in Desktop is set to avoid a 404 for
latest.Note that a PR in docs must be made to announce the 5.2 branch. The docs PR must be merged AFTER this PR is merged to avoid a CI error in docs.
Before merging this PR, we should take care that 5.0 has all changes necessary merged as post merging the 5.0 pdf is fixed.
@michaelstingl @HanaGemela fyi
@mmattel @EParzefall @phil-davis Post merging this, we need to backport all relevant changes to 5.2