ARROW-18291: [Release][Docs] Update how to release #14612
Conversation
|
|
|
@raulcd @assignUser You may be interested in this. |
|
@github-actions crossbow submit preview-docs |
|
Revision: 8216ae5 Submitted crossbow builds: ursacomputing/crossbow @ actions-81ab023231
|
| #. Bump versions | ||
| #. Update tags for Go modules | ||
| #. Update docs | ||
| #. Announce the new release | ||
| #. Remove old artifacts |
There was a problem hiding this comment.
Should we add the update of the Arrow version on the cookbooks as a post-release task too? The main problem is that is requires the conda packages to be available at the moment and they might take a while. I am monitoring for them to be available for 10.0.0 to update the cookbooks version at the moment.
There was a problem hiding this comment.
Wow, I didn't know that!
I've added a place holder for it. Could you fill it in a follow-up pull request?
docs/source/developers/release.rst
Outdated
| dev/release/post-02-binary.sh <version> <rc number> | ||
| .. code-block:: Bash | ||
|
|
||
| ## You need to run this on macOS that Homebrew is installed. |
There was a problem hiding this comment.
Minor nit, this should also work with brewlinux, that's how I did the 9.0.0 one
There was a problem hiding this comment.
Really!? I didn't know that!
I've added "or Linux".
docs/source/developers/release.rst
Outdated
| :class-title: sd-fs-5 | ||
| :class-container: sd-shadow-md | ||
|
|
||
| The API documentations are generated in release process. We just need to upload the generated API documentations: |
There was a problem hiding this comment.
| The API documentations are generated in release process. We just need to upload the generated API documentations: | |
| The API documentations are generated in the release process. We just need to upload the generated API documentations: |
There was a problem hiding this comment.
And you can also remove "API", since this is for all docs, not just API docs
|
Changes can be found here from the pr-docs job: http://crossbow.voltrondata.com/pr_docs/14612/developers/release.html |
| @@ -216,123 +216,365 @@ Be sure to go through on the following checklist: | |||
| #. Start the new version on JIRA on the ARROW project | |||
| #. Start the new version on JIRA for the related CPP PARQUET version | |||
| #. Merge changes on release branch to maintenance branch for patch releases | |||
| #. Add the new release to the Apache Reporter System | |||
| #. Upload source | |||
| #. Upload binaries | |||
| #. Update website | |||
There was a problem hiding this comment.
Should we add preparing and releasing the blog post to this list?
There was a problem hiding this comment.
Good catch!
I've added a place holder for it. Could you fill it in a follow-up pull request?
docs/source/developers/release.rst
Outdated
| :animate: fade-in-slide-down | ||
| :class-title: sd-fs-5 | ||
| :class-container: sd-shadow-md | ||
|
|
||
| Fork the `arrow-site repository <https://github.com/apache/arrow-site>`_ and clone it next to the arrow repository. | ||
| A PMC member must upload the binary release artifacts to Artifactory: |
There was a problem hiding this comment.
I thought committers also have access to the artifactory, not entirely sure though, might need to request the access, couldn't find anything in the infra wiki. 🤷
|
Benchmark runs are scheduled for baseline = 3767599 and contender = 4e99f59. 4e99f59 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
No description provided.