@@ -48,8 +48,8 @@ patch release:
48
48
- Created a personal access token in GitHub for changelog automation script.
49
49
- Github PAT should be created with ` repo ` access
50
50
- Make sure your signing key is added to the following files in SVN:
51
- - https://dist.apache.org/repos/dist/dev/arrow /KEYS
52
- - https://dist.apache.org/repos/dist/release/arrow /KEYS
51
+ - https://dist.apache.org/repos/dist/dev/datafusion /KEYS
52
+ - https://dist.apache.org/repos/dist/release/datafusion /KEYS
53
53
54
54
### How to add signing key
55
55
@@ -58,8 +58,8 @@ See instructions at https://infra.apache.org/release-signing.html#generate for g
58
58
Committers can add signing keys in Subversion client with their ASF account. e.g.:
59
59
60
60
``` bash
61
- $ svn co https://dist.apache.org/repos/dist/dev/arrow
62
- $ cd arrow
61
+ $ svn co https://dist.apache.org/repos/dist/dev/datafusion
62
+ $ cd datafusion
63
63
$ editor KEYS
64
64
$ svn ci KEYS
65
65
```
@@ -128,7 +128,7 @@ release.
128
128
129
129
See [ #9697 ] ( https://github.com/apache/datafusion/pull/9697 ) for an example.
130
130
131
- Here are the commands that could be used to prepare the ` 5.1 .0` release:
131
+ Here are the commands that could be used to prepare the ` 38.0 .0` release:
132
132
133
133
### Update Version
134
134
@@ -139,10 +139,10 @@ git fetch apache
139
139
git checkout apache/main
140
140
```
141
141
142
- Update datafusion version in ` datafusion/Cargo.toml ` to ` 5.1 .0` :
142
+ Update datafusion version in ` datafusion/Cargo.toml ` to ` 38.0 .0` :
143
143
144
144
```
145
- ./dev/update_datafusion_versions.py 5.1 .0
145
+ ./dev/update_datafusion_versions.py 38.0 .0
146
146
```
147
147
148
148
Lastly commit the version change:
@@ -167,7 +167,7 @@ Pick numbers in sequential order, with `0` for `rc0`, `1` for `rc1`, etc.
167
167
While the official release artifacts are signed tarballs and zip files, we also
168
168
tag the commit it was created for convenience and code archaeology.
169
169
170
- Using a string such as ` 5.1 .0` as the ` <version> ` , create and push the tag by running these commands:
170
+ Using a string such as ` 38.0 .0` as the ` <version> ` , create and push the tag by running these commands:
171
171
172
172
``` shell
173
173
git fetch apache
@@ -181,29 +181,29 @@ git push apache <version>
181
181
Run ` create-tarball.sh ` with the ` <version> ` tag and ` <rc> ` and you found in previous steps:
182
182
183
183
``` shell
184
- GH_TOKEN=< TOKEN> ./dev/release/create-tarball.sh 5.1 .0 0
184
+ GH_TOKEN=< TOKEN> ./dev/release/create-tarball.sh 38.0 .0 0
185
185
```
186
186
187
187
The ` create-tarball.sh ` script
188
188
189
- 1 . creates and uploads all release candidate artifacts to the [ arrow
190
- dev] ( https://dist.apache.org/repos/dist/dev/arrow ) location on the
189
+ 1 . creates and uploads all release candidate artifacts to the [ datafusion
190
+ dev] ( https://dist.apache.org/repos/dist/dev/datafusion ) location on the
191
191
apache distribution svn server
192
192
193
193
2 . provide you an email template to
194
- send to dev@arrow .apache.org for release voting.
194
+ send to dev@datafusion .apache.org for release voting.
195
195
196
196
### Vote on Release Candidate artifacts
197
197
198
- Send the email output from the script to dev@arrow .apache.org . The email should look like
198
+ Send the email output from the script to dev@datafusion .apache.org . The email should look like
199
199
200
200
```
201
- To: dev@arrow .apache.org
202
- Subject: [VOTE][DataFusion] Release Apache DataFusion 5.1 .0 RC0
201
+ To: dev@datafusion .apache.org
202
+ Subject: [VOTE] Release Apache DataFusion 38.0 .0 RC1
203
203
204
204
Hi,
205
205
206
- I would like to propose a release of Apache DataFusion version 5.1 .0.
206
+ I would like to propose a release of Apache DataFusion version 38.0 .0.
207
207
208
208
This release candidate is based on commit: a5dd428f57e62db20a945e8b1895de91405958c4 [1]
209
209
The proposed release artifacts and signatures are hosted at [2].
@@ -214,16 +214,16 @@ and vote on the release.
214
214
215
215
The vote will be open for at least 72 hours.
216
216
217
- [ ] +1 Release this as Apache DataFusion 5.1 .0
217
+ [ ] +1 Release this as Apache DataFusion 38.0 .0
218
218
[ ] +0
219
- [ ] -1 Do not release this as Apache DataFusion 5.1 .0 because...
219
+ [ ] -1 Do not release this as Apache DataFusion 38.0 .0 because...
220
220
221
221
Here is my vote:
222
222
223
223
+1
224
224
225
225
[1]: https://github.com/apache/datafusion/tree/a5dd428f57e62db20a945e8b1895de91405958c4
226
- [2]: https://dist.apache.org/repos/dist/dev/arrow /apache-datafusion-5.1 .0
226
+ [2]: https://dist.apache.org/repos/dist/dev/datafusion /apache-datafusion-38.0 .0
227
227
[3]: https://github.com/apache/datafusion/blob/a5dd428f57e62db20a945e8b1895de91405958c4/CHANGELOG.md
228
228
```
229
229
@@ -234,7 +234,7 @@ For the release to become "official" it needs at least three PMC members to vote
234
234
The ` dev/release/verify-release-candidate.sh ` is a script in this repository that can assist in the verification process. Run it like:
235
235
236
236
```
237
- ./dev/release/verify-release-candidate.sh 5.1 .0 0
237
+ ./dev/release/verify-release-candidate.sh 38.0 .0 0
238
238
```
239
239
240
240
#### If the release is not approved
@@ -249,11 +249,11 @@ NOTE: steps in this section can only be done by PMC members.
249
249
### After the release is approved
250
250
251
251
Move artifacts to the release location in SVN, e.g.
252
- https://dist.apache.org/repos/dist/release/datafusion/datafusion-5.1 .0/ , using
252
+ https://dist.apache.org/repos/dist/release/datafusion/datafusion-38.0 .0/ , using
253
253
the ` release-tarball.sh ` script:
254
254
255
255
``` shell
256
- ./dev/release/release-tarball.sh 5.1 .0 0
256
+ ./dev/release/release-tarball.sh 38.0 .0 0
257
257
```
258
258
259
259
Congratulations! The release is now official!
@@ -263,9 +263,9 @@ Congratulations! The release is now official!
263
263
Tag the same release candidate commit with the final release tag
264
264
265
265
```
266
- git co apache/5.1 .0-rc0
267
- git tag 5.1 .0
268
- git push apache 5.1 .0
266
+ git co apache/38.0 .0-rc0
267
+ git tag 38.0 .0
268
+ git push apache 38.0 .0
269
269
```
270
270
271
271
### Publish on Crates.io
@@ -300,7 +300,7 @@ of the following crates:
300
300
Download and unpack the official release tarball
301
301
302
302
Verify that the Cargo.toml in the tarball contains the correct version
303
- (e.g. ` version = "5.1 .0" ` ) and then publish the crates by running the script ` release-crates.sh `
303
+ (e.g. ` version = "38.0 .0" ` ) and then publish the crates by running the script ` release-crates.sh `
304
304
in a directory extracted from the source tarball that was voted on. Note that this script doesn't
305
305
work if run in a Git repo.
306
306
@@ -413,10 +413,9 @@ https://crates.io/crates/datafusion-substrait/28.0.0
413
413
414
414
### Add the release to Apache Reporter
415
415
416
- Add the release to https://reporter.apache.org/addrelease.html?arrow with a version name prefixed with ` RS-DATAFUSION- ` ,
417
- for example ` RS-DATAFUSION-14.0.0 ` .
416
+ Add the release to https://reporter.apache.org/addrelease.html?datafusion using the version number e.g. 38.0.0.
418
417
419
- The release information is used to generate a template for a board report (see example
418
+ The release information is used to generate a template for a board report (see example from Apache Arrow project
420
419
[ here] ( https://github.com/apache/arrow/pull/14357 ) ).
421
420
422
421
### Delete old RCs and Releases
@@ -431,13 +430,13 @@ Release candidates should be deleted once the release is published.
431
430
Get a list of DataFusion release candidates:
432
431
433
432
``` bash
434
- svn ls https://dist.apache.org/repos/dist/dev/arrow | grep datafusion
433
+ svn ls https://dist.apache.org/repos/dist/dev/datafusion
435
434
```
436
435
437
436
Delete a release candidate:
438
437
439
438
``` bash
440
- svn delete -m " delete old DataFusion RC" https://dist.apache.org/repos/dist/dev/datafusion/apache-datafusion-7.1 .0-rc1/
439
+ svn delete -m " delete old DataFusion RC" https://dist.apache.org/repos/dist/dev/datafusion/apache-datafusion-38.0 .0-rc1/
441
440
```
442
441
443
442
#### Deleting old releases from ` release ` svn
@@ -447,35 +446,25 @@ Only the latest release should be available. Delete old releases after publishin
447
446
Get a list of DataFusion releases:
448
447
449
448
``` bash
450
- svn ls https://dist.apache.org/repos/dist/release/arrow | grep datafusion
449
+ svn ls https://dist.apache.org/repos/dist/release/datafusion
451
450
```
452
451
453
452
Delete a release:
454
453
455
454
``` bash
456
- svn delete -m " delete old DataFusion release" https://dist.apache.org/repos/dist/release/datafusion/datafusion-7 .0.0
455
+ svn delete -m " delete old DataFusion release" https://dist.apache.org/repos/dist/release/datafusion/datafusion-37 .0.0
457
456
```
458
457
459
- ### Publish the User Guide to the Arrow Site
460
-
461
- - Run the ` build.sh ` in the ` docs ` directory from the release tarball.
462
- - Clone the [ arrow-site] ( https://github.com/apache/arrow-site ) repository
463
- - Checkout the ` asf-site ` branch
464
- - Copy content from ` docs/build/html/* ` to the ` datafusion ` directory in arrow-site
465
- - Create a PR against the ` asf-site ` branch ([ example] ( https://github.com/apache/arrow-site/pull/237 ) )
466
- - Once the PR is merged, the content will be published to https://datafusion.apache.org/ by GitHub Pages (this
467
- can take some time).
468
-
469
458
### Optional: Write a blog post announcing the release
470
459
471
- We typically crowdsource release announcements by collaborating on a Google document, usually starting
460
+ We typically crowd source release announcements by collaborating on a Google document, usually starting
472
461
with a copy of the previous release announcement.
473
462
474
463
Run the following commands to get the number of commits and number of unique contributors for inclusion in the blog post.
475
464
476
465
``` bash
477
- git log --pretty=oneline 10 .0.0..11 .0.0 datafusion datafusion-cli datafusion-examples | wc -l
478
- git shortlog -sn 10 .0.0..11 .0.0 datafusion datafusion-cli datafusion-examples | wc -l
466
+ git log --pretty=oneline 37 .0.0..38 .0.0 datafusion datafusion-cli datafusion-examples | wc -l
467
+ git shortlog -sn 37 .0.0..38 .0.0 datafusion datafusion-cli datafusion-examples | wc -l
479
468
```
480
469
481
470
Once there is consensus on the contents of the post, create a PR to add a blog post to the
0 commit comments