Release Arrow 22.0.0 (next release after 21.0.0)

[alamb]

Follow on from #2382

• Planned Release Candidate: 2022-09-02
• Planned Release and Publish to crates.io: 2022-09-05

Items (from dev/release/README.md):

• PR to update version and CHANGELOG: Update version to 22.0.0 and update CHANGELOG #2612
• Release candidate created: https://lists.apache.org/thread/mlj3bn8bvdlq25gq2glrto3018jgt3zk
• Release candidate approved: https://lists.apache.org/thread/lzct69wrnjv9fvrp2x1xy5o3lg2p3kzl
• Release to crates.io
• Draft update to DataFusion: Upgrade to arrow 22 datafusion#3363

See full list here:
21.0.0...master

[alamb]

@iajoiner here is ticket. The instructions are here: https://github.com/apache/arrow-rs/blob/master/dev/release/README.md

Basically a PMC member such as myself, @nevi-me etc needs to run the scripts to upload to svn and crates.io but all the other steps (the version and changelog specifically) can be done by anyone. If someone could help make the changelog and then pushing the updates through to datafusion that is what takes most of my time

However, the update of the changelog is largely done by modifying the descriptions / tags on various github issues, which if I recall can only be done by committers (e.g. @liukun4515 or @tustvold )

[liukun4515]

@iajoiner here is ticket. The instructions are here: https://github.com/apache/arrow-rs/blob/master/dev/release/README.md

Basically a PMC member such as myself, @nevi-me etc needs to run the scripts to upload to svn and crates.io but all the other steps (the version and changelog specifically) can be done by anyone. If someone could help make the changelog and then pushing the updates through to datafusion that is what takes most of my time

However, the update of the changelog is largely done by modifying the descriptions / tags on various github issues, which if I recall can only be done by committers (e.g. @liukun4515 or @tustvold )

Is there automation script to generate the changelog from the commit information or github information?
I didn't do that before, but I am happy to do something with you and reduce the work of you for each release.

@alamb

[alamb]

Hi @liukun4515 -- sorry for the late reply. There is a script to create the changelog from github -- ./dev/release/update_change_log.sh

The instructions for use are described in https://github.com/apache/arrow-rs/blob/master/dev/release/README.md#prepare-changelog-and-version

[liukun4515]

Hi @liukun4515 -- sorry for the late reply. There is a script to create the changelog from github -- ./dev/release/update_change_log.sh

The instructions for use are described in https://github.com/apache/arrow-rs/blob/master/dev/release/README.md#prepare-changelog-and-version

No worries, I can help to do this for the next release.

[iajoiner]

@liukun4515 Really thanks! However this is actually unnecessary. I managed to generate the change log using my credentials.

[alamb]

I plan to cut the release candidate in a few hours. I need to do some other things now

[wangfenjin]

Do we plan to release version 22.0.0 today?

[alamb]

Do we plan to release version 22.0.0 today?

@wangfenjin I do plan to release 22.0.0 today -- However, I need to wait another 8 hours or so for the 72 hour voting window to expire (see link to mailing list post above).

I will try and release shortly after the window has expired, assuming there are no issues found, but depending on my schedule it may take a few more hours

[alamb]

Released!