Skip to content

docs: make sure release maintainer updates arrow clone #4607

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lidavidm merged 1 commit into from
Jul 28, 2026
+15 −0
Merged

docs: make sure release maintainer updates arrow clone #4607

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions docs/source/development/releasing.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,14 @@ Before creating a Release Candidate

./dev/release/assign-milestone.sh

4. Create a fresh clone of the latest apache/arrow repo, which is used by several steps below.

.. warning:: Make sure an up-to-date clone is used, so that the Linux packaging scripts in particular are in sync, else there is the possibility of corrupting the shared Linux package repositories.

.. code-block::

git clone git@github.com:apache/arrow

Check Nightly Verification Job
------------------------------

Expand Down Expand Up @@ -155,6 +163,7 @@ Create the Release Candidate tag from the updated maintenance branch
# <rc-number> starts at 0 and increments every time the Release Candidate is burned
# so for the first RC this would be: dev/release/01-prepare.sh 1.0.0 0

# make sure <arrow-dir> is up-to-date with apache/arrow:main
dev/release/01-prepare.sh <arrow-dir> <rc-number>

git push -u apache apache-arrow-adbc-<release>-rc<rc-number> maint-<release>
Expand Down Expand Up @@ -187,6 +196,8 @@ Build source and binaries and submit them
#
# This reuses release scripts in apache/arrow. So you need to
# specify cloned apache/arrow directory.

# make sure <arrow-dir> is up-to-date with apache/arrow:main
dev/release/05-linux-upload.sh <arrow-dir> <rc-number>

# Start verifications for binaries and wheels
Expand Down Expand Up @@ -347,6 +358,8 @@ Be sure to go through on the following checklist:
# specify cloned apache/arrow directory.
#
# dev/release/post-05-linux.sh ../arrow 0

# make sure <arrow-dir> is up-to-date with apache/arrow:main
dev/release/post-05-linux.sh <arrow-dir> <rc-number>

.. dropdown:: Update R packages
Expand Down Expand Up @@ -481,6 +494,8 @@ Be sure to go through on the following checklist:
.. code-block:: Bash

# dev/release/post-12-bump-versions.sh ../arrow

# make sure <arrow-dir> is up-to-date with apache/arrow:main
dev/release/post-12-bump-versions.sh <arrow-dir>

.. dropdown:: Publish release blog post
Expand Down
Loading