Hi tison, For TLPs, there is already a process for an expedited release [1], which I believe can also be used for podlings. This could help reduce the duration of the vote when there is a genuine need to get a release out quickly. I believe FastTrack should be reserved for genuinely critical cases. Otherwise, 72 × 2 hours = 6 days does not seem excessively long for getting a release out after an RC. In fact, many projects generally run their release votes for around a week.
I am also not entirely in favour of the proposal where, once the PPMC has three +1 votes on dev@, the release can proceed with only a notice to general@. Instead, in such extraordinary circumstances, perhaps the vote could be run concurrently on both dev@ and general@. This would still allow everyone who is entitled to vote to participate, while reducing the overall time required. That said, I would still prefer this mechanism to be limited to exceptional circumstances where an expedited release is actually warranted, similar to the existing expedited release process for TLPs. -Ayush [1] https://www.apache.org/legal/release-policy.html#expedited-releases On Thu, 3 Sept 2026 at 10:53, tison <[email protected]> wrote: > > Hi, > > Currently, for a typical podling release, one should go through a PPMC > vote + an IPMC vote, both with a minimum of a 72-hour period [1][2]. > > [1] https://www.apache.org/legal/release-policy.html#release-approval > [2] https://incubator.apache.org/policy/incubation.html#releases > > IIRC, there are several discussions about release velocity. Here, I'd > like to propose a concrete fast path for an IPMC vote to reduce the > reputation of "the ASF (Incubator) will slow your project." > > That is, if the PPMC votes already have 3 +1 votes from IPMC members, > with a notice to [email protected] for further (post) review, a > podling can conclude the release. > > I'd like to hear your feedback. Or perhaps a podling that keeps > releasing and evolving well should just consider graduating from the > Incubator. > > 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]
