You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/11/10 06:46:53 UTC
[GitHub] [arrow] kou commented on a diff in pull request #14612: ARROW-18291: [Release][Docs] Update how to release
kou commented on code in PR #14612:
URL: https://github.com/apache/arrow/pull/14612#discussion_r1018705703
##########
docs/source/developers/release.rst:
##########
@@ -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
#. Update Homebrew packages
#. Update MSYS2 package
#. Upload RubyGems
-#. Upload JS packages
+#. Upload JavaScript packages
#. Upload C# packages
#. Update conda recipes
#. Upload wheels/sdist to pypi
#. Publish Maven artifacts
#. Update R packages
#. Update vcpkg port
+#. Update Conan recipe
#. Bump versions
#. Update tags for Go modules
#. Update docs
+#. Announce the new release
#. Remove old artifacts
Review 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:
##########
@@ -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
Review 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:
##########
@@ -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
#. Update Homebrew packages
#. Update MSYS2 package
#. Upload RubyGems
-#. Upload JS packages
+#. Upload JavaScript packages
#. Upload C# packages
#. Update conda recipes
#. Upload wheels/sdist to pypi
#. Publish Maven artifacts
#. Update R packages
#. Update vcpkg port
+#. Update Conan recipe
#. Bump versions
#. Update tags for Go modules
#. Update docs
+#. Announce the new release
#. Remove old artifacts
-.. dropdown:: Marking the released version as "RELEASED" on JIRA
+.. dropdown:: Mark the released version as "RELEASED" on JIRA
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ - Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ - Click "..." for the release version in "Actions" column
+ - Select "Release"
+ - Set "Release date"
+ - Click "Release" button
- Click "..." for the release version in "Actions" column
+.. dropdown:: Start the new version on JIRA
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ - Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ - Click "..." for the next version in "Actions" column
+ - Select "Edit"
+ - Set "Start date"
+ - Click "Save" button
+
+.. dropdown:: Merge changes on release branch to maintenance branch for patch releases
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
- Select "Release"
+ Merge ``release-X.Y.Z-rcN`` to ``maint-X.Y.Z``:
- Set "Release date"
+ .. code-block:: Bash
- Click "Release" button
+ # git checkout maint-10.0.0
+ git checkout maint-X.Y.Z
+ # git merge release-10.0.0-rc0
+ git merge release-X.Y.Z-rcN
+ # git push -u apache maint-10.0.0
+ git push -u apache maint-X.Y.Z
-.. dropdown:: Starting the new version on JIRA
+.. dropdown:: Add the new release to the Apache Reporter System
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ Add relevant release data for Arrow to `Apache reporter <https://reporter.apache.org/addrelease.html?arrow>`_.
- Click "..." for the next version in "Actions" column
+.. dropdown:: Upload source release artifacts to Subversion
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
- Select "Edit"
+ A PMC member must commit the source release artifacts to Subversion:
- Set "Start date"
+ .. code-block:: Bash
- Click "Save" button
+ # dev/release/post-01-upload.sh 0.1.0 0
+ dev/release/post-01-upload.sh <version> <rc>
-.. dropdown:: Updating the Arrow website
+.. dropdown:: Upload binary release artifacts to Artifactory
: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:
Review Comment:
Right. I've fixed.
##########
docs/source/developers/release.rst:
##########
@@ -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
#. Update Homebrew packages
#. Update MSYS2 package
#. Upload RubyGems
-#. Upload JS packages
+#. Upload JavaScript packages
#. Upload C# packages
#. Update conda recipes
#. Upload wheels/sdist to pypi
#. Publish Maven artifacts
#. Update R packages
#. Update vcpkg port
+#. Update Conan recipe
#. Bump versions
#. Update tags for Go modules
#. Update docs
+#. Announce the new release
#. Remove old artifacts
-.. dropdown:: Marking the released version as "RELEASED" on JIRA
+.. dropdown:: Mark the released version as "RELEASED" on JIRA
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ - Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ - Click "..." for the release version in "Actions" column
+ - Select "Release"
+ - Set "Release date"
+ - Click "Release" button
- Click "..." for the release version in "Actions" column
+.. dropdown:: Start the new version on JIRA
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ - Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ - Click "..." for the next version in "Actions" column
+ - Select "Edit"
+ - Set "Start date"
+ - Click "Save" button
+
+.. dropdown:: Merge changes on release branch to maintenance branch for patch releases
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
- Select "Release"
+ Merge ``release-X.Y.Z-rcN`` to ``maint-X.Y.Z``:
- Set "Release date"
+ .. code-block:: Bash
- Click "Release" button
+ # git checkout maint-10.0.0
+ git checkout maint-X.Y.Z
+ # git merge release-10.0.0-rc0
+ git merge release-X.Y.Z-rcN
+ # git push -u apache maint-10.0.0
+ git push -u apache maint-X.Y.Z
-.. dropdown:: Starting the new version on JIRA
+.. dropdown:: Add the new release to the Apache Reporter System
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ Add relevant release data for Arrow to `Apache reporter <https://reporter.apache.org/addrelease.html?arrow>`_.
- Click "..." for the next version in "Actions" column
+.. dropdown:: Upload source release artifacts to Subversion
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
- Select "Edit"
+ A PMC member must commit the source release artifacts to Subversion:
- Set "Start date"
+ .. code-block:: Bash
- Click "Save" button
+ # dev/release/post-01-upload.sh 0.1.0 0
+ dev/release/post-01-upload.sh <version> <rc>
-.. dropdown:: Updating the Arrow website
+.. dropdown:: Upload binary release artifacts to Artifactory
: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:
- Generate the release note:
+ .. code-block:: Bash
- .. code-block::
-
- # dev/release/post-03-website 0.13.0 0.14.0
- dev/release/post-03-website <previous-version> <version>
-
- Create a pull-request and a Jira with the links the script shows at the end.
+ # dev/release/post-02-binary.sh 0.1.0 0
+ dev/release/post-02-binary.sh <version> <rc number>
-.. dropdown:: Uploading source release artifacts to SVN
+.. dropdown:: Update website
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- A PMC member must commit the source release artifacts to SVN:
+ Add a release note for the new version to our website and update the latest release information:
- .. code-block::
-
- # dev/release/post-01-upload.sh 0.1.0 0
- dev/release/post-01-upload.sh <version> <rc>
+ .. code-block:: Bash
+
+ ## Prepare your fork of https://github.com/apache/arrow-site .
+ ## You need to do this only once.
+ # git clone git@github.com:kou/arrow-site.git ../
+ git clone git@github.com:<YOUR_GITHUB_ID>/arrow-site.git ../
+ cd ../arrow-site
+ ## Add git@github.com:apache/arrow-site.git as "apache" remote.
+ git remote add apache git@github.com:apache/arrow-site.git
+ cd -
+
+ ## Generate a release note for the new version, update the
+ ## latest release information automatically.
+ # dev/release/post-03-website.sh 9.0.0 10.0.0
+ dev/release/post-03-website.sh OLD_X.OLD_Y.OLD_Z X.Y.Z
+
+ This script pushes a ``release-note-X.Y.Z`` branch to your ``apache/arrow-site`` fork. You need to open a pull request from the ``release-note-X.Y.Z`` branch on your Web browser.
-.. dropdown:: Uploading binary release artifacts to Artifactory
+.. dropdown:: Update Homebrew packages
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- A PMC member must upload the binary release artifacts to Artifactory:
+ Open a pull request to Homebrew:
- .. code-block::
-
- # dev/release/post-02-binary.sh 0.1.0 0
- dev/release/post-02-binary.sh <version> <rc number>
+ .. code-block:: Bash
+
+ ## You need to run this on macOS that Homebrew is installed.
+
+ ## Fork https://github.com/Homebrew/homebrew-core on GitHub.
+ ## You need to do this only once.
+ ##
+ ## Prepare your fork of https://github.com/Homebrew/homebrew-core .
+ ## You need to do this only once.
+ cd "$(brew --repository homebrew/core)"
+ # git remote add kou git@github.com:kou/homebrew-core.git
+ git remote add <YOUR_GITHUB_ID> git@github.com:<YOUR_GITHUB_ID>/homebrew-core.git
+ cd -
-.. dropdown:: Announcing release
+ # dev/release/post-13-homebrew.sh 10.0.0 kou
+ dev/release/post-13-homebrew.sh X.Y.Z <YOUR_GITHUB_ID>
+
+ This script pushes a ``apache-arrow-X.Y.Z`` branch to your ``Homebrew/homebrew-core`` fork. You need to create a pull request from the ``apache-arrow-X.Y.Z`` branch with ``apache-arrow, apache-arrow-glib: X.Y.Z`` title on your Web browser.
+
+.. dropdown:: Update MSYS2 packages
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- Add relevant release data for Arrow to `Apache reporter <https://reporter.apache.org/addrelease.html?arrow>`_.
+ Open a pull request to MSYS2:
+
+ .. code-block:: Bash
+
+ ## Fork https://github.com/msys2/MINGW-packages on GitHub.
+ ## You need to do this only once.
+ ##
+ ## Prepare your fork of https://github.com/msys2/MINGW-packages .
+ ## You need to do this only once.
+ # git clone git@github.com:kou/MINGW-packages.git ../
+ git clone git@github.com:<YOUR_GITHUB_ID>/MINGW-packages.git ../
+ cd ../MINGW-packages
+ ## Add https://github.com/msys2/MINGW-packages.git as "upstream" remote.
+ git remote add upstream https://github.com/msys2/MINGW-packages.git
+ cd -
- Write a release announcement (see `example <https://lists.apache.org/thread/6rkjwvyjjfodrxffllh66pcqnp729n3k>`_) and send to announce@apache.org and dev@arrow.apache.org.
+ # dev/release/post-12-msys2.sh 10.0.0 ../MINGW-packages
+ dev/release/post-12-msys2.sh X.Y.Z <YOUR_MINGW_PACAKGES_FORK>
- The announcement to announce@apache.org must be sent from your apache.org e-mail address to be accepted.
+ This script pushes a ``arrow-X.Y.Z`` branch to your ``msys2/MINGW-packages`` fork. You need to create a pull request from the ``arrow-X.Y.Z`` branch with ``arrow: Update to X.Y.Z`` title on your Web browser.
-.. dropdown:: Generating new API documentations and update the website
+.. dropdown:: Update RubyGems
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- The API documentation for C++, C Glib, Python, Java, and JavaScript can be generated via a Docker-based setup.
- To generate the API documentation run the following command:
+ You need an account on https://rubygems.org/ to release Ruby packages.
- .. code-block::
-
- # preferred to have a cuda capable device with a recent docker version to generate the cuda docs as well
- # if you don't have an nvidia GPU please ask for help on the mailing list
- dev/release/post-08-docs.sh <version>
-
- # without a cuda device it's still possible to generate the apidocs with the following archery command
- archery docker run -v "${ARROW_SITE_DIR}/docs:/build/docs" -e ARROW_DOCS_VERSION="${version}" ubuntu-docs
-
- Note, that on a case insensitive filesystem sphinx generate duplicate filenames, so there can be missing links on the documentation page. Please use a system (preferably Linux) to execute the command above.
+ If you have an account on https://rubygems.org/ , you need to join owners of the following gems:
+
+ - red-arrow gem
+ - red-arrow-cuda gem
+ - red-arrow-dataset gem
+ - red-arrow-flight gem
+ - red-arrow-flight-sql gem
+ - red-gandiva gem
+ - red-parquet gem
+ - red-plasma gem
+
+ Existing owners can add a new account to the owners of them by the following command lines:
+
+ .. code-block:: Bash
+
+ gem owner red-arrow -a NEW_ACCOUNT
+ gem owner red-arrow-cuda -a NEW_ACCOUNT
+ gem owner red-arrow-dataset -a NEW_ACCOUNT
+ gem owner red-arrow-flight -a NEW_ACCOUNT
+ gem owner red-arrow-flight-sql -a NEW_ACCOUNT
+ gem owner red-gandiva -a NEW_ACCOUNT
+ gem owner red-parquet -a NEW_ACCOUNT
+ gem owner red-plasma -a NEW_ACCOUNT
+
+ Update RubyGems after Homebrew packages and MSYS2 packages are updated:
+
+ .. code-block:: Bash
+
+ # dev/release/post-04-ruby.sh 10.0.0
+ dev/release/post-04-ruby.sh X.Y.Z
+
+.. dropdown:: Update JavaScript packages
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ In order to publish the binary build to npm, you will need to get access to the project by asking one of the current collaborators listed at https://www.npmjs.com/package/apache-arrow packages.
+
+ When you have access, you can publish releases to npm by running the ``npm-release.sh`` script inside the JavaScript source release:
+
+ .. code-block:: Bash
+
+ # Login to npmjs.com (You need to do this only for the first time)
+ npm login --registry=https://registry.yarnpkg.com/
+
+ # dev/release/post-05-js.sh 10.0.0
+ dev/release/post-05-js.sh X.Y.Z
+
+.. dropdown:: Update C# packages
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ You need an account on https://www.nuget.org/. You need to join owners of Apache.Arrow package. Existing owners can invite you to the owners at https://www.nuget.org/packages/Apache.Arrow/Manage .
+
+ You need to create an API key at https://www.nuget.org/account/apikeys to upload from command line.
+
+ Install the latest .NET Core SDK from https://dotnet.microsoft.com/download .
+
+ .. code-block:: Bash
+
+ # NUGET_API_KEY=YOUR_NUGET_API_KEY dev/release/post-06-csharp.sh 10.0.0
+ NUGET_API_KEY=<your NuGet API key> dev/release/post-06-csharp.sh X.Y.Z
+
+.. dropdown:: Upload wheels/sdist to PyPI
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ pip binary packages (called "wheels") and source package (called "sdist") are built using the crossbow tool that we used above during the release candidate creation process and then uploaded to PyPI (Python Package Index) under the pyarrow package.
+
+ We use the twine tool to upload wheels to PyPI:
+
+ .. code-block:: Bash
+
+ # dev/release/post-09-python.sh 10.0.0 0
+ dev/release/post-09-python.sh <version> <rc number>
+
+.. dropdown:: Publish Maven packages
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ - Logon to the Apache repository: https://repository.apache.org/#stagingRepositories
+ - Select the Arrow staging repository you created for RC: ``orgapachearrow-XXXX``
+ - Click the ``release`` button
+
+.. dropdown:: Update R packages
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ TODO: Move from https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-UpdatingRpackages
+
+.. dropdown:: Update vcpkg port
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ Open a pull request to vcpkg:
+
+ .. code-block:: Bash
+
+ ## Fork https://github.com/microsoft/vcpkg on GitHub.
+ ## You need to do this only once.
+ ##
+ ## Prepare your fork of https://github.com/microsoft/vcpkg .
+ ## You need to do this only once.
+ # git clone git@github.com:kou/vcpkg.git ../
+ git clone git@github.com:<YOUR_GITHUB_ID>/vcpkg.git ../
+ cd ../vcpkg
+ ./bootstrap-vcpkg.sh
+ ## Add https://github.com/microsoft/vcpkg.git as "upstream" remote.
+ git remote add upstream https://github.com/microsoft/vcpkg.git
+ cd -
+
+ # dev/release/post-14-vcpkg.sh 10.0.0 ../vcpkg
+ dev/release/post-14-vcpkg.sh X.Y.Z <YOUR_VCPKG_FORK>
+
+ This script pushes a ``arrow-X.Y.Z`` branch to your ``microsoft/vcpkg`` fork. You need to create a pull request from the ``arrow-X.Y.Z`` branch with ``[arrow] Update to X.Y.Z`` title on your Web browser.
+
+.. dropdown:: Update Conan port
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ TODO
+
+.. dropdown:: Bump versions
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ .. code-block:: Bash
+
+ # dev/release/post-11-bump-versions.sh 10.0.0 11.0.0
+ dev/release/post-11-bump-versions.sh X.Y.Z NEXT_X.NEXT_Y.NEXT_Z
+
+.. dropdown:: Update tags for Go modules
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ .. code-block:: Bash
+
+ # dev/release/post-10-go.sh 10.0.0
+ dev/release/post-10-go.sh X.Y.Z
+
+.. dropdown:: Update docs
+ :animate: fade-in-slide-down
+ :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:
Review Comment:
OK. Fixed them.
##########
docs/source/developers/release.rst:
##########
@@ -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
#. Update Homebrew packages
#. Update MSYS2 package
#. Upload RubyGems
-#. Upload JS packages
+#. Upload JavaScript packages
#. Upload C# packages
#. Update conda recipes
#. Upload wheels/sdist to pypi
#. Publish Maven artifacts
#. Update R packages
#. Update vcpkg port
+#. Update Conan recipe
#. Bump versions
#. Update tags for Go modules
#. Update docs
+#. Announce the new release
#. Remove old artifacts
-.. dropdown:: Marking the released version as "RELEASED" on JIRA
+.. dropdown:: Mark the released version as "RELEASED" on JIRA
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ - Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ - Click "..." for the release version in "Actions" column
+ - Select "Release"
+ - Set "Release date"
+ - Click "Release" button
- Click "..." for the release version in "Actions" column
+.. dropdown:: Start the new version on JIRA
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
+
+ - Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ - Click "..." for the next version in "Actions" column
+ - Select "Edit"
+ - Set "Start date"
+ - Click "Save" button
+
+.. dropdown:: Merge changes on release branch to maintenance branch for patch releases
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
- Select "Release"
+ Merge ``release-X.Y.Z-rcN`` to ``maint-X.Y.Z``:
- Set "Release date"
+ .. code-block:: Bash
- Click "Release" button
+ # git checkout maint-10.0.0
+ git checkout maint-X.Y.Z
+ # git merge release-10.0.0-rc0
+ git merge release-X.Y.Z-rcN
+ # git push -u apache maint-10.0.0
+ git push -u apache maint-X.Y.Z
-.. dropdown:: Starting the new version on JIRA
+.. dropdown:: Add the new release to the Apache Reporter System
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- Open https://issues.apache.org/jira/plugins/servlet/project-config/ARROW/administer-versions
+ Add relevant release data for Arrow to `Apache reporter <https://reporter.apache.org/addrelease.html?arrow>`_.
- Click "..." for the next version in "Actions" column
+.. dropdown:: Upload source release artifacts to Subversion
+ :animate: fade-in-slide-down
+ :class-title: sd-fs-5
+ :class-container: sd-shadow-md
- Select "Edit"
+ A PMC member must commit the source release artifacts to Subversion:
- Set "Start date"
+ .. code-block:: Bash
- Click "Save" button
+ # dev/release/post-01-upload.sh 0.1.0 0
+ dev/release/post-01-upload.sh <version> <rc>
-.. dropdown:: Updating the Arrow website
+.. dropdown:: Upload binary release artifacts to Artifactory
: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:
- Generate the release note:
+ .. code-block:: Bash
- .. code-block::
-
- # dev/release/post-03-website 0.13.0 0.14.0
- dev/release/post-03-website <previous-version> <version>
-
- Create a pull-request and a Jira with the links the script shows at the end.
+ # dev/release/post-02-binary.sh 0.1.0 0
+ dev/release/post-02-binary.sh <version> <rc number>
-.. dropdown:: Uploading source release artifacts to SVN
+.. dropdown:: Update website
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- A PMC member must commit the source release artifacts to SVN:
+ Add a release note for the new version to our website and update the latest release information:
- .. code-block::
-
- # dev/release/post-01-upload.sh 0.1.0 0
- dev/release/post-01-upload.sh <version> <rc>
+ .. code-block:: Bash
+
+ ## Prepare your fork of https://github.com/apache/arrow-site .
+ ## You need to do this only once.
+ # git clone git@github.com:kou/arrow-site.git ../
+ git clone git@github.com:<YOUR_GITHUB_ID>/arrow-site.git ../
+ cd ../arrow-site
+ ## Add git@github.com:apache/arrow-site.git as "apache" remote.
+ git remote add apache git@github.com:apache/arrow-site.git
+ cd -
+
+ ## Generate a release note for the new version, update the
+ ## latest release information automatically.
+ # dev/release/post-03-website.sh 9.0.0 10.0.0
+ dev/release/post-03-website.sh OLD_X.OLD_Y.OLD_Z X.Y.Z
+
+ This script pushes a ``release-note-X.Y.Z`` branch to your ``apache/arrow-site`` fork. You need to open a pull request from the ``release-note-X.Y.Z`` branch on your Web browser.
-.. dropdown:: Uploading binary release artifacts to Artifactory
+.. dropdown:: Update Homebrew packages
:animate: fade-in-slide-down
:class-title: sd-fs-5
:class-container: sd-shadow-md
- A PMC member must upload the binary release artifacts to Artifactory:
+ Open a pull request to Homebrew:
- .. code-block::
-
- # dev/release/post-02-binary.sh 0.1.0 0
- dev/release/post-02-binary.sh <version> <rc number>
+ .. code-block:: Bash
+
+ ## You need to run this on macOS that Homebrew is installed.
Review Comment:
Really!? I didn't know that!
I've added "or Linux".
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org