-1 binding I would prefer that only podlings that have done a clean release in the past can take advantage of expedited releases. I'm not against some mechanism to support shorter release turnarounds but I can't support the current proposal.
Or the release checklist should be expanded to include items like whether the source licenses have been validated - current wording typically just asks that the LICENSE and NOTICE are in the release. Convenience Binaries and their licenses/notices are not always considered. On Mon, 7 Sept 2026 at 19:59, Jean-Baptiste Onofré <[email protected]> wrote: > > +1 (binding) > > Regards > JB > > On Mon, Sep 7, 2026 at 6:09 AM tison <[email protected]> wrote: > > > > Hi, > > > > Here is a vote to change the Incubator Guidelines on [1] to explicitly > > permit concurrent PPMC and IPMC votes for release. > > > > [1] https://incubator.apache.org/policy/incubation.html#releases > > > > The rendered version can be found at [2], of commit > > 56e442484462dcd16d3f3bdd75ecded0969cb719 [3] > > > > [2] https://github.com/apache/incubator/pull/145 > > [3] > > https://github.com/apache/incubator/blob/56e442484462dcd16d3f3bdd75ecded0969cb719/pages/policy/incubation.ad > > > > Please review the proposed content and vote accordingly. > > > > [ ] +1 Change the Incubator Guidelines as proposed > > [ ] +0 No opinion. > > [ ] -1 Do not approve. Please explain why. > > > > Below is a copy of the frozen version (trivial markers trimmed). > > > > [CONTENT START] > > > > Releases > > > > See the guidelines for Podling releases for good practices for making > > releases. The Podling can make non-ASF releases while incubating as long as > > it is moving towards making ASF releases. > > > > 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. > > > > When a Podling proposes an ASF release, it MUST hold a vote on its public > > dev list to seek endorsement from the PPMC and MUST request approval from > > the Incubator PMC on the Incubator's general list. The PPMC vote and the > > Incubator PMC vote MAY be conducted sequentially or, at the Podling's > > discretion, concurrently. The timing and conduct of the votes MUST follow > > the applicable requirements of the Apache Voting Process and the ASF > > Release Policy. > > > > The proposed release is approved only when both of the following > > requirements have been satisfied: > > > > - At least three PPMC members have voted +1, and there are more +1 than -1 > > votes from PPMC members. > > - At least three Incubator PMC members have cast binding +1 votes, and > > there are more binding +1 than binding -1 votes. > > > > Only votes from Incubator PMC members are binding for ASF release approval. > > > > Below are examples of the two kinds of release vote requests: > > > > - Post to the Podling dev list calling the PPMC vote. > > - Post to the Incubator's general list requesting approval from the > > Incubator PMC. > > > > Once both voting requirements have been satisfied, the Podling MAY make the > > release available to the public under these conditions: > > > > - The release archive(s) MUST include the word "incubating" in the filename. > > - The release archive(s) MUST contain a disclaimer (see above), which > > SHOULD be placed in a DISCLAIMER or DISCLAIMER-WIP file. > > > > Releases for the Podling MUST be distributed through > > http://www.apache.org/dist/incubator/Podling. The Podling MAY choose to > > distribute approved releases through other channels by following the link: > > https://incubator.apache.org/guides/distribution.html[guidelines here]. > > > > [CONTENT END] > > > > Best, > > tison. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
