[GitHub] [arrow] kszucs edited a comment on pull request #9155: ARROW-6103: [Java] Remove mvn release plugin

[GitBox <gi...@apache.org>]

kszucs edited a comment on pull request #9155:
URL: https://github.com/apache/arrow/pull/9155#issuecomment-819632190


   Thanks Andy! Going to ask my questions in a separate comment.
   
   I updated the preparation script to automatically create the necessary branches and tag the release. 
   After the following commands: 
   
   ```console
   $ # create a release branch manually
   $ git checkout release-4.0.0
   $ # commit fixes required for the release
   $ git commit -m "[Release]: ..."
   $ git commit -m "[Release]: ..."
   $ # 01-prepare.sh <version> <next-version> <rc-number>
   $ 01-prepare.sh 4.0.0 5.0.0 0
   ```
   
   I have the following git history:
   
   ```console
   # post-tag commits bumping the versions to the new development version numbers
   54ed24c39 (HEAD -> release-4.0.0-rc0) [Release] Update .deb package names for 5.0.0
   4757d2d08 [Release] Update versions for 5.0.0-SNAPSHOT
   
   # pre-tag commits: changelog update and version bumps
   # the actual tag will point to the last version bump commit
   ab83815a1 (tag: apache-arrow-4.0.0) [Release] Update versions for 4.0.0
   ea248a9fe [Release] Update .deb/.rpm changelogs for 4.0.0
   e67ba60f1 [Release] Update CHANGELOG.md for 4.0.0
   
   # the head of the release branch where we can place release related patches without blocking the development on the master branch
   c3d27a899 (release-4.0.0) [Release] Fix a something else required for the release
   8671464f9 [Release] Fix a cmake error
   263365500 [Release] Fix a wheel packaging issue
   
   # this will be the HEAD of the master branch during the release
   b17a52751 (remove-mvn-release-plugin) Create the release branch explicitly before prepare 
   5960e4391 Force delete branch
   f559480e6 Don't remove the remote tracking branch
   6aca9078a Exit if RC branch already exists
   ```
   
   The `release-4.0.0` branch and `apache-arrow-4.0.0` tag can be pushed upstream. Once we have finished with the release, we can create a pull request from `release-4.0.0` branch and update the version numbers on master and add any supplemental patches which were required to cut the release.


-- 
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org