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: docs/Release.md
+35-13Lines changed: 35 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,52 +77,46 @@ press *Run Workflow*. Confirm both actions run successfully.
77
77
78
78
Once the alpha versions have been approved for release, we can start publishing.
79
79
80
-
#### 2.1 Tag & Create Release
80
+
#### 2.1 Tag & Merge Release
81
81
82
-
2.1.1 Tag the latest commit on the release branch:
82
+
**2.1.1** Tag the latest commit on the release branch:
83
83
84
84
```
85
85
git tag -s v[x.y.z] -f -m "[x.x.x] release"
86
86
git push origin tag v[x.y.z]
87
87
```
88
88
89
-
2.1.2 Merge the release branch PR into `main`, always through a merge commit! We don't want to lose
89
+
**2.1.2** Merge the release branch PR into `main`, always through a merge commit! We don't want to lose
90
90
our tagged commit.
91
91
92
-
2.1.3 Create a new [Github release](https://github.com/ooni/probe-multiplatform/releases) based on
93
-
the new tag and write the release notes.
94
-
95
-
The new Github release should create new release on Sentry to help with error reporting, and publish
96
-
an internal Slack message warning of the new incoming release.
97
-
98
92
#### 2.2 Publish iOS Apps
99
93
100
94
Go to [Publish iOS Apps](https://github.com/ooni/probe-multiplatform/actions/workflows/publish_ios.yml),
101
95
press *Run Workflow*, use workflow from the new tag, pick both apps and press *Run Workflow*.
102
96
Confirm both actions run successfully. The updates will be reviewed by Apple, so we need to keep an
103
97
eye if they pass.
104
98
105
-
#### 2.2 Publish OONI Probe Android on F-Droid
99
+
#### 2.3 Publish OONI Probe Android on F-Droid
106
100
107
101
By pushing a new tag on Github, F-Droid bots will check if our app `versionCode` was updated. Since
108
102
it was, they will trigger a new build and release it automatically. It should take around 3 days for
109
103
the new release to be available [here](https://f-droid.org/en/packages/org.openobservatory.ooniprobe/)
110
104
but sometimes it can take more time.
111
105
112
-
#### 2.3 Publish OONI Probe Android on Huawei AppGallery
106
+
#### 2.4 Publish OONI Probe Android on Huawei AppGallery
113
107
114
108
Go to [Publish OONI Probe on Huawei AppGallery](https://github.com/ooni/probe-multiplatform/actions/workflows/publish_android_on_huawei.yml),
115
109
press *Run Workflow*, use workflow from the new tag and press *Run Workflow*. Confirm the action ran
116
110
successfully.
117
111
118
-
#### 2.4 Promote News Media Scan Android
112
+
#### 2.5 Promote News Media Scan Android
119
113
120
114
Go to [Promote Android on Google Play](https://github.com/ooni/probe-multiplatform/actions/workflows/promote_android_on_google_play.yml),
121
115
press *Run Workflow*, pick the Organization `dw`, the Current Track
122
116
`alpha`, the Promote Track `production` and press *Run Workflow*. Confirm the action ran
123
117
successfully.
124
118
125
-
#### 2.5 Promote OONI Probe Android
119
+
#### 2.6 Promote OONI Probe Android
126
120
127
121
Since this is our app with the biggest amount of users, we take more steps to release it. First we
128
122
promote from `alpha` to `beta`, and then from `beta` to `production` with a `0.2` (20%) rollout
@@ -131,6 +125,34 @@ value.
131
125
Both steps are done at [Promote Android on Google Play](https://github.com/ooni/probe-multiplatform/actions/workflows/promote_android_on_google_play.yml) like on the previous step, but with the
132
126
Organization as `ooni`.
133
127
128
+
#### 2.7 Publish OONI Probe Desktop
129
+
130
+
#### 2.7.1 Generate apps
131
+
132
+
Go to [Desktop package apps](https://github.com/ooni/probe-multiplatform/actions/workflows/desktop_make.yml),
133
+
press *Run Workflow*, use workflow from the new tag, and press *Run Workflow*. Confirm the action ran
134
+
successfully and download the generated apps (zipped artifact).
135
+
136
+
#### 2.7.2 Sign windows app
137
+
138
+
We need to sign both the windows `.exe` and `.msix` files using our Extended Validation certificate.
139
+
Follow the steps on our internal process to do so.
140
+
141
+
### 2.8 Create Release
142
+
143
+
**2.8.1** Create a new [Github release](https://github.com/ooni/probe-multiplatform/releases)
144
+
based on the new tag.
145
+
146
+
**2.8.2** Write our manual release notes and add at the bottom the automatic changelog using the
147
+
`Generate release notes` button.
148
+
149
+
**2.8.3** Upload all the desktop files downloaded during step *2.7.1*, except the `download.html`
150
+
file, and swapping the windows `.exe` and `.msix` files for their signed versions (step *2.7.2*).
151
+
152
+
**2.8.4** Publish release
153
+
154
+
The new Github release post an internal Slack message warning of the new incoming release.
155
+
134
156
## Monitoring
135
157
136
158
We use Sentry to monitor for crashes and handled errors. We have specific views for:
0 commit comments