That will significantly reduce release time and make the process less
error-prone.

Thank you Hyukjin!

On Thu, May 29, 2025 at 2:07 PM Dongjoon Hyun <dongjoon.h...@gmail.com>
wrote:

> Thank you, Hyujjin!
>
> It's really great.
>
> Dongjoon.
>
> On Thu, May 29, 2025 at 00:41 Hyukjin Kwon <gurwls...@apache.org> wrote:
>
>> Yup I'll write it down 👍
>>
>> On Thu, May 29, 2025 at 4:39 PM Jungtaek Lim <
>> kabhwan.opensou...@gmail.com> wrote:
>>
>>> Awesome work! I also can't see the screenshots. Maybe we'd need to have
>>> this in the release guide page in Apache Spark website anyway?
>>>
>>> On Thu, May 29, 2025 at 4:24 PM Yuanjian Li <xyliyuanj...@gmail.com>
>>> wrote:
>>>
>>>> Thanks, Hyukjin—this made the release 10 times easier (maybe even more)!
>>>>
>>>> (Not sure if it’s just me, but I can’t see the screenshot you sent.)
>>>>
>>>> Hyukjin Kwon <gurwls...@apache.org> 于2025年5月28日周三 23:34写道:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I would like to share that GitHub Actions workflow to release Apache
>>>>> Spark is now available.
>>>>> The workflow is in
>>>>> https://github.com/apache/spark/blob/master/.github/workflows/release.yml
>>>>> .
>>>>> Apache Spark 3.5.6 was the first release done by this GitHub Actions.
>>>>>
>>>>> I plan to make some more changes to make it easier, and document it in
>>>>> https://spark.apache.org/release-process.html but wanted to share it
>>>>> here first.
>>>>>
>>>>> Only PMC members can run this. In short, the steps are as follows:
>>>>>
>>>>> 1. You have to use your forked repository with the GitHub Actions
>>>>> Secrets set, see the comments in release.yml.
>>>>> 2. Then, you can run as follows to create an RC. Effectively same as:
>>>>>
>>>>> do-release-docker.sh -d ...
>>>>>
>>>>> [image: Screenshot 2025-05-29 at 3.25.26 PM.png]
>>>>>
>>>>> 3. After the vote on RC passes, you can convert this to the official
>>>>> release as below. Same as:
>>>>>
>>>>> do-release-docker.sh -d ... -s finalize
>>>>>
>>>>> [image: Screenshot 2025-05-29 at 3.25.32 PM.png]
>>>>>
>>>>> Thanks all!
>>>>>
>>>>>

Reply via email to