> On Sep 7, 2026, at 4:37 PM, tison <[email protected]> wrote: > >> IPMC vote (release) SHOULD still follow the release policy defined in > > As this uses the uppercase form, it is a MUST. > > Best, > tison. > > tison <[email protected]> 于2026年9月8日周二 07:30写道: >> >> Hi PJ, >> >> I recorded your vote. >> >> To keep the vote thread focused and keep this specific idea discussion >> focused, I am starting a new thread. >> >> Let's see how we can improve the license/release verification method. >> >> Comment inline. >> >>> -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. >> >> Technically speaking, the concurrent PPMC and IPMC vote is not an >> expedited release as defined in [1]. It is still a formal and normal >> vote by either the PPMC or the IPMC.
Incubator podlings simply have no policy route to an “Expedited Release”. None, allowing that would be a new discussion. Expedited Releases must occur on private@ and require informing the board afterwards. If we need a name then how is “Compressed Release”? >> >> [1] https://www.apache.org/legal/release-policy.html#expedited-releases >> >>> 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. >> >> I totally agree that we can extend the release criteria to help >> podlings make better releases. This item, IMO, can also apply to TLPs. >> >> Actually, the Incubator defines release guidelines in [2], and the >> IPMC vote (release) SHOULD still follow the release policy defined in >> [3], which states: >> >>> Every ASF release MUST comply with ASF licensing policy. This requirement >>> is of utmost importance and an audit SHOULD be performed before any full >>> release is created. In particular, every artifact distributed MUST contain >>> only appropriately licensed code per Apache Licensing Policy [4]. I would like to discuss how we can make release candidates and the critical checks more like a periodic step done during development to track progress towards the next release. I’ve been thinking about this with respect to ATR and would like to chat about this during CoC in Glasgow. >> >> [2] https://incubator.apache.org/policy/incubation.html#releases >> [3] https://www.apache.org/legal/release-policy.html#licensing >> [4] https://www.apache.org/legal/resolved >> >> So I think it is actually included. The wording could be improved, and >> proposals are welcome. >> >> But I can try to understand your concerns and consider whether we have >> better methods to validate source licenses. So far, RAT can do >> something but it would miss others that are not mechanically wrong. >> ScanOSS can do some other things but it can still hardly replace human >> checks. >> >> What are human checks? They are defined as PPMC/IPMC votes cast on the >> voting thread. The checks on releases on ATR include more than the standard ones. We do check for binaries in source artifacts for example and what rat excludes you have or concerns you get are available. Perhaps we are closer to giving humans the best information about where to look. Tooling has a workshop on ATR scheduled for the conference. >> >> So technically, even if we repeat the requirement in the guidelines, >> it doesn't change the practices. >> >> The significant part is to enable and help PPMC/IPMC members verify >> source licenses more effectively. And I find that the current AI agent >> can reduce the workload (but you should not outsource the work). >> >> My prompt is in Chinese, but it's as simple as asking the agent to >> verify all the sources by following our policy, and it would search >> the Internet to find similar sources. You can even ask for a lower >> false-negative output in trade-off for a higher false-positive rate, >> since false positives can be resolved by RM's answers without >> canceling the vote. As examples, some recent -1 votes [5][6] are >> spotted with the help of an agent. >> >> [5] https://lists.apache.org/thread/bwr06m0mczd69tnq7h9opm1hnwhn4o9h >> [6] https://lists.apache.org/thread/8tg6lwh154f5fxvjjkrpdlnxd9l9n37y >> >> If you have other good practices or methods, feel free to share. >> >> Our goal should be to help podlings release better, and waiting a few >> more hours doesn't magically achieve that. Finally, we need a >> combination of better methods and better education so that (P)PMC can >> follow the policy more proactively and more easily. >> >>> Convenience Binaries and their licenses/notices are not always considered. >> >> I'm not sure what you want to emphasize here. Could you elaborate a bit? Best, Dave >> >> 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]
