Skip to content

Commit 2d92d80

Browse files
committed
doc: Update release instructions for beta phase
1 parent ec23542 commit 2d92d80

File tree

1 file changed

+41
-11
lines changed

1 file changed

+41
-11
lines changed

docs/release.md

Lines changed: 41 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,4 @@
1-
# Releasing alpha versions
2-
3-
This is a prototype, so we make releases only to an alpha channel.
4-
1+
# Making releases
52

63
## Prepare source tree
74

@@ -22,7 +19,7 @@ This is a prototype, so we make releases only to an alpha channel.
2219
* Push the tag to our central repo: `git push origin main v0.0.NNN`
2320

2421

25-
## Build and upload: Android
22+
## Build and upload alpha: Android
2623

2724
* Decrypt the upload key temporarily:
2825

@@ -37,15 +34,17 @@ This is a prototype, so we make releases only to an alpha channel.
3734
```
3835

3936
* Upload to the "Zulip (Flutter prototype)" app on the Play Console,
40-
at [Release -> Testing -> Internal testing][play-internaltesting],
37+
at [Release > Testing > Internal testing][play-internaltesting],
4138
using the "Create new release" button there.
4239

43-
* Don't worry about release notes; "An alpha release." is plenty.
40+
* Write something for release notes. Consider copying the previous
41+
version's, to say it's a beta and where to send feedback
42+
without enumerating changes.
4443

4544
[play-internaltesting]: https://play.google.com/console/developers/8060868091387311598/app/4972181690507348330/tracks/internal-testing
4645

4746

48-
## Build and upload: iOS
47+
## Build and upload alpha: iOS
4948

5049
* Build an app archive:
5150

@@ -70,12 +69,43 @@ This is a prototype, so we make releases only to an alpha channel.
7069
provided all goes well with the "processing" step.
7170
7271
72+
## Promote to beta
73+
74+
* Android via Play Store:
75+
76+
* Go to [Release > Testing > Internal testing][play-internaltesting]
77+
in the Google Play Console. (If you just uploaded the alpha, that
78+
took you here already.)
79+
80+
* Under the release you want to promote, choose "Promote release >
81+
Open testing".
82+
83+
* Confirm and send to Google for review.
84+
85+
86+
* iOS via TestFlight:
87+
88+
* After the build reaches alpha, you can add it to TestFlight so it
89+
goes to our beta users. Go in App Store Connect to [TestFlight >
90+
Testers & Groups > External Testers][asc-external],
91+
and hit the "+" icon at the top of the list of builds to enter a
92+
modal dialog.
93+
94+
* For the "What to Test" notes, see remark above about release notes.
95+
96+
* The same External Testers page should now show the build in status
97+
"Waiting for Review". This typically comes back the next morning,
98+
California time. If successful, the app is out in beta!
99+
100+
[asc-external]: https://appstoreconnect.apple.com/apps/1672696023/testflight/groups/87223480-4e5d-4007-a3a1-542cd410546c
101+
102+
73103
## Announce
74104
75-
* Announce the updated alpha in
76-
[#mobile-team > zulip-flutter releases][releases-thread].
105+
* Announce the updated beta in
106+
[#announce > mobile beta][releases-thread].
77107
78-
[releases-thread]: https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/zulip-flutter.20releases
108+
[releases-thread]: https://chat.zulip.org/#narrow/stream/1-announce/topic/mobile.20beta
79109
80110
81111
## One-time or annual setup

0 commit comments

Comments
 (0)