I was just looking at the voting rules, and specifically the rules for package 
releases:

===
Votes on whether a package is ready to release use majority approval 
<https://www.apache.org/foundation/glossary.html#MajorityApproval>, i.e., at 
least three PMC members must vote affirmatively for release, and there must be 
more positive than negative binding votes. Releases may not be vetoed. 
Generally the community will cancel the release vote if anyone identifies 
serious problems, but in most cases the ultimate decision lies with the 
individual serving as release manager. The specifics of the process may vary 
from project to project, but the 'minimum quorum of three +1 votes' rule is 
universal.

Note that there is no implicit +1 from the release manager, or from anyone in 
any ASF vote. Only explicit votes are valid. The release manager is encouraged 
to vote on releases, like any reviewer would do.

===

The way I read this is that the release manager (Dongjoon in this case) made 
the ultimate decision to move on with the release, taking on the responsibility 
that comes with this decision.

I am also quoting here the official phrasing regarding timelines:

===
Voting periods should generally run for at least 72 hours to provide an 
opportunity for all concerned persons to participate, regardless of their 
geographic location.
===


Although technically not mandated by the rules, I think it would be good 
practice to consider the 72 hours as weekday hours. The call for vote for RC3 
was sent on Dec 11th. This was a Thursday, or maybe even a Friday for some, 
given the time zone differences. The voting period included a Saturday and a 
Sunday, which reduces the possibility for members of the community to be able 
to react. I think it would be good practice (again not technically mandated by 
the rules), to send voting requests on Mondays or Tuesdays, in order to 
maximize the possibility of community involvement. The voting is after all 
about community involvement, and a means for the release manager to assess the 
situation and the readiness of the release based on the feedback during the 
voting period.

- Menelaos


> On Dec 17, 2025, at 2:50 AM, Dongjoon Hyun <[email protected]> wrote:
> 
> Thank you for sharing the rule with Herman, Sean.
> 
> BTW, there is no hurry here. May I ask why you think in that way (we are in 
> hurry)?
> 
> Apache Spark 4.1.0 has been prepared over 5 months with four previews and 
> three RCs. 4.1.0 RC3 vote passes based on the ASF policy. Like RC1 and RC2, I 
> stopped the vote with the valid reasons. I'm sure that I proceeded the RC 
> votes until I don't see any valid Apache Spark release blockers.
> 
> - v4.1.0-preview1 (7/8)
> - v4.1.0-preview2 (9/24)
> - v4.1.0-preview3 (10/27)
> - v4.1.0-preview4 (11/17, Release Manager: Dongjoon Hyun)
> - v4.1.0-rc1 (11/24, Release Manager: Dongjoon Hyun)
> - v4.1.0-rc2 (11/30, Release Manager: Dongjoon Hyun)
> - v4.1.0-rc3 (12/11, Release Manager: Dongjoon Hyun)
> - v4.1.0 (Now)
> 
> Thanks,
> Dongjoon
> 
> On 2025/12/16 14:03:34 Sean Owen wrote:
>> (Release vote criteria is "more +1 than -1", FWIW)
>> I also do not understand the hurry here. Just finish up the change and
>> re-roll a RC like we've done 100 times before.
>> What is the special circumstance for this RC to rush it?
>> 
>> On Tue, Dec 16, 2025 at 7:18 AM Herman van Hovell via dev <
>> [email protected]> wrote:
>> 
>>> Dongjoon,
>>> 
>>> I am not sure I follow. I have voted -1 on the release. I am a PMC member
>>> so that is a binding vote. Please cut a new RC and put it for another vote.
>>> 
>>> Kind regards,
>>> Herman
>>> 
>>> 
>>> On Tue, Dec 16, 2025 at 7:29 AM Dongjoon Hyun <[email protected]>
>>> wrote:
>>> 
>>>> The vote passes with 6 +1s (3 binding +1s).
>>>> Thanks to all who helped with the release!
>>>> 
>>>> (* = binding)
>>>> +1:
>>>> - Dongjoon Hyun *
>>>> - Peter Toth
>>>> - Kent Yao *
>>>> - Yang Jie *
>>>> - Jules Damji
>>>> - Scott
>>>> 
>>>> +0: None
>>>> 
>>>> -1: None
>>>> - Herman van Hovell
>>>> 
>>> 
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe e-mail: [email protected]
> 

Reply via email to