This is an automated email from the ASF dual-hosted git repository. brycemecum pushed a commit to branch feature/GH-45140--release-guide-improvements in repository https://gitbox.apache.org/repos/asf/arrow.git
commit 5f385a9b6f43c35234a7f1705fe4f2bbdb21144b Author: Bryce Mecum <[email protected]> AuthorDate: Tue Dec 31 11:44:34 2024 -0800 Add steps for the release blog post --- docs/source/developers/release.rst | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/docs/source/developers/release.rst b/docs/source/developers/release.rst index 1a5cf36091..deb1ed005d 100644 --- a/docs/source/developers/release.rst +++ b/docs/source/developers/release.rst @@ -669,7 +669,25 @@ Be sure to go through on the following checklist: :class-title: sd-fs-5 :class-container: sd-shadow-md - TODO + The blog post process isn't automated. The rough set of steps we usually take + are: + + * Clone https://github.com/apache/arrow-site. + * Create a new branch off ``main`` for the blog post pull request we're + creating. + * Duplicate a recent blog post entry in the ``_posts`` subfolder and update + the filename and YAML metadata. + + * Set the date in the filename and in the YAML metadata to the date that the + release candidate vote thread for the release closed. + + * *For minor releases only*, remove any section about community updates (new + committers, PMC members, etc). + * Update the remainder of the text as needed + * Create the pull request + * In the pull request, ping contributors in each section requesting help + filling in the details for each section. + .. dropdown:: Announce the release on Twitter :animate: fade-in-slide-down
