Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MM-50458] Desktop App release process #1252

Merged
merged 20 commits into from Jun 14, 2023
Merged

[MM-50458] Desktop App release process #1252

merged 20 commits into from Jun 14, 2023

Conversation

devinbinnie
Copy link
Member

Summary

This contains a release process document for the Desktop App, outlining how to perform the release including the App Store work.

Ticket Link

https://mattermost.atlassian.net/browse/MM-50458

@devinbinnie devinbinnie added 1: Dev Review Requires review by a core commiter 2: Editor Review Requires review by an editor labels May 25, 2023
@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA f72580c

2 similar comments
@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA f72580c

@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA f72580c

@github-actions
Copy link

Newest code from cwarnermm has been published to preview environment for Git SHA cdd3785

Copy link
Member

@cwarnermm cwarnermm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @devinbinnie! Provided editorial feedback inline

site/content/internal/desktop-release-process.md Outdated Show resolved Hide resolved

***NOTE**: For the purposes of this document, the letter `X` will refer to the major version number, `Y` wil refer to the minor version number, and `Z` will refer to the patch (dot) version number.*

### Before you begin
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's start at H2 for major headings on a dev docs page (##) rather than H3 headings.

site/content/internal/desktop-release-process.md Outdated Show resolved Hide resolved
Before starting a new release, you want to make sure you do a few things:
- Check to make sure that there are no further Story tickets waiting to be merged. You can check JIRA to see if there are anything tickets with the Fix version: `vX.Y Desktop App`. If there are, you'll want to wait until those have been merged.

- If you work off of a for of the `mattermost/desktop` repo, make sure your local master branch is up to date:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- If you work off of a for of the `mattermost/desktop` repo, make sure your local master branch is up to date:
- If you work off of the `mattermost/desktop` repository, make sure your local master branch is up to date:

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, that should say "a fork of" which is the important part here. I'll manually fix this one.

git checkout master && git fetch --all && git merge upstream/master`
```

### Starting a new release
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please avoid gerund verb constructions (-ing) in titles

site/content/internal/desktop-release-process.md Outdated Show resolved Hide resolved
site/content/internal/desktop-release-process.md Outdated Show resolved Hide resolved
site/content/internal/desktop-release-process.md Outdated Show resolved Hide resolved
site/content/internal/desktop-release-process.md Outdated Show resolved Hide resolved
site/content/internal/desktop-release-process.md Outdated Show resolved Hide resolved
@cwarnermm cwarnermm removed the 2: Editor Review Requires review by an editor label May 26, 2023
devinbinnie and others added 2 commits May 26, 2023 09:15
Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA a0679b9

@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA 6a37a40

devinbinnie and others added 3 commits May 26, 2023 09:17
Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA 3cee15a

@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA 6b9712c

devinbinnie and others added 2 commits May 26, 2023 09:18
Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA 249b05a

Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA 2d4f895

@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA c8f3e66

Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA 96af076

devinbinnie and others added 2 commits May 26, 2023 09:19
Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA 0285cb9

Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA f083628

@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA 25ffb52

devinbinnie and others added 2 commits May 26, 2023 09:20
Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
Co-authored-by: Carrie Warner (Mattermost) <74422101+cwarnermm@users.noreply.github.com>
@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA 6a0d26d

@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA 7daf3b9

@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA 2fb3139

@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA cfb9d88

Copy link
Member

@marianunez marianunez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @devinbinnie! Instructions LGTM 👍

This process looks like a good candidate for a playbook we can run in the Release: Desktop channel.

Comment on lines +98 to +100
If the app is **approved** by App Review, you will get an email from App Store Connect saying "Your submission was accepted". From there, you can go back and release the app once the final release has been cut.

If the app is **rejected** by App Review, you will get an email from App Store Connect saying "We noticed an issue with your submission". At that point, you'll need to log back into App Store Connect and review their comments. Make the necessary changes and you can follow the same process as above to re-submit for review until the app has been approved.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How long do they usually take for an answer?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@devinbinnie - friendly bump on Maria's question.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry - missed this :D

Usually about 24 hours is their turnaround time, depends on the time of day. I'll add a note in here about that.

@@ -0,0 +1,117 @@
---
title: Desktop Release Process
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. If you'd like, feel free to add steps from this doc to the existing Playbook we have https://community.mattermost.com/playbooks/playbooks/h3a39biacpnuim7ufmwiuuoxfo/outline.
  2. I can also add a link to this page from the Handbook release process page https://handbook.mattermost.com/operations/research-and-development/product/release-process/desktop-release.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@devinbinnie - friendly bump on Amy's feedback.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missed this as well 😅

I can have a look at the playbook and make sure these line up as well :)
A link to this page would definitely be helpful.

@github-actions
Copy link

github-actions bot commented Jun 8, 2023

Newest code from hanzei has been published to preview environment for Git SHA e10a5f8

@github-actions
Copy link

github-actions bot commented Jun 9, 2023

Newest code from devinbinnie has been published to preview environment for Git SHA e4a1591

@github-actions
Copy link

Newest code from devinbinnie has been published to preview environment for Git SHA fb21118

@devinbinnie devinbinnie merged commit 0752136 into master Jun 14, 2023
4 checks passed
@devinbinnie devinbinnie deleted the MM-50458 branch June 14, 2023 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1: Dev Review Requires review by a core commiter
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants