development/github-desktop
development/github-desktop
1
0
Fork 0
mirror of https://github.com/desktop/desktop synced 2024-09-13 21:31:32 +00:00
Code Issues Packages Projects Releases Wiki Activity

Mention enabling prod releases in docs

Browse source
This commit is contained in:
Sergio Padrino 2022-09-05 17:25:02 +02:00
parent 5a9963c30e
commit 69c7d05890
1 changed files with 9 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
docs/process/releasing-updates.md
View file

@ -154,7 +154,7 @@ IMPORTANT NOTE: Ensure that you indicate which channel to release to. If not, ch
### 5. Check for Completed Release ### 5. Check for Completed Release
Go to [Central's Deployments](https://central.github.com/deployments) to find your release; you'll see something at the top of the page like: Go to [Central's Deployments](https://central.githubapp.com/deployments) to find your release; you'll see something at the top of the page like:
``` ```
desktop/desktop deployed from {YOUR_BRANCH}@{HASH_ABBREVIATION_FOR_COMMIT} to {production|beta|test} desktop/desktop deployed from {YOUR_BRANCH}@{HASH_ABBREVIATION_FOR_COMMIT} to {production|beta|test}
``` ```
@ -163,7 +163,11 @@ it will initially specify its state as `State: pending` and will be completed wh
You will also see this in Chat: You will also see this in Chat:
`desktopbot tagged desktop/release-{YOUR_VERSION}` `desktopbot tagged desktop/release-{YOUR_VERSION}`
### 6. Test that your app auto-updates to new version ### 6. Enable the Release
Production releases are disabled by default. To enable them, go to [Central's Release Control](https://central.githubapp.com/release_control), select the percentage of users that will be able to auto-update to this new version, and then click the "Apply" button.
### 7. Test that your app auto-updates to new version
When the release in Central is in `State: released` for `beta` or `production`, switch to your installed Desktop instance and make sure that the corresponding (prod|beta) app auto-updates. When the release in Central is in `State: released` for `beta` or `production`, switch to your installed Desktop instance and make sure that the corresponding (prod|beta) app auto-updates.
@ -173,11 +177,11 @@ If you don't have the app for `beta`, for example, you can always download the p
_Make sure you move your application out of the Downloads folder and into the Applications folder for macOS or it won't auto-update_. _Make sure you move your application out of the Downloads folder and into the Applications folder for macOS or it won't auto-update_.
### 7. Merge PR with changelog entries ### 8. Merge PR with changelog entries
So that we keep the `changelog.json` up to date. Beta entries will be used for the upcoming production release. So that we keep the `changelog.json` up to date. Beta entries will be used for the upcoming production release.
### 8. Check Error Reporting ### 9. Check Error Reporting
If an error occurs during the release process, a needle will be reported to Central's [Haystack](https://haystack.githubapp.com/central). If an error occurs during the release process, a needle will be reported to Central's [Haystack](https://haystack.githubapp.com/central).
@ -186,7 +190,7 @@ After the release is deployed, you should monitor Desktop's [Haystack](https://h
#### Final Beta release #### Final Beta release
If the active beta is the last beta prior to a production release, extra care should be taken when looking at Desktop's [Haystack](https://haystack.githubapp.com/desktop) roll-ups. The lead engineer responsible for deployment should produce a _Haystack report_ the day before and after the release. The report should contain a list of any new or unexpected errors from the past beta releases in the milestone and be published to the team's Slack channel. If the active beta is the last beta prior to a production release, extra care should be taken when looking at Desktop's [Haystack](https://haystack.githubapp.com/desktop) roll-ups. The lead engineer responsible for deployment should produce a _Haystack report_ the day before and after the release. The report should contain a list of any new or unexpected errors from the past beta releases in the milestone and be published to the team's Slack channel.
### 9. Celebrate ### 10. Celebrate
Once your app updates and you see the visible changes in your app and there are no spikes in errors, celebrate 🎉!!! You did it! Once your app updates and you see the visible changes in your app and there are no spikes in errors, celebrate 🎉!!! You did it!