On Mon, Mar 14, 2011 at 09:33, ant elder <ant.el...@gmail.com> wrote: > On Mon, Mar 14, 2011 at 8:13 AM, Martijn Dashorst > <martijn.dasho...@gmail.com> wrote: >> I was under the impression that *any* mentor is an IPMC member, has a >> binding +1 vote for releases and could therefore approve of releases >> without having to go through general@ >> >> While I find it very helpful and valuable for first time releases (and >> first time release managers) to go to general@ the first time, >> consecutive releases could go a lot smoother if Mentor votes were all >> that is required. >> >> The current policy states: >> >>> Therefore, should a Podling decide it wishes to perform a release, the >>> Podling SHALL >>> hold a vote on the Podling's public -dev list. At least three +1 votes are >>> required (see the >>> Apache Voting Process page). If the majority of all votes is positive, then >>> the Podling >>> SHALL send a summary of that vote to the Incubator's general list and >>> formally request >>> the Incubator PMC approve such a release. Three +1 Incubator PMC votes are >>> required. >> >> So there's not much leeway here. Although the three +1 incubator PMC >> votes are often already satisfied. >> >> Martijn >> > > There have been numerous releases where we have not followed exactly > that process, two other common approaches these days seem to be: > > - the email to general@ says they already have three IPMC +1 votes on > the poddling dev list, there may or may not be comments on the > general@ thread and the release is done anyway after 3 days > > - the initial vote email is CC'ed to both the poddling dev list and > general@ and the vote result is tallied from both lists and there may > or may not have been votes on general@ > > Both of those approaches seem ok to me and I'd be fine with a simpler > and more flexible policy, perhaps saying that the main thing is that > general@ must be notified.
All PMC members have binding votes - means, they can be -1 on a particular release. I'd appreciate if more PMC members would review releases for projects they don't mentor (however I myself do fail miserably at this). (Let's remember that before mentors were formally established, all releases were ratified on general@ only and much Incubation work happened here.) So making release votes visible on general@ early can only increase overall release quality and give the whole PMC an opportunity to exercise oversight. One could also argue that binding release votes are required to happen on general@. However, in the past this led to stale votes, which does not serve the incubating projects. Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
