On Mon, Sep 7, 2026 at 7:05 PM Dave Fisher <[email protected]> wrote:
>...

> 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”?
>

Maybe call it an "Incubator-Approved Release"? We're talking about the IPMC
(the formal PMC constructed per the Bylaws) approving a release. What more
needs to be done?

Historically, anybody can make a release once they get (3) +1 votes on that
release. I see no reason to treat the IPMC any differently from the other
200 PMCs at the Foundation, just because the repository being released has
been labeled as a "podling". The Foundation does not recognize that
construct in its Bylaws, nor any Resolutions I'm aware of, which formalize
the podling concept as an independent entity.

I believe Tison is correct here, in saying that (3) IPMC Members may vote
for a podling release to be made, before waiting for a PPMC vote.

Not sure on the name. As all releases are "Incubator-Approved".
"Compressed" seems fine, but doesn't quite land properly. It also sounds
like the "faster than 72h" rule or somesuch. "Overlapped Approval" or
something? Blue-skying.

So needless to say, I asked Grok. It provided a great naming and policy
guidance:

--

Keep the release name ordinary (Apache Foo 1.2.3). Name the *procedure*:

A release vote may close as *passed by concurrence* when the first-stage
thread has both (a) a passing first-body tally and (b) at least three
binding +1 votes from the second body. In that case the second-stage vote
is not opened.

RESULT subject:

[RESULT][VOTE] Release Apache Foo 1.2.3-rc2 — passed by concurrence

Body line:

Binding second-body votes on this thread: John, Jane, Tom. Second-stage
vote waived.

--

>...

Cheers,
-g

Reply via email to