You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site/content/internal/desktop-release-process.md
+7-12Lines changed: 7 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,7 @@ weight: 101
12
12
13
13
Before starting a new release, you want to make sure you do a few things:
14
14
- Check to make sure that there are no further Bug or Story tickets waiting to be merged. You can check JIRA to see if there are any tickets with the Fix version: `vX.Y Desktop App`. If there are, you'll want to wait until those have been merged.
15
+
- For major/minor releases, check to make sure that an Electron upgrade has been done shortly before the release. It's important to keep up with the latest security changes in Electron and Chrome.
15
16
16
17
- If you work off of a fork of the `mattermost/desktop` repository, make sure your local master branch is up to date:
17
18
```
@@ -31,12 +32,12 @@ Before starting a new release, you want to make sure you do a few things:
31
32
32
33
## Start a new release
33
34
34
-
1. For a new major or minor release, check out the `master` branch and create a new release branch from it.
35
+
1. For a new major or minor release, check out the `master` branch and create a new release branch from it
35
36
```
36
37
git checkout master
37
38
git checkout -b release-X.Y
38
39
```
39
-
For a patch release, just check out the existing release branch matching the version you're patching.
40
+
For a patch release, or if the branch already exists, just check out the existing release branch matching the version you're patching.
40
41
```
41
42
git checkout release-X.Y
42
43
```
@@ -88,8 +89,8 @@ You can then follow steps **5-8** above to make sure the release is published.
88
89
89
90
Once the final release candidate has been approved by QA, you will need approval from the Mac App Store. To do so, we create a special release for them:
You can then follow steps **5-8** above to make sure the release is published, but make sure that the checkbox for 'set as pre-release` is unchecked.
125
-
126
-
### Final Steps
127
-
128
-
Afterwards, you will need to update the [`ci/latest`](https://git.internal.mattermost.com/ci/latest) repository in GitLab to update the latest version of the Desktop App available on mattermost.com.
129
-
130
-
In that repository there is a file called `release-updates.vars`, and in that file there is a line that says `DESKTOP_STREAM_LATEST`. You can replace that version number with the one you just released, and submit a PR to be reviewed by Release team.
125
+
You can then follow steps **5-8** from the "Start a new release" section above to make sure the release is published, but make sure that the checkbox for 'Set as pre-release` is unchecked.
0 commit comments