fix(release): prepare the 55 release process (#2527)

Author: andygrove

.asf.yaml

@@ -55,6 +55,9 @@ github:
     branch-54:
       required_pull_request_reviews:
         required_approving_review_count: 1
+    branch-55:
+      required_pull_request_reviews:
+        required_approving_review_count: 1
   # publishes the content of the `asf-site` branch to
   # https://datafusion.apache.org/ballista/
   rulesets:

dev/release/README.md

@@ -87,6 +87,7 @@ Before creating a new release:
 - a PR should be created and merged to update the major version number of the project. There is a script to automate
   updating the version number: `./dev/update_ballista_versions.py 0.11.0`. The script does not change `python/`,
   which is versioned as part of the [Python client release](../../python/dev/release/README.md)
+- Add the new release branch to `github.protected_branches` in `.asf.yaml` so that it requires an approving review
 - A new release branch should be created, such as `branch-0.11`
 
 Once the release branch has been created, the `main` branch can immediately go back to depending on DataFusion with a
@@ -155,9 +156,9 @@ tag the commit it was created for convenience and code archaeology.
 Using a string such as `0.11.0` as the `<version>`, create and push the tag by running these commands:
 
 ```shell
-git tag <version>-<rc>
+git tag <version>-rc<rc>
 # push tag to Github remote
-git push apache <version>
+git push apache <version>-rc<rc>
 ```
 
 ### Create, sign, and upload artifacts

dev/release/create-tarball.sh

@@ -103,7 +103,7 @@ Here is my vote: +1
 
 [1]: https://github.com/apache/datafusion-ballista/tree/${release_hash}
 [2]: ${url}
-[3]: https://github.com/apache/datafusion-ballista/blob/${release_hash}/CHANGELOG.md
+[3]: https://github.com/apache/datafusion-ballista/blob/${release_hash}/docs/source/changelog/${version}.md
 MAIL
 echo "---------------------------------------------------------"
 

dev/release/verify-release-candidate.sh

@@ -141,11 +141,26 @@ test_source_distribution() {
     exit 1
   fi
 
-  # Note can't verify other ballista crates as they depend
-  # on ballista-core which isn't published yet
-  pushd ballista/core
-    cargo publish --dry-run
-  popd
+  # Check that Cargo can determine the package contents for every crate that
+  # will be published. Full dry runs of dependent crates are not possible until
+  # their Ballista dependencies have been published to crates.io.
+  publishable_crates=(
+    ballista-core
+    ballista-api-types
+    ballista-executor
+    ballista-history
+    ballista-scheduler
+    ballista
+    ballista-cli
+  )
+  for crate in "${publishable_crates[@]}"; do
+    cargo package --list --package "${crate}" --locked >/dev/null
+  done
+
+  # These two crates have no unpublished Ballista dependencies, so Cargo can
+  # build and validate their complete publish artifacts before the vote.
+  cargo publish --dry-run --package ballista-core --locked
+  cargo publish --dry-run --package ballista-api-types --locked
 }
 
 TEST_SUCCESS=no