incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson" <>
Subject Re: [doc] podling software releases
Date Thu, 09 Feb 2006 19:58:57 GMT
Martin Sebor wrote:
> Jean T. Anderson wrote:
> [...]
>> it should be public vote, so on the public -dev list.  Here's a
>> suggested refinement:
>> "Therefore, should a Podling decide it wishes to perform a release, the
>> Podling SHALL hold a vote on the Podling's public -dev list and notify
>> the Podling's PPMC list that the vote has been called.
> Hmm. This is different from what stdcxx has been practicing (we
> never notified our PPMC since all PPMC members are committers and
> the active ones participate on -dev). What would be the purpose
> of this notification? OTOH, I could see that it might be important
> for a podling to notify a sponsoring TLP's PMC. My understanding
> is that only podlings on the TLP track have a PPMC and all others
> use their sponsoring TLP project's PMC. Isn't that correct?

Derby was sponsored by the Apache DB Project, but had its own PPMC, and
the PPMC decision was to include all Derby committers as a PPMC member.
 We never notified the DB Project of anything -- it simply didn't occur
to us. Then again, we also didn't explicitly notify the Derby PPMC that
I remember. :-) We fumbled a bit.

Derby actually did graduate into an Apache DB subproject, but it's worth
it to mention what Noel pointed out yesterday about the "final
destination will be determined at graduation" -- see .
(I'll try to keep this on my radar for docs.)

What's the best practice moving forward? If we nail down clear
guidelines, new projects will spend less time figuring things out and
more time building their communities.

>> At least three +1
>> votes are required (see guidelines at
>>, and only the PPMC member
>> votes are binding.
> IMO, the PPMC/committer question needs to be clarified. In fact,
> if my understanding about TLPs and PMC/PPMCs is correct, this
> could not be correct.

I think Ken covered this on a parallel thread.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message