masterbranch is merged to the Cloud branch.
release-5.32) will be cut once the Mattermost Cloud release that will be used for the next self-managed release has been shipped.
masterbranch into the
masterbranch is merged into a
cloudbranch in order to be mindful of avoiding having incomplete features in a Cloud release, and to include bug fixes that we may want to include in a release.
Cherry-pick Approvedlabel and Self-Managed milestone on the PR. Cloud doesn't have a specific milestone in GitHub and the PRs can be tracked via the
Cherry-pick Approvedlabel. The Release Manager keeps track of PRs with the
Cherry-pick Approvedlabel and Self-Managed milestone on a daily basis.
master) is used, and any regression bug fixes for the next Cloud release will be cherry-picked there. This applies to webapp/server/Enterprise repos.
cloud-2021-01-26release tag. Currently the cadence is that the Mattermost Cloud release shipped in the last week of a month will become the next self-managed release. The release branch for a self-managed release will be cut once the Mattermost Cloud release that will be used for the next self-managed release has been shipped.
masterbranch and it updates hourly.
cloud-2021-06-02-1. With Mattermost Cloud, it's not whether or not a feature is enabled, but whether or not the server is capable of supporting the feature.