Hi, While the voting page uses the word “generally”, in ASF practice, release votes are expected to run for at least 72 hours so that contributors in all time zones have the opportunity to review the artifacts and provide feedback.
Closing the vote early because the required binding votes have been reached is not normally how release votes are handled. Exceptions are rare and typically announced when the vote starts; that was not done in this case. It may also come as a surprise to the wider community that the vote has already closed, which has not given them the opportunity to review the release or raise any concerns. The release policy says: “Release votes SHOULD remain open for at least 72 hours. See the next Expedited Releases section when considering a reduced voting period.” That section [1] clarifies when this applies: Emails calling for a release vote that run less than 72 hours MUST include an explanation. Note also that “SHOULD” here is used as defined in RFC 2119 [2], meaning that deviations are possible only when there are valid reasons, and the implications have been carefully considered. I suggest the project wait for the full 72 hours before proceeding with the release, and take into account any other feedback received. Kind Regards, Justin 1. https://www.apache.org/legal/release-policy.html#expedited-releases 2. https://www.rfc-editor.org/rfc/rfc2119
