Thanks for your feedback and further discussion. I'll start the vote on Monday. You can find the current draft at [1].
[1] https://github.com/apache/incubator/pull/145 When voting, an immutable version will be finalized. [CURRENT VERSION; for changing the release guideline] 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. 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]. [END] Best, tison. Justin Mclean <[email protected]> 于2026年9月5日周六 09:45写道： > Hi, > > > Have you asked your LLM to compare graduation timelines? BTW - > archives.apache.org has stored find output > > that provides a full history of releases. It would interesting to > compare historical release cadence with time in incubation. Some of the > early podlings graduated in less than 6 months. > > This has already been analyzed. Look at the wiki [1] - graduation medians > were 20 to 42 months, but are now 13 to 18 months. Incubation is faster now > for healthy podlings, not slower. Time to make a first release has dropped > from 6 to 7 months to 4 to 5 months, and issues found in release votes have > declined sharply over the last decade. > > Only a handful of incubating projects have graduated in under 6 months; > you can see the data in podlings.xml. By my count, it is 7 from 318 > podlings, or 2% of them. And if you look, it seems most were > long-established open-source communities, e.g., Subversion. > > Kind regards, > Justin > > 1. > https://cwiki.apache.org/confluence/spaces/INCUBATOR/pages/399279029/10+years+of+the+Incubator > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
