refine release notes

Author: alamb

dev/release/README.md

@@ -92,7 +92,7 @@ Using a string such as `v0.52.0` as the `<version>`, create and push the tag by
 
 ```shell
 git fetch apache
-git tag <version>-<rc> apache/main
+git tag <version> apache/main
 # push tag to Github remote
 git push apache <version>
 ```
@@ -102,7 +102,7 @@ git push apache <version>
 Run `create-tarball.sh` with the `<version>` tag and `<rc>` and you found in previous steps:
 
 ```shell
-GH_TOKEN=<TOKEN> ./dev/release/create-tarball.sh 38.0.0 0
+GH_TOKEN=<TOKEN> ./dev/release/create-tarball.sh 0.52.0 1
 ```
 
 The `create-tarball.sh` script
@@ -125,7 +125,7 @@ For the release to become "official" it needs at least three PMC members to vote
 The `dev/release/verify-release-candidate.sh` is a script in this repository that can assist in the verification process. Run it like:
 
 ```shell
-./dev/release/verify-release-candidate.sh 38.0.0 0
+./dev/release/verify-release-candidate.sh 0.52.0 1
 ```
 
 #### If the release is not approved
@@ -139,78 +139,41 @@ NOTE: steps in this section can only be done by PMC members.
 
 ### After the release is approved
 
-Move artifacts to the release location in SVN, e.g.
-https://dist.apache.org/repos/dist/release/datafusion/datafusion-38.0.0/, using
-the `release-tarball.sh` script:
+Move artifacts to the release location in SVN, using the `release-tarball.sh` script:
 
 ```shell
-./dev/release/release-tarball.sh 38.0.0 0
+./dev/release/release-tarball.sh 0.52.0 1
 ```
 
 Congratulations! The release is now official!
 
-### Create release git tags
-
-Tag the same release candidate commit with the final release tag
-
-```shell
-git co apache/38.0.0-rc0
-git tag 38.0.0
-git push apache 38.0.0
-```
-
 ### Publish on Crates.io
 
 Only approved releases of the tarball should be published to
 crates.io, in order to conform to Apache Software Foundation
 governance standards.
 
-An Arrow committer can publish this crate after an official project release has
+A DataFusion committer can publish this crate after an official project release has
 been made to crates.io using the following instructions.
 
 Follow [these
 instructions](https://doc.rust-lang.org/cargo/reference/publishing.html) to
 create an account and login to crates.io before asking to be added as an owner
-to all of the DataFusion crates.
+to the sqlparser DataFusion crates.
 
 Download and unpack the official release tarball
 
 Verify that the Cargo.toml in the tarball contains the correct version
-(e.g. `version = "38.0.0"`) and then publish the crates by running the following commands
+(e.g. `version = "0.52.0"`) and then publish the crates by running the following commands
 
 ```shell
-(cd datafusion/common && cargo publish)
-(cd datafusion/expr-common && cargo publish)
-(cd datafusion/physical-expr-common && cargo publish)
-(cd datafusion/functions-aggregate-common && cargo publish)
-(cd datafusion/expr && cargo publish)
-(cd datafusion/execution && cargo publish)
-(cd datafusion/physical-expr && cargo publish)
-(cd datafusion/functions && cargo publish)
-(cd datafusion/functions-aggregate && cargo publish)
-(cd datafusion/functions-window && cargo publish)
-(cd datafusion/functions-nested && cargo publish)
-(cd datafusion/sql && cargo publish)
-(cd datafusion/optimizer && cargo publish)
-(cd datafusion/common-runtime && cargo publish)
-(cd datafusion/physical-plan && cargo publish)
-(cd datafusion/physical-optimizer && cargo publish)
-(cd datafusion/catalog && cargo publish)
-(cd datafusion/core && cargo publish)
-(cd datafusion/proto-common && cargo publish)
-(cd datafusion/proto && cargo publish)
-(cd datafusion/substrait && cargo publish)
+(cd sqlparser && cargo publish)
 ```
 
-
-
-## `sqlparser_derive` crate
-
-Currently this crate is manually published via `cargo publish`.
+If necessary, also publish the `sqlparser_derive` crate:
 
 crates.io homepage: https://crates.io/crates/sqlparser_derive
 
 ```shell
-cd derive
-cargo publish
+(cd derive && cargo publish
 ```