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

🎨

Browse source
This commit is contained in:
Brendan Forster 2018-03-15 11:05:09 +11:00 committed by GitHub
parent 949f3be0a8
commit e04a560ec8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -6,7 +6,7 @@ We have three channels to which we can release: `production`, `beta`, and `test`
- `production` is the channel from which the general public downloads and receives updates. It should be stable and polished.
- `beta` is released more often than `production`. We want to ensure master is always in a state where it can be released to users, so it should be used as the source for beta releases as an opportunity for additional QA before releasing to production.
- `beta` is released more often than `production`. We want to ensure `master` is always in a state where it can be released to users, so it should be used as the source for `beta` releases as an opportunity for additional QA before releasing to `production`.
- `test` is unlike the other two. It does not receive updates. Each test release is locked in time. It's used entirely for providing test releases.
@ -154,4 +154,4 @@ It is normal to monitor Haystack closely for 15 minutes just to make sure.
Once your app updates and you see the visible changes in your app and there are no spikes in errors, celebrate 🎉!!! You did it!
Also it might make sense to continue to monitor Haystack in the background for the next 24 hours.
Also it might make sense to continue to monitor Haystack in the background for the next 24 hours.