On 2/23/06, David M Johnson <[EMAIL PROTECTED]> wrote: > Roller 2.1-incubating RC5 is available for your review. > http://people.apache.org/~snoopdave/release_candidates/ > > The only changes: > - (Security) fix for ResourceServlet to disallow .. paths > - Fix for ROL-1051 to allow spaces in uploaded file names
+1 (Bindong as a member of the Incubator PMC only) > How many more votes do we need to release this puppy? Well, as an ASF PMC, your first official action would be to adopt a set of guidelines that outlined the decision making process. :) In the meantime, the usual protocol to stamp something as an "ASF release" is to hold a a majority vote, which means we need at least three binding +1s (to establish quorum), and more binding +1s than -1s. In the normal course, the PMC member votes are binding (which means they count). In pratice, binding also means that you are using the release yourself, and that you pledge to support the release, with patches and posts to the User list (at least to the extent your volunteer schedule permits). In this case, Roller is a podling and can't release software yet. But, the Incubator PMC can. So, as a compromise, first the Podling PMC votes in the usual way. And then the Incubator PMC also votes in the usual way. After you get a valid majority vote of the PPMC here, you should bring another vote up on [EMAIL PROTECTED] Henri's vote is binding as both a PPMC member and a Incubator PMC member. Mine is only binding as a Incubator PMC member. Right now, the votes stands at Roller PPMC * Dave J +1 * Henri Y +1 Incubator PMC * Henri Y +1 * Ted H +1 The latest published Incubator policy on releases is here: * http://incubator.apache.org/incubation/Incubation_Policy.html#Releases Of course, once Roller graduates, you can release ASF software on your own authority, and need only the one majority vote. The Apache Struts decision making guidelines are a typical example of what Roller might adopt for itself. * http://struts.apache.org/bylaws.html -Ted.
