Clarify release voting process details and allow concurrent votes by tisonkun · Pull Request #145 · apache/incubator

tisonkun · 2026-09-03T13:05:19Z

... request for comment.

Mailing list discussion: https://lists.apache.org/thread/1jjbb1yjqngc87g9ocwwnsgbrn93x0xb

…t votes

dave2wave

If the IPMC wants to allow for expedited votes then that needs to be described and must use the private @ mailing lists.

The Board has asked to be informed about use of expedited releases

tisonkun · 2026-09-03T15:08:16Z

If the IPMC wants to allow for expedited votes then that needs to be described and must use the private @ mailing lists.

I think "expedited votes" is another topic, and I'd exclude it from this discussion thread. We can have another thread focusing on expedited votes in the Incubator.

justinmclean · 2026-09-03T16:09:47Z

Closing at the IPMC would need to vote on any changes to policy.

tisonkun · 2026-09-03T16:12:20Z

Closing at the IPMC would need to vote on any changes to policy.

I'd keep it open for a squashed view for a final word that is easy to review.

Would keep it as a draft.

Otherwise it's nothing different from copying the whole content back to the mailing list, and this PR is just similar to a cwiki page.

The IPMC vote would run on an immutable statement that is finalized on the list.

Co-authored-by: tison <wander4096@gmail.com>

justinmclean · 2026-09-04T00:43:25Z


-Podlings are not yet fully accepted as official projects within the Apache Software Foundation. Podlings MUST NOT perform any ASF releases of software without the approval of the Incubator PMC. When a Podling decides it wants to make an ASF release, the Podling MUST hold a vote on their public dev list. At least three +1 PPMC votes are required (see the http://www.apache.org/foundation/voting.html[Apache Voting Process] page) and more +1 votes than -1 votes. If the vote passes, the Podling MUST send a summary of that vote to the Incubator's link:/howtoparticipate.html#Mailing+lists[general] list and request that the Incubator PMC approve the release. Three +1 Incubator PMC votes are required to approve a release. Below is an example showing how an incubating project managed this process:
+During incubation, PPMC members learn how to govern an ASF project. A PPMC operates like a PMC but reports to the Incubator PMC rather than to the ASF Board. The PPMC release vote ensures that the Podling community participates in producing and reviewing ASF releases. Because the PPMC cannot make formal decisions on behalf of the ASF, the Incubator PMC provides the binding approval required for a Podling release to become an ASF release.



"Podlings MUST NOT perform any ASF releases of software without the approval of the Incubator PMC" needs to stay

Try to resolve with https://github.com/apache/incubator/pull/145/changes#r3929964934.

tisonkun · 2026-09-04T00:53:59Z

 link:/guides/releasemanagement.html#requesting_feedback_on_interim_non_asf_releases[non-ASF releases] while incubating as long as it is moving towards making ASF releases.

-Podlings are not yet fully accepted as official projects within the Apache Software Foundation. Podlings MUST NOT perform any ASF releases of software without the approval of the Incubator PMC. When a Podling decides it wants to make an ASF release, the Podling MUST hold a vote on their public dev list. At least three +1 PPMC votes are required (see the http://www.apache.org/foundation/voting.html[Apache Voting Process] page) and more +1 votes than -1 votes. If the vote passes, the Podling MUST send a summary of that vote to the Incubator's link:/howtoparticipate.html#Mailing+lists[general] list and request that the Incubator PMC approve the release. Three +1 Incubator PMC votes are required to approve a release. Below is an example showing how an incubating project managed this process:
+During incubation, PPMC members learn how to govern an ASF project. A PPMC operates like a PMC but reports to the Incubator PMC rather than to the ASF Board. The PPMC release vote ensures that the Podling community participates in producing and reviewing ASF releases. Because the PPMC cannot make formal decisions on behalf of the ASF, the Incubator PMC provides the binding approval required for a Podling release to become an ASF release.


Suggested change

During incubation, PPMC members learn how to govern an ASF project. A PPMC operates like a PMC but reports to the Incubator PMC rather than to the ASF Board. The PPMC release vote ensures that the Podling community participates in producing and reviewing ASF releases. Because the PPMC cannot make formal decisions on behalf of the ASF, the Incubator PMC provides the binding approval required for a Podling release to become an ASF release.

During incubation, PPMC members learn how to govern an ASF project. A PPMC operates like a PMC but reports to the Incubator PMC rather than to the ASF Board. The PPMC release vote ensures that the Podling community participates in producing and reviewing ASF releases. Podlings MUST NOT perform any ASF releases of software without the approval of the Incubator PMC. Because the PPMC cannot make formal decisions on behalf of the ASF, the Incubator PMC provides the binding approval required for a Podling release to become an ASF release.

Clarify release voting process details and explicitly allow concurren…

a8292c8

…t votes

dave2wave reviewed Sep 3, 2026

View reviewed changes