[Release] 21.0.0 post release tasks

[kou]

Describe the enhancement requested

The vote thread: https://lists.apache.org/thread/0k08fmzonyj00rtwt63fpt9c8hkkcyg9

https://arrow.apache.org/docs/developers/release.html#post-release-tasks

• Update the released milestone Date and set to "Closed" on GitHub
• Merge changes on release branch to maintenance branch for patch releases
• Add the new release to the Apache Reporter System
• Push release tag
• Upload source
• Upload binaries
• Update website
• Update GitHub Release Notes
• Update Homebrew packages
  • apache-arrow apache-arrow-glib 21.0.0 Homebrew/homebrew-core#230431
• Update MSYS2 package
  • arrow python-pyarrow: update to 21.0.0 msys2/MINGW-packages#24879
• Upload RubyGems
• Upload JavaScript packages
• Upload C# packages
• Update conda recipes
  • libarrow: arrow-cpp v21.0.0 conda-forge/arrow-cpp-feedstock#1819
  • pyarrow: pyarrow v21.0.0 conda-forge/pyarrow-feedstock#155
• Upload wheels/sdist to pypi
• Update R packages
  • [R][Release] CRAN packaging checklist for version 21.0.0 #46950
• Update vcpkg port
  • [arrow] Update to 21.0.0 microsoft/vcpkg#46477
• Update Conan recipe
  • arrow: add version 21.0.0 conan-io/conan-center-index#27949
• Bump versions
• Update docs
  • Release docs 21.0.0 arrow-site#676
• Update version in Apache Arrow Cookbook
  • MINOR: [Release][C++][Python] Update versions for 21.0.0 arrow-cookbook#380
  • Blocked on [R] Stable cookbook build failing on reticulate arrow-cookbook#381
• Announce the new release
• Publish release blog posts
  • [Website] Add blog post for Arrow 21.0.0 arrow-site#668
• Announce the release on BlueSky / LinkedIn
• Remove old artifacts

Post-post-release tasks:

• [Release] Update Release Management Guide to reflect changes in 21.0.0 #47058

Component(s)

Release

[AlenkaF]

I will run the docs update. If I am not mistaken, I should wait for the versions to be bumped first?

[amoeba]

Hey @AlenkaF, I'm not sure it's strictly required but I did misspeak yesterday: I think it's best to hold off on the docs update until packages are available, most importantly PyPi and conda-forge. I think you can start testing the docs by running them with PUSH=0, like PUSH=0 post-09-docs.sh.

[amoeba]

Thanks for starting this @kou, I was just about to do the same! I can start on the various packaging PRs later today and I've updated your post to include links to in-progress issues and PRs.

[kou]

Thanks!

[AlenkaF]

Thanks for the info @amoeba, will do!

[lscheilling]

Noticed that the new pypi release dropped old glibc support making unable to uninstall on older linux machines (specifically Amazon Linux 2 in this case), is this a bug or planned behaviour?

[fvalenduc]

I tried to install the arrow package with devtools using the apache-arrow-21.0.0 tag and it failed like this:
** testing if installed package can be loaded from temporary location
Error: le chargement du package ou de l'espace de noms a échoué pour ‘arrow’ in dyn.load(file, DLLpath = DLLpath, ...) :
impossible de charger l'objet partagé '/usr/lib64/R/library/00LOCK-arrow/00new/arrow/libs/arrow.so' :
/usr/lib64/R/library/00LOCK-arrow/00new/arrow/libs/arrow.so: undefined symbol: _ZN5arrow7compute10InitializeEv

[kou]

@lscheilling Could you open a new issue for it? FYI: #46959 is the related issue for it.

[kou]

@fvalenduc Could you open a new issue for it? You may need to wait for the R package release. #46950 is the related issue for it.

[amoeba]

Hi @AlenkaF, I think you can create the PR to update the docs whenever you're ready to start testing.

[amoeba]

@raulcd do you want to post the release to BlueSky and LinkedIn? I just merged the blog post and announced the release today.

[raulcd]

BlueSky:

• https://bsky.app/profile/arrow.apache.org/post/3lujz5aaq5c2t

LinkedIn:

• https://www.linkedin.com/posts/apache-arrow_apache-arrow-2100-release-activity-7353330092636303362-wqhC/