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
The significant change here is copying the packages from svn into the dist folder instead of rebuilding packages for PyPI upload after voting.
2 other essential changes:
1. Unified the release docs into one piece
2. Added email template instead of relying on the user modifying Airflow email template
Edit the file `airflow/airflow/api_connexion/openapi/v1.yaml`
110
-
Make sure it has the following `securitySchema`s listed under security `section`
111
-
```yaml
112
-
security:
113
-
- Basic: []
114
-
- GoogleOpenId: []
115
-
- Kerberos: []
116
-
```
117
-
If your deployment of Airflow uses any different authentication mechanism than the three listed above, you might need to make further changes to the `v1.yaml` and generate your own client, see [OpenAPI Schema specification](https://swagger.io/docs/specification/authentication/) for details.
118
-
(*These changes should not be commited to the upstream `v1.yaml` [as it will generate misleading openapi documentaion](https://github.com/apache/airflow/pull/17174)*)
119
-
120
-
Update the VERSION string in setup.py with the corresponding new version string.
121
-
122
-
```bash
123
-
cd airflow
124
-
125
-
# bump up the version in python.sh & run the following command
Edit the file `airflow/airflow/api_connexion/openapi/v1.yaml`
41
+
Make sure it has the following `securitySchema`s listed under security `section`
42
+
```yaml
43
+
security:
44
+
- Basic: []
45
+
- GoogleOpenId: []
46
+
- Kerberos: []
47
+
```
48
+
If your deployment of Airflow uses any different authentication mechanism than the three listed above, you might need to make further changes to the `v1.yaml` and generate your own client, see [OpenAPI Schema specification](https://swagger.io/docs/specification/authentication/) for details.
49
+
(*These changes should not be commited to the upstream `v1.yaml` [as it will generate misleading openapi documentaion](https://github.com/apache/airflow/pull/17174)*)
50
+
51
+
52
+
```bash
53
+
54
+
# bump up the version in python.sh & run the following command
@@ -148,12 +203,63 @@ is not supposed to be used by and advertised to the end-users who do not read th
148
203
149
204
- Push Tag for the release candidate
150
205
151
-
```shell script
152
-
git push origin ${VERSION}
153
-
```
206
+
```shell script
207
+
git push origin ${VERSION}
208
+
```
154
209
155
210
## Prepare Vote email on the Airflow Client release candidate
156
-
See Airflow process documented [here](https://github.com/apache/airflow/blob/master/dev/README_RELEASE_AIRFLOW.md#prepare-vote-email-on-the-apache-airflow-release-candidate) (just replace Airflow with Airflow Client).
211
+
212
+
Subject:
213
+
214
+
```shell script
215
+
cat <<EOF
216
+
[VOTE] Release Airflow Python Client ${VERSION_WITHOUT_RC} from ${VERSION}
217
+
EOF
218
+
```
219
+
220
+
Body:
221
+
222
+
```shell script
223
+
cat <<EOF
224
+
Hey fellow Airflowers,
225
+
226
+
I have cut the first release candidate for the Airflow Python Client ${VERSION}.
227
+
The client consists of APIs corresponding to REST APIs available in
228
+
*Apache Airflow ${AIRFLOW_VERSION}*. This email is calling for a vote on
229
+
the release, which will last for 72 hours. Consider this my (binding) +1.
Only votes from PMC members are binding, but the release manager should
245
+
encourage members of the community to test the release and vote with
246
+
"(non-binding)".
247
+
248
+
*Changelog:*
249
+
250
+
*Major changes:*
251
+
...
252
+
253
+
*Major fixes:*
254
+
...
255
+
256
+
*New API supported:*
257
+
...
258
+
259
+
Cheers,
260
+
<your name>
261
+
EOF
262
+
```
157
263
158
264
# Verify the release candidate by PMCs
159
265
See Airflow process documented [here](https://github.com/apache/airflow/blob/master/dev/README_RELEASE_AIRFLOW.md#verify-the-release-candidate-by-pmcs).
@@ -167,8 +273,6 @@ See Airflow process documented [here](https://github.com/apache/airflow/blob/mas
167
273
## Signature check
168
274
See Airflow process documented [here](https://github.com/apache/airflow/blob/master/dev/README_RELEASE_AIRFLOW.md#signature-check).
169
275
170
-
171
-
172
276
# Verify release candidates by Contributors
173
277
This can be done (and we encourage to) by any of the Contributors. In fact, it's best if the
174
278
actual users of Airflow Client test it in their own staging/test installations. Each release candidate
@@ -187,23 +291,55 @@ that the client works as you expected.
187
291
188
292
## Summarize the voting for the Apache Airflow client release
189
293
190
-
See Airflow process documented [here](https://github.com/apache/airflow/blob/master/dev/README_RELEASE_AIRFLOW.md#publish-the-final-apache-airflow-release) (just replace Airflow with Airflow Client).
294
+
```shell script
295
+
Hello,
296
+
297
+
Apache Airflow Python Client 2.5.0 (based on RC1) has been accepted.
0 commit comments